Tests
Requify supports adding test runs for verification and validation requirements.
What is a verification and validation requirement
Verification and validation requirements are essential components of the systems engineering V-model:
Verification Requirements
Verification requirements define how to confirm that a system or component has been built correctly according to its specifications:
- They answer the question: "Did we build the system right?"
- They focus on confirming that the implementation meets the specified requirements
- They typically involve objective, measurable criteria
- Examples include functional tests, performance tests, and compliance checks
Validation Requirements
Validation requirements define how to confirm that a system or component meets the actual needs of stakeholders:
- They answer the question: "Did we build the right system?"
- They focus on ensuring the system satisfies the intended use and user needs
- They often involve subjective assessment and stakeholder feedback
- Examples include user acceptance tests, usability tests, and field trials
The V-Model Connection
In Requify, verification and validation requirements form the right side of the V-model:
- Each verification requirement links to a corresponding system or technical requirement
- Each validation requirement links to a corresponding stakeholder requirement
- This creates complete traceability from requirements to testing
How to create a test run
See tests view for information on Requify's user interface for test cases.
Test statuses
Requify has the following test statuses that can be assigned:
- Running
- No Result
- Failed
- Inconclusive
- Passed with Reservation
- Passsed