Software Verification and Validation Practices Flashcards
confirms the consistency among elements of the software architecture.
Software Verification and Validation (V & V) Practices
ensures that each element of the architecture is consistent with the other preceding elements.
Verification
confirms that the structural configuration will fulfill its intended use.
Validation
4 V & V TASKS PRIMARY ACTIVITIS
- Define the V & V strategy
- Verify the software architecture
- Validate the physical architecture
- Document the result of V & V
the V&V activities and task must be incorporated into the software engineering plans.
Define the V & V Strategy
3 THINS TO ESTABLISH WHEN DEFINING V & V STRATEGY
- Establish the V & V Scope
- Establish the V & V Methods
- Establish the V & V Procedures
the software engineering work products should be reviewed to identify V & V opportunities.
Establish the V & V Scope
the methods of conducting must be identified.
Establish the V & V Methods
4 THINGS THAT COULD BE DONE WHEN ESTABLISHING THE V & V METHODS
- Documentation Evaluation
- Peer Review
- Static Analysis
- Dynamic Analysis
procedures for conducting task must be prepares to establish the intended approach for accomplishing a sequence of action.
Establish the V & V Procedures
software engineering verification tasks address confirming that the software product architecture is complete.
Verify Software Architecture
4 THINGS TO BE VERIFIED
- Verify Requirement Baseline
- Verify the Functional Architecture
- Verify the Physical Architecture
- Verify the Software Implementation
software engineering validation tasks address confirming that the physical architecture is complete.
Validate the Physical Architecture
2 OTHER THINGS TO VALIDATE IN THE PHYSICAL ARCHITECTURE
- Validate the Structural Configuration
- Validate the Integrated Software Configuration
the V & V finding must be reported.
Document the V & V Result
