Requirements Verification and Validation
Gregor v. Bochmann, University of OttawaBased on Powerpoint slides by Gunter Mussbacherwith material from:G. Kotonya and I. Sommerville, M. Jackson, P. Heymans,S. Som 2008, and D. Amyot 2008Requirements Verification and ValidationSEG3101 (Fall 2010)2SEG3101 (Fall 2010). Requirements Verification and ValidationTable of Contents Introduction to Requirements Verification and Validation Requirements Verification and Validation Techniques Simple checks Prototyping Functional test design User manual development Reviews and inspections Model-based (formal) Verification and Validation The software is done. We are just trying to get it to [1] Anonymous3SEG3101 (Fall 2010). Requirements Verification and Validation4SEG3101 (Fall 2010). Requirements Verification and Validation Requirements Validation Check that the right product is being built Ensures that the software being developed (or changed) will satisfy its stakeholders Checks the software Requirements specification against stakeholders goals and Requirements Requirements Verification Check that product is being built right Ensures that each step followed in the process of building the software yields the right products Checks consist
SEG3101 (Fall 2010). Requirements Verification and Validation Specification with assumptions and guarantees (example) Example: A power utility provides electricity to a client. The problem is that the monthly invoice is not related to the electricity consumption, because there is no information about this consumption.
Download Requirements Verification and Validation
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: