V-Model in Software Testing
Download as PPTX, PDF0 likes579 views
The v-model in software testing refers to the verification and validation model, comprising phases such as requirements, high level design, low level design, implementation, and coding. It is particularly advantageous for small projects due to early defect detection, although changes mid-way necessitate revisions of test documents and specifications. Overall, it promotes proactive defect tracking but can be challenged by changes in requirements.
V-Model in Software Testing
- 1. V-Model in Software Testing V-model in software testing means Verification and Validation model.
- 2. V-model phases 1) Requirements Phase : Prerequisites like BRS and SRS are the starting points of the life cycle; be it software development life cycle or the testing life cycle
- 3. V-model phases 2) High Level Design Phase (HLD) The high level design (HLD) stage concentrates on system design and architecture.
- 4. 3) Low Level Design (LLD) The low-level design (LLD) stage is the place where the software components are designed.
- 5. V-model phases 4) Implementation Phase The implementation stage is, once more, where all coding happens.
- 6. V-model phases 5) Coding Phase The modular level design is transformed into code by the development guys.
- 7. Advantages of V-model Ideal for small scaled projects where understanding the requirements is an easy task. Defects can be detected at an very early stage. Also known as the proactive defect tracking.
- 8. Disadvantages of V-model In the event that any progressions or changes happen in halfway, then the test documents alongside requirement specifications, must be edited and changed.
- 9. Thank You