1 / 8

Requirements and Testing Peer Reviews and Walkthroughs

Requirements and Testing Peer Reviews and Walkthroughs. CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 8, 2007. V&V Terminology (from last time).

lorne
Download Presentation

Requirements and Testing Peer Reviews and Walkthroughs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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. Requirements High-level Design Low-level Design Code Unit Testing Integration Testing System Testing Acceptance Testing Testing Relationships (from last time)

  8. Requirements Traceability

More Related