In this model the process execution done in V shape manner. SDLC
It is also known as Verification and validation model. SDLC
It is the extension of waterfall model. SDLC
It follows similar actions, but adds more to it creating a parallel of steps, hence the name V-model. SDLC
For each development phase, there is a testing phase as well. SDLC
Instead of the stages following a cascade effect, they swoop back up to potentially repeated part of the process. SDLC
After determining the requirements and making sure everyone agrees with and knows what to expect, the designing stage is broken down by system, architectural, and modular designs. SDLC
Testing is done after each to find any possible flaws hiding within the software. SDLC
Coding is completed and the testing stage can begin, but as in the same fashion as the design stage, the testing is broken down. SDLC
It consists of unit, integration, system, and acceptance. SDLC
This breakdown offers multiple trials for the product to give the most chance for issue correction before release, thus possibly pulling it back into the development stages. SDLC
Each testing phase corresponds with one of the development stages to give a more defined process. SDLC
The V-Model does take longer than the Waterfall Model and has many of the same downfalls, but it offers more chances to fix issues earlier on. SDLC
While it is definitely a detailed way to perfect a project, it limits the flexibility of fixing bugs later on. SDLC
In this model the next phase will only start when the previous phase developed and tested thoroughly. SDLC
In this model, there’re Verification phases on one side of the ‘V’ while the validations phases are on the other side. SDLC
The Coding Phase joins both sides of the Model. SDLC
Verification Phases of V Model Includes: SDLC
Validation Phases of V Model Includes: SDLC
Applications using V-Model SDLC
Why you should use V-Model SDLC
No comments:
Post a Comment