Professional Documents
Culture Documents
Verification and Validation
Verification and Validation
Validation: are we building the right product? Verification: are we building the product right?
(Boehm, 1979)
Verification:
Validation:
V & V goals
Software function: dependant on how critical the sw is for the organization User expectations Marketing environments: dependant on competing sw, market prices, delivery times
Approaches to V&V
Analysis of sw documents and source code Static process, doesn t need to run the system Running an implementation of the sw with test data Dynamic process, main V&V technique
Software testing:
Program
Prototype
Program Testing
Types of testing
Validation testing:
Checks for sw meeting customer s requirements Checks performance and reliability Looks for inconsistencies between program and specification
Defect testing:
System debugging
Test results
Locate error
Service
Acceptance test
Testing process Requirements traceability Tested items Testing schedule Test recording procedures Hardware and software requirements Constraints
Inspection vs testing
Inspection => static => one error cannot lead to another one Inspections can be performed on incomplete version Inspections look for more than sw defects
Inspections checklist
Data faults Control faults I/O faults Interface faults Storage management faults Exception management faults