volume_mute
Five Validation Checks
publish date: 2026/06/06 23:20:10.255870 UTC
volume_muteMatch each validation check to its correct description.
To complete the line match
- Click on an item in the first group
- Click on the match in the second group
To delete a match, double click on a line
Check
Validity
Consistency
Completeness
Realism
Verifiability
Description
Requirements should always be written so that tests can demonstrate the delivered system meets them
The requirements document should define all functions and constraints intended by the user
Requirements should not contain contradictory constraints or conflicting descriptions of the same function
Requirements should be technically and economically feasible to implement within budget and schedule
Analysis may identify additional or different functions required beyond what users initially thought was needed
Correct Answer
(1) Validity,Analysis may identify additional or different functions required beyond what users initially thought was needed
(2) Consistency,Requirements should not contain contradictory constraints or conflicting descriptions of the same function
(3) Completeness,The requirements document should define all functions and constraints intended by the user
(4) Realism,Requirements should be technically and economically feasible to implement within budget and schedule
(5) Verifiability,Requirements should always be written so that tests can demonstrate the delivered system meets them
Explanation
The five validation checks: Validity (may discover additional needed functions), Consistency (no conflicting requirements), Completeness (all required functions and constraints included), Realism (technically and economically feasible), Verifiability (requirements can be tested — if a test is impossible to design, the requirement should be reconsidered).
Reference
Software Engineering, Ian Sommerville, 9th edition