Software Testing - Software V&V and selection processes
- 1. Software V&V and Selection Process • Prepared By : *Salah AboAlrob *Anas Za’za’ *Majd Abbadi • Dr. Sami Awad. • SOFTWARE TESTING AND VALIDATION.
- 2. V&V • Validation: process of evaluating software at the end of its development to insure that it is free from failures and complies with its requirements. • Verification: process of determining whether or not the products of a given phase of a software development process fulfill the requirements established during the previous phase.
- 3. V&V Objectives • Correctness. • Consistency. • Necessity. • Sufficiency. • Performance.
- 4. V&V Approaches • Software Technical Reviews. • Software Testing. • Proof of Correctness. • Simulation and Prototyping. • Requirements Tracing.
- 5. V&V Approaches • Software Technical Reviews: • Walk-Through: feedback about the technical quality or content of the document • Inspections: identify defects • Audits: verify conformance to standards
- 6. V&V Approaches • Software Testing • Module Testing • Integration Testing • System Testing • Regression Testing • Proof of Correctness • Simulation and Prototyping • Requirement Tracing
- 7. V&V Limitations • Theoretical Foundations. • Impracticality of Testing All Data. • Impracticality of Testing All Paths. • No Absolute Proof of Correctness.
- 8. Testing Techniques • Functional Testing and Analysis: • Structural Testing and Analysis: • Error-Oriented Testing and Analysis: • Hybrid Approaches: • Integration Strategies: • Transaction Flow Analysis: • Stress Analysis: • Failure Analysis: • Concurrency Analysis: • Performance Analysis:
- 9. Selection of V&V Techniques Objectives identified Specific Techniques must be selected to accomplish it. Selection of V&V techniques based on software life cycle. • Requirements: Technical Reviews, Prototyping and Simulation. • Specifications: Technical Reviews, Prototyping and Simulation, Requirements Tracing. • Design: Technical Reviews, Prototyping and Simulation, Requirements Tracing, and Proof of Correctness. • Implementations: Technical Reviews, Requirements Tracing, Testing, and Proof of Correctness. • Changes: Same techniques used during modification.