The scenario
A medical device software team must maintain traceability from design input requirements to automated verification test cases and test execution results to support regulatory submissions.
What is in this drawing
Read the decisions behind it.
01
Introduced RequirementTestTrace entity to model many-to-many relationships between requirements and test cases.
02
Separated TestCase from TestResult to retain test definition history across executions.
03
Linked automation scripts to test cases to distinguish manual vs automated verification.
Use when modeling data for requirements management and automated test execution with regulatory traceability needs.
More like this