Requirement Linking
Linking of requirements is what creates the V pattern for Validation and Verification.
The V model is easy to visualize, and can be seen on the about page or further reading on Wikipedia .
Why linking is important
Requirement linking is crucial for several reasons:
Traceability: Links create a clear path from stakeholder needs to technical implementation, ensuring nothing is missed.
Impact Analysis: When requirements change, links help identify all affected components and documentation.
Verification & Validation: Links ensure that each requirement is properly tested and verified, forming the V-model pattern.
Completeness Check: Links help identify orphaned requirements or implementations without requirements.
Regulatory Compliance: Many regulated industries require traceability matrices that demonstrate requirements have been implemented and tested.
Suspect Links
What does it mean to be suspect
A suspect link is a relationship between requirements (or between a requirement and a test) that may no longer be valid due to changes in either the source or target item. Links become suspect when:
- The linked requirement has been modified
- The implementation or test linked to the requirement has changed
- Related requirements have been updated that might affect the validity of the link
Suspect links indicate areas that need review to ensure continued alignment between requirements, implementation, and testing.
How does Requify show this
Please refer to the Suspect Links Page .
What should be done
When encountering suspect links, follow these steps:
Review the Changes: Examine what changed in the source and target items that caused the link to become suspect.
Assess Impact: Determine if the changes invalidate the relationship or if the link is still valid.
Update as Needed: Modify requirements, tests, or implementations to restore alignment.
Confirm Links: Once satisfied that the relationship is valid, mark the link as confirmed in Requify.
Document Decisions: For significant changes, document the reasoning behind confirming or modifying links.
Regular review of suspect links is an essential part of maintaining requirement integrity throughout the development lifecycle.