Requirements and TestingPeer 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)

Requirements

High-level Design

Low-level Design

Code Unit Testing

Integration Testing

System Testing

Acceptance Testing

8

Requirements Traceability

Reqt. Design Code Unit Test

System Test

Accept. Test

R3.4 D3.4.1 C3.4.1 U3.4.1 S3.4.1 A3.4.1

R3.4 D3.4.2 C3.4.2 U3.4.2 S3.4.2 ---

R3.4 D3.4.2 C3.4.3 U3.4.3 --- ---

R3.5 D3.5.1 C3.5.1 U3.5.1 S3.5.1 A3.5.1