The scenario
An automotive ADAS project needs to trace feature-level requirements to automated test cases and record execution results.
What is in this drawing
Read the decisions behind it.
01
Many-to-many requirement-test traceability captured via a mapping table.
02
Separate execution table records test runs independent of mapping.
03
ASIL level and priority stored on the Requirement entity.
Use when modeling traceability between requirements and automated tests in safety-critical domains like automotive, aerospace, or medical devices.
More like this
Other examples in this family.
Loading drawing…
DO-178C Requirements and Automated Test Coverage ER DiagramaerospaceOpen →Loading drawing…
Medical Device Software Requirements and Automated Verification Test ER DiagramRequirements EngineeringOpen →Loading drawing…
E-Commerce Checkout Requirements & Selenium Regression Test Automation ERDrequirements managementOpen →