Module 6: Software Verification and Validation
- V & V must be applied at each framework activity in the software process.
- Verification refers to the set of tasks that ensure that software correctly implements a specific function.
- Validation refers to a different set of tasks that ensure that the software that has been built istraceable to customer requirements. Boehm [Boe81] states this another way:
- Verification: "Are we building the product right?"
- Validation: "Are we building the right product?”
•V & V activities include:
–Quality and configuration audits
•The process of exercising a program with the specific intent of finding
errors prior to delivery to the end user.
•Must be planned carefully to avoid wasting development time and
resources, and conducted systematically.
•What testing shows?
- requirements conformance
- an indication of quality
WHO TESTS THE SOFTWARE
- understand the system but will test "gently" and it driven by "delivery"
- must learn about the system but will attempt to break it and is driven by quality
OVERALL SOFTWARE TESTING STRATEGY
- viewed in the context of the spiral.
- Begins by ‘testing-in-the-small’ and move toward ‘testing-in-the-large’
SOFTWARE TEST DOCUMENTATION
- Test Plan
- Test Design Specification
- Test Case Specification
- Test Procedure Specification
- Test Item Transmittal Report
- Test Log
- Test Incident Report
- Test Summary Report
TEST CASE DESIGN
Focuses on a set of techniques for the creation of test
cases that meet overall testing objectives and the
–focus on the program control
structure (internal program logic).
–Test cases are derived to ensure that
all statements in the program have
been executed at least once during
testing and all logical conditions have
–Performed early in the testing
–Examines some fundamental aspect
of a system with little regard for the
internal logical structure of the
–Performed during later stages of
DERIVING TEST CASES
Flow graph notation:
NURUL AIN BINTI MD HASHIM (IS086681)