What are the advantages and disadvantages of SDLC V-Model?
Overview
In this tutorial, let’s understand the advantages and disadvantages of SDLC V-Model. For more information on the V-Model, follow the link:
https://www.testingdocs.com/v-model/
Verification Phases
Requirement Analysis
In this phase, customer requirements are gathered and analyzed. Verification activities include reviewing the requirements. This phase involves clear communication with the customer to understand the product expectations and needs.
System Design
In this phase, we analyze and understand the proposed system’s business by studying the user requirements. .
High-Level Design
In this phase, Architectural specifications are understood and designed. Technical and financial feasibility is analyzed.
Low-Level Design
In this phase, actual software components are designed. It defines the actual logic for each component. The developed system is broken into smaller modules, and each of them is explained so that programmer can start coding.
Coding
In this phase, the developer starts coding, and module design is converted into code by developers. The coding is performed following the coding standards of the orgainzation.
Validation Phases
Unit Testing
In this phase, individual components or modules of the product are tested. The purpose of unit testing is to validate each module of the software to works as designed.
Integration Testing
It is the process individual components are integrated and tested. For example, software and hardware components are integrated and tested.
System Testing
In this phase, the complete system is being tested. The entire system’s functionality is tested in this phase.
Acceptance Testing
User acceptance and requirements are tested on environment that is close to end-user or production environment. It uncovers the compatibility issues with the other systems available in the user environment. The product shipping decision ( go / no go) is taken after this testing phase.
Advantages
This model is a simple, and easy to manage. This model is perfect for standard projects with fixed requirements.
Test activities like test designing, planning take place in parallel to development phases. Defects are found at an early stage of software development.
Disadvantages
This approach is not suitable for complex projects. Most of the disadvantages of Waterfall model applies to this model as well. This model ships only once in the entire lifecycle.
Fixed requirements. Changes in the requirements are not allowed .