Daisy

Accelerating Testing and Certification with an AI-Driven Requirements Traceability Approach

Date
Tue, Dec 15

From publicly posted calendar Checked 13 hours ago

About this event

Advertisement
From visuresolutions.com

Aerospace software teams face a challenge that extends beyond executing tests: demonstrating that the right requirements have been verified, changes have been evaluated, and the resulting evidence reflects the correct software configuration. When requirements, test cases, and results sit in disconnected systems, establishing these connections becomes time-consuming. AI-driven requirements traceability can help accelerate testing and certification preparation by improving requirements quality, highlighting missing relationships, and supporting analysis across connected engineering information. Combined with requirements-based testing and controlled evidence management, this approach helps teams identify gaps earlier and reduce avoidable rework. For aerospace projects working toward DO-178C objectives, the opportunity is practical: make the path from requirement to verification evidence easier to manage, inspect, and maintain throughout development. AI-driven requirements traceability uses artificial intelligence to assist with analyzing relationships between requirements and associated engineering artifacts, such as designs, test cases, test results, and change records. Conventional traceability records these relationships. AI adds assistance with interpreting the information behind them, for example, flagging a potentially ambiguous requirement, suggesting a relevant test relationship, or summarizing the possible impact of a change. Visure’s Engineering Intelligence approach connects AI agents with requirements, traceability, risks, and verification information through the VISURE MCP Server. This provides engineering context for AI-assisted workflows while retaining governance and lifecycle accountability. The value depends on the quality of that context. An AI suggestion is useful only when engineers can inspect its source, assess its reasoning, and confirm whether the proposed relationship is correct. DO-178C addresses software considerations in airborne systems and equipment certification. The FAA recognizes it through Advisory Circular AC 20-115D as an acceptable means of demonstrating compliance for the software aspects of airborne systems. Its scope includes planning, development, verification, configuration management, quality assurance, and certification liaison. Within this lifecycle, traceability helps teams investigate questions that matter during verification and review: A populated traceability matrix alone cannot answer all these questions. A requirement may be linked to a test that no longer reflects its current behavior. A passing result may belong to an earlier build. Effective requirements traceability therefore requires both maintained relationships and engineering review of what those relationships demonstrate. Efficient requirements-based testing starts with requirements that describe observable, verifiable behavior. Ambiguous wording forces test engineers to interpret intent, increasing the likelihood of inconsistent test cases and late clarification. Consider an illustrative requirement: “The system shall display the warning quickly.” Before designing a meaningful test, engineers need an agreed triggering condition, a measurable response time, and any relevant operating conditions. AI-assisted requirements analysis can help flag this ambiguity for review. Engineers must then establish and approve the intended behavior. Visure describes Vivia as providing governed AI support across requirements, testing, risk, and traceability, with human approval in the workflow. Applied early, this assistance can help teams prepare clearer inputs for verification. The practical goal is to resolve uncertainty while requirements are being developed, before it spreads into implementation and testing. Requirements management and test execution become more useful when information moves between them with its identity and context preserved. RapiTest supports requirements-based testing and interfaces with requirements management tools. Rapita documents a workflow involving requirements import, assignment to tests, reporting, and export, including importing Visure requirements through ReqIF. RapiTest also supports on-target execution and presents expected and actual results when checks fail. Visure and RapiTest’s previously published joint webinar describes executing safety-critical test cases in RapiTest, importing results, and generating requirements-to-test traceability reports. This provides a practical foundation for connecting requirements management with verification activities. A useful workflow follows five stages: Teams should agree how identifiers, versions, result status, and configuration information are handled before relying on the exchanged data. Requirements coverage and structural coverage answer different questions. Requirements coverage examines whether verification activities adequately address the specified behavior. Structural coverage examines which parts of the im

Keep exploring

More around San Francisco

This weekend in San Francisco
600 connected calendars
View full calendar
Around San Francisco, your ad shows up everywhere. See how it works →
Tue
Nov
17
Events
Foodwise San Francisco, CA
11:00 AM
Food & Drink
Tue
Nov
17
Latch Clinic (No Cost for GGDA Clients)
goldengatedoula.com San Francisco, CA
10:00 AM
Classes & Learning
Fri
Nov
20
HVFF
Emporium Arcade Bar San Francisco, CA
9:00 PM
Music
See full San Francisco calendar 256 events this weekend across 600 calendars
Advertisement

Something wrong or missing? Suggest an update