What is a V-Model or V-Shaped Life Cycle?

Verification (Are we building the Product Right) and Validation (Are we building the Right Product) model is otherwise known as the V-Model. Here all the processes or the phases of development (Verification) are executed sequentially one by one and in parallel the test plan and test conditions (Validation) for the corresponding test phase are created, reviewed and Signed off. The previous Development Phase or Process must be completed before the next phase or the process begins. 

Please refer the diagram below to understand the V- Model clearly. Initially when the Business Requirement Documents or BRD’s are created ,in parallel the User Acceptance Testing or UAT Test Plan is created and the test conditions as per the BRD’s are Reviewed and finalized which will be tested during the execution phase of UAT.

In the next phase System Requirement Documents or Specification (SRS) are derived from the BRD’s during this phase the system Test Plan and Test Conditions are created reviewed and finalized as per the SRS which will be executed during the System Testing.

After the SRS are finalized then the High Level Design document or HLD is derived out of it which focuses on the system architecture and design. During this phase the integration test plan and test condition as per the high level design document are created which will be executed during the execution phase of Integration Testing.

Before the coding starts the low-level design document or LLD is derived out of the high HLD where the detailed software components are designed and in parallel the Unit test plan and test conditions are Reviewed and finalized which will be executed during the execution phase of unit testing or component testing.

In short every development or design phase has the corresponding Test Plan and test conditions created for that test phase. This Model is very easy and Simple to use for the small or medium sized projects and a lot of time is saved as the test planning and test designing happens before the actual coding starts. This has a high probability of finding the defects in an early stage.

As the documentation happens at an earlier stage ,hence any requirement change in the middle or last stage needs all the documents to be updated accordingly .

Join Renaissance Softwares today to become an expert in Software Testing +91- 8698055550