- then click on the link "definition of V&V Requirements", NOW!
The V&V requirements defined in the table below for "Family relationships" have mainly been extracted from PSS-05, click on the link "V&V requirements given by PSS-05", NOW!
- then you may browse the requirements.
Click on the next demo step "V&V plan construction", NOW!
| V&V ReqId | V&V requirement |
|---|---|
| VVUR1 | The URD shall provide a general description of what the user expects the software to do (UR12 in ViVaWeb) |
| VVUR2 | All known user requirements shall be included in the URD (UR13) |
| VVSR1 | References that trace software requirements back to the URD shall accompany each software requirement (SR07) |
| VVSR2 | Each software requirement shall be verifiable (SR08) |
| VVSR3 | The SRD shall cover all the requirements stated in the URD (SR12) |
| VVAD1 | A recognised method for software design shall be adopted and applied consistently in the AD phase (AD02) |
| VVAD2 | The ADD shall be complete, covering all the software requirements described in the SRD (AD20) |
| VVDD1 | The DDD shall be complete, accounting for all the software requirements in the SRD (DD15) |
| VVCode1 | The class hierarchy and rule base must be defined and used consistently |
| VVCode2 | The rule base must be complete |
| VVCode3 | The class hierarchy and rule base must comply with expectations for Hybrid Frame Systems |
| VVCode4 | Before a module can be accepted, every statement in a module shall be executed successfully at least once (DD06) |
| VVCode5 | The software must be compliant with the DDD |
| VVCode6 | The software must be compliant with the ADD |
| VVCode7 | System testing shall verify compliance with system objectives, as stated in the SRD (DD09) |
| VVCode8 | Installed system must be validated against the URD |