Verification and Validation

Question 1

Verification

vs

Validation

Answer 1

Verification

• Checks if software conforms to specifications
• “Are we building the product right?”

Validation

• Checks if it does what the user really requires
• “Are we building the right product?”

Question 2

V&V:

Two Principal Objectives

Answer 2

• Discover defects in a system
  
  • good implementation
• Assess whether the system is useful and usable in an operational situation
  
  • _​_good design

Question 3

V&V:

Types of Testing

Answer 3

Verification (Defect Testing (not debugging)

Validation Testing

Question 4

Static vs Dynamic V&V

Answer 4

Static V&V

Software Inspections

Analysis of static system representation to discover problems. Class diagrams, linting, etc

Dynamic V&V

Software Testing

Concerned with exercising and observing product behavior

Question 5

Static V&V

What is Inspected?

Answer 5

• Requirements specification
• Software Architecture
• UML Design Models
• Database Schemas
• Code syntax/style

Question 6

Dynamic V&V

What is Tested?

Answer 6

System Prototype

Testing (?)

Question 7

When is

Verification and Validation

performed in the development cycle?

Answer 7

V & V is performed throughout the whole development process.

Each stage of software development requires some sort of V&V

Question 8

Testing:

Stages/Levels of Testing

Answer 8

Component Testing (Development Testing)

System Testing (Integration Testing)

Acceptance Testing (Alpha Testing)

Question 9

Testing:

Difference between

Testing and Debugging

Answer 9

Testing

Establishes the existence of defects

Debugging

Locates and corrects the defects