Requirements and Testing Peer Reviews and Walkthroughs CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 8, 2007

2 V&V Terminology (from last time)  verification: The process of determining whether or not the products of a given phase... fulfill the requirements... Did we build it right?  validation: The process of evaluating software... to ensure compliance with software requirements. Did we build the right thing?

3 Peer Review Methods  Walkthroughs  Inspections  Desk Checks  All of these methods are sometimes called “static analysis" methods (defined last time as the process of evaluating software based on its execution)  All of these can be used on requirements

4 Why Review?  Find defects earlier finding and fixing after delivery is 100 times more expensive than during requirements and design peer reviews find 60 percent of defects  Inability to test all artifacts How do you test a non-executable artifact? Exhaustive testing is infeasible

5 Why Review? (continued)  Project tracking progress can be tracked against plans quality can be tracked against history  Education project understanding technical skills  Enhances maintainability improves internal documentation promotes standardization

6 Walkthroughs  Producer "walks through" an artifact  Purposes: education defect detection  No formal results are reported to producer of the artifact

7 Testing Relationships (from last time) RequirementsHigh-level DesignLow-level DesignCodeUnit TestingIntegration TestingSystem TestingAcceptance Testing

8 Requirements Traceability Reqt.DesignCodeUnit TestSystem Test Accept. Test R3.4D3.4.1C3.4.1U3.4.1S3.4.1A3.4.1 R3.4D3.4.2C3.4.2U3.4.2S R3.4D3.4.2C3.4.3U R3.5D3.5.1C3.5.1U3.5.1S3.5.1A3.5.1