V Model in SDLC | What are the Different Software Development Models

 

What is V-model in SDLC? 

The V-Model is a software development methodology that is used to guide the development process from the beginning to the end. The name "V-Model" comes from the shape of the process, which is represented by a V-shape. The left side of the V represents the development phases, and the right side represents the testing and validation phases.

Different Phases in V Model?

This model came up in order to overcome the drawback of the waterfall model – here testing starts from the requirement stage itself.

The V & V model is shown in the figure in the next page.

1) In the first stage, the client send the CRS both to developers and testers. The developers translate the CRS to the SRS.

The testers do the following tests on CRS,

1. Review CRS

a. conflicts in the requirements

b. missing requirements

c. wrong requirements

2. Write Acceptance Test plan

3. Write Acceptance Test cases

The testing team reviews the CRS and identifies mistakes and defects and send it to the development team for correcting the bugs. The development updates the CRS and continues developing SRS simultaneously.

2 ) In the next stage, the SRS is sent to the testing team for review and the developers start building the HLD of the product. The testers do the following tests on SRS,

1. Review SRS against CRS

a. every CRS is converted to SRS

b. CRS not converted properly to SRS

2. Write System Test plan

3. Write System Test case

The testing team reviews every detail of the SRS if the CRS has been converted properly to SRS.

3 ) In the next stage, the developers start building the LLD of the product. The testers do the following tests on HLD,

1. Review HLD

2. Write Integration test plan

3. Write Integration test case

4 ) In the next stage, the developers start with the coding of the product. The testing team carries out the following tasks,

1. Review LLD

2. Write Functional test plan

3. Write Functional Test case

After coding, the developers themselves carry out unit testing or also known as white box testing. Here the developers check each and every line of code and if the code is correct. 

After white-box testing, the s/w product is sent to the testing team which tests the s/w product and carries out functional testing, integration testing, system testing and acceptance testing and finally deliver the product to the client. 

The testing and validation phases of the V-Model include:

Unit testing: This phase is used to test individual components of the system to ensure that they work as expected.

Integration testing: This phase is used to test the integrated system to ensure that all the components work together as expected.

System testing: This phase is used to test the entire system to ensure that it meets the user's requirements.

Acceptance testing: This phase is used to test the system with the end-users to ensure that it meets their needs and expectations.

The V-Model is a linear sequential model, meaning that each phase must be completed before moving on to the next one. This makes it a good choice for projects with well-defined requirements and a clear end goal. One of the main advantages of the V-Model is that it provides a clear and well-defined process for development and it ensures that the final product will meet the user's requirements.

Advantages and Disadvantages of the V Model?

Advantages of V-Model:

Clear and well-defined process: The V-Model provides a clear and well-defined process for development, which helps to ensure that the final product will meet the user's requirements.

Early detection of defects: The V-Model includes extensive testing and validation phases, which helps to detect defects early in the development process, reducing the overall cost and time needed to fix them.

Improved communication: The V-Model promotes clear communication and collaboration between different teams and stakeholders, which helps to ensure that everyone is on the same page and working towards the same goal.

Better quality assurance: The V-Model includes a thorough testing and validation process, which helps to ensure that the final product meets the user's requirements and is of high quality.

Disadvantages of V-Model:

Inflexible: The V-Model is a linear sequential model, which means that each phase must be completed before moving on to the next one. This can make it difficult to adjust to changes in requirements or unexpected issues that arise during the development process.

Time-consuming: The V-Model includes a lot of testing and validation phases, which can add a significant amount of time to the overall development process.

Costly: If defects are found during the testing and validation phases, it can be costly and time-consuming to go back and fix them.

Not suitable for projects with constantly changing requirements: The V-Model is not suitable for projects with constantly changing requirements, as it can be difficult to adjust to changes in requirements or unexpected issues that arise during the development process.

In summary, The V-Model is a linear sequential software development model that provides a clear and well-defined process for development, however, it can be inflexible, time-consuming and costly if requirements change during the development process. It is best suited for projects with well-defined requirements and a clear end goal.