Software Test Services: V-Model

Hello, guys! I hope that you enjoy our blog because we are trying hard to provide interesting and useful information. If you are interested in software, it's peculiarities - click here for more information! 
And now let's proceed to V-Model.


It is a sequential software development model and it gained its name because the diagram resembles letter V. Classical V-model consists of 4 levels, where each development level has its own test level.

Basic Levels of V-Models Are:

Component/Unit testing. Dedicated testing team check different components of the software.
Integration testing. Testers verify the correlation between program interface and external systems or components of the software product
System testing. Testers check the performance of the whole software product.
Acceptance testing. The customer or users perform the given testing type.

V-model differs from Waterfall model that now there is not only one level of testing after encoding but four levels. 

Testing Process Starts at the Stage of Receiving Requirements:

- Based on requirements, dedicated tester creates acceptance testing.
- Because of functional requirements, system tests are created.
- Based on the technical specification, testers create continuous integration services.
- Component/ Unit tests are created based on the program specification.

When a code is written, software testing starts from component testing and finishes with acceptance testing. The advantage of this model is that at each level of development (programming) there are active testers who can find errors in the documentation, refine and clarify the job functionality in documentation before the code was written.


- The model is easy in using.
- Testers participate in the project from its early stages.
- Test planning and test design take place before writing the code, which saves time and helps to detect defects or clarify discrepancies in documentation.
- Is suitable for small projects, when all the requirements are clear.
- Testers detect bugs in the early stages.


- A prototype of the product is missing until the code is not written.
- Changes in unplanned requirements require patching in the test plan, test design and test.

It is Recommended to Use When:

- When all the requirements are formulated.
- The project’s complexity is small or medium.
- Qualified staff is available at every level of development.

No comments: