V - Testing
Verification and Validation Activities
- Requirements gathering
- Requirements specifications or objectives → The specified objectives from the full system which is going to be developed, are prepared in the form of a document known as software requirement specification (SRS).
- Funtional or High-Level Design or Macro-Level → describes product behaviour as a whole.
- Internal or Low-Level Design or Micro-level → describes each and every module in an elaborate manner.
- Coding
Flow of Validation Testing:
Unit → Integration and Function → System → Acceptance testing
Flow of Verification testing:
Static → Black box → White box
Verification
Verifiaction of Requirements → Builds an Acceptance test plan
- Correctness
- Unambiguous → a requirement should not provide too many meanings or interpretations.
- Consistent → No specification should contradict or conflict with another.
- Completeness
- Updation → if any updation is there in the SRS, then the updated specifications must be verified.
- Traceability
Verification of High level Design → Builds Function and Integration test plan
The architecture and design is documented in another document called the software design document (SDD).