Chapter V - Software Verification and Validation
Chapter V - Software Verification and Validation
Software
Verification and Validation
?
What’s the difference?
• Verification
Are you building the product right?
• Software must conform to its specification
• Is the process of checking that software achieves its goal
without any bugs.
• Validation
Are you building the right product?
• Software should do what the user really requires
• Is the process of checking whether the software product is
up to the mark or in other words product has high level
requirements.
What’s the difference? (cont’d)
Verification and Validation Process
• Defect testing
• Tests designed to discover system defects
• A successful defect test reveals the presence of
defects in the system
• Statistical testing
• Tests designed to reflect the frequency of user
inputs
• Used for reliability estimation
Verification and Validation Goals
• Component Testing
• usually responsibility of component developer
• test derived from developer’s experiences
• Integration Testing
• responsibility of independent test team
• tests based on system specification
Testing Priorities
• Exhaustive testing only way to show program is
defect free
• Exhaustive testing is not possible
• Tests must exercise system capabilities, not its
components
• Testing old capabilities is more important than
testing new capabilities
• Testing typical situations is more important
than testing boundary value cases
The defect testing process
Test Test Test Test
cases data results reports
Execution File
Simulator
report comparator