Steps
1. Navigate to Testing Space Dashboard
Go to Testing space from the sidebar. The dashboard displays real-time coverage metrics:
- System Requirements Verification Coverage — Percentage of system requirements with linked verification test cases
- Customer Requirements Validation Coverage — Percentage of customer requirements with linked validation test cases
- Design Requirements Verification Coverage — Percentage of design requirements with linked verification test cases
Each coverage bar shows:
[████████░░] 83% (26/31) [View Gaps]
Check coverage incrementally as you create test cases rather than waiting until the end. Set target thresholds per ISO 26262 Part 4 §8: aim for 100% verification coverage for all safety requirements (ASIL A-D) and >90% for QM-classified requirements.
2. Drill Down to Gap Queries
Click View Gaps on any coverage bar to execute a Lucene query showing uncovered requirements:
type:sysReq AND NOT backlinkedWorkItems:verifies=TA*
verifies role.
Coverage Query Structure:
| Requirement Level | Gap Query | Link Role | Direction |
|---|
| System Requirements | type:sysReq AND NOT backlinkedWorkItems:verifies=TA* | verifies | backward (test → req) |
| Customer Requirements | type:customerRequirement AND NOT backlinkedWorkItems:validates=TA* | validates | backward (test → req) |
| Design Requirements | type:desReq AND NOT backlinkedWorkItems:verifies=TA* | verifies | backward (test → req) |
TA* wildcard matches all test case IDs with the project prefix.
System and Design requirements use verifies link role (verification tests). Customer requirements use validates link role (validation tests). Mixing these roles breaks coverage metrics. See Verification vs Validation Model for semantics. 3. Analyze Multi-Hop Coverage (SC/CC Requirements)
For safety-critical and cybersecurity-critical design requirements, check SC/CC Design Reqs → Failure Modes coverage on the Design space dashboard:
Covered: 11/14 (78%)
Gap Query: type:desReq AND classification.KEY:(sc cc)
The coverage algorithm checks:
- Find characteristics that refine the SC/CC design requirement
- Find failure modes that assess those characteristics
- Coverage = design requirements with at least one failure mode in the chain
4. Use Verification PowerSheets for Detailed Review
Open verification PowerSheets to see requirement-to-test-to-evidence chains:
- System Verification Sheet — System Requirements → Verification Test Cases → External Evidence
- Design Verification Sheet — Design Requirements → Verification Test Cases → External Evidence
- Subsystem Verification Sheet — Subsystem Requirements → Verification Test Cases
Each PowerSheet shows:
System Requirement | Verification Test Case | Evidence
-----------------------------|----------------------------|------------------
TA-123 Sensor fusion logic | TC-045 Unit test fusion | TR-012 Result OK
| TC-046 Integration test | (missing)
TA-124 Braking threshold | (no test case) |
Create missing test cases inline from PowerSheet rows using the entity factory: click the test case title field, type the test name, press Enter. The test case is auto-created in Testing/SystemVerificationSpecification with automatic link to the requirement.
5. Review FMEA Coverage Report
Navigate to FMEA Coverage Report from the Reports section. This validates:
- SC/CC Customer Requirements → Failure Modes — 24/25 covered (96%)
- SC/CC System Requirements → Failure Modes — All covered (100%)
- SC/CC Design Requirements → Failure Modes — 11/14 covered (78%)
- Functions → Failure Modes — All covered (100%)
- SFMEA Failure Modes → Child Failure Modes — All covered (100%)
The report uses transitive link coverage checks across refines, assesses, and parent relationships.
6. Generate Traceability Report
Run the Requirements Traceability Report for full bidirectional coverage matrix:
- Go to Reports → Requirements Traceability Report
- Select report scope (All Requirements, System Only, Design Only)
- Click Generate
The report shows forward and backward coverage:
| Traceability Link | Coverage | Percentage |
|---|
| Customer Req → System Req (refined by) | 14/25 | 56% |
| System Req → Design Req (refined by) | 10/31 | 32% |
| System Req → Test Cases (verified by) | 26/31 | 83% |
| Design Req → Test Cases (verified by) | 15/15 | 100% |
7. Set Coverage Targets in Safety Readiness Scorecard
Check overall verification percentage in the Safety Readiness Scorecard:
| Standard | Verification % | Target |
|---|
| ISO 26262 Part 3 (Concept) | 48% | 100% |
| ISO 26262 Part 4 (System Design) | 83.9% | 100% |
| ISO 26262 Part 5 (Hardware Design) | 100% | 100% |
| ISO 26262 Part 6 (Software Dev) | 100% | 100% |
verifies or validates / total requirements in scope.
Verification Steps
You should now see:
- Real-time coverage percentages on Testing, Requirements, and Design space dashboards
- Gap query results showing uncovered requirements with clickable links
- PowerSheet views displaying requirement-test-evidence chains with visual gaps
- FMEA coverage metrics for safety-classified items
- Overall verification % per ISO 26262 part in the Safety Readiness Scorecard
See Also
