
Test Matrix & Traceability Generator for V&V
Generate bidirectional traceability matrices and test coverage maps for V&V compliance
What You Can Do
You can automatically generate bidirectional traceability matrices that map system requirements to test cases and verification results, eliminating manual mapping errors and identifying uncovered requirements. The skill produces audit-ready V&V documentation that demonstrates compliance with aerospace standards, tracks requirement allocation across hardware/software/integration domains, and supports change impact analysis through complete traceability chains.
Features
automatically maps requirements to test cases and back-traces verification results to source requirements
identifies uncovered requirements, orphaned test cases, and incomplete verification chains with visual gap reports
generates structured matrices in formats that satisfy DO-178C, ARP 4754A, and MIL-STD-498 documentation requirements
ingests and standardizes requirement data from DOORS, Requisite, Azure DevOps, or Jira exports
separates and maps requirements across hardware, software, and integration test domains with safety-critical flags
traces requirement modifications through dependent test cases and verifications to assess scope of changes
sets and validates minimum coverage percentages by requirement type or domain for certification readiness
Example Output
Example 1: Requirements Traceability Matrix (RTM)
| Req ID | Requirement Text | Type | Allocated To | Test Case ID | Test Status | Coverage |
|---|---|---|---|---|---|---|
| SYS-101 | System shall accept pilot input within 100ms | Functional | SW | TC-2047, TC-2048 | PASS | ✓ Covered |
| SYS-102 | System shall detect and report sensor failures | Safety-Critical | HW/SW | TC-3001, TC-3002, TC-3015 | PASS | ✓ Covered |
| SYS-201 | Integration test for data flow validation | Integration | SW/HW | TC-5001 | PENDING | ⚠ Partial |
Example 2: Coverage Gap Report
Coverage Summary:
- Total Requirements: 87
- Covered: 82 (94.3%)
- Partially Covered: 3 (3.4%)
- Uncovered: 2 (2.3%) [ALERT: Below 95% threshold]
Uncovered Requirements:
- SYS-305: Environmental qualification test (no test case assigned)
- SYS-412: Graceful degradation mode (orphaned test TC-7043)
Example 3: Change Impact Analysis
Requirement Modified: SYS-102 (sensor failure detection timeout: 200ms → 150ms)
Dependent Test Cases: TC-3001, TC-3002, TC-3015
Downstream Impact: Integration test TC-5001 may need parameter update
Recommendation: Re-run TC-3001, TC-3002, TC-3015; assess TC-5001 validity
What's Included
- SKILL.md: Complete instruction file with core workflow, input/output specifications, and compliance mapping
- RTM Template (Excel/CSV): Pre-formatted traceability matrix with auto-calculation formulas for coverage percentages
- Requirements Ingestion Checklist: Step-by-step guide for exporting and normalizing data from DOORS, Requisite, Azure DevOps, or Jira
- Coverage Gap Report Template: Structured format for identifying uncovered requirements and orphaned test cases
- DO-178C/ARP 4754A Compliance Mapping: Quick-reference guide linking RTM outputs to certification documentation requirements
Who It's For
- Systems Engineers — managing requirements allocation and traceability across hardware/software/integration domains in aerospace programs
- V&V Engineers — creating and maintaining compliance documentation for DO-178C, DO-254, and ARP 4754A certification audits
- Quality Assurance Leads — verifying test coverage completeness and identifying gaps before certification readiness reviews
- Program Managers — tracking requirement status, test execution progress, and change impact across development phases
- Certification Specialists — generating audit-ready traceability evidence for regulatory reviews and configuration audits
Best For
- Creating or updating Requirements Traceability Matrices (RTM) for DO-178C/DO-254 aerospace projects
- Mapping system and software requirements to test cases and acceptance criteria with bidirectional verification
- Identifying and reporting uncovered requirements, orphaned test cases, and incomplete verification chains
- Generating compliance documentation for V&V audits, certification readiness, and configuration reviews
- Performing change impact analysis by tracing requirement modifications through dependent test cases and verifications







