Software Testing Life Cycle – V Model

In software testing v model stands for verification and validation. This model defines mapping between software development phase and testing phase. Simply we can say that testing and development phases are performing parallel. In Developers used “Do-Procedure” to achieving the goals, and testing team follows “Check-Procedure” to find errors. Thus v-model means the testing strategy starts from the design phase till itself and continue till the system test.

In Software Testing Life Cycle (STLC) the V-model is extension of waterfall model. Rather than going down in linear way, there steps are bent upwards after coding phase, which is a typical V shape. The V model is a relationship between every phase of the development life cycle and its related phases of testing.

Stages of v model:

Requirement and analysis: In this phase we get the requirements from client side, analysis.

System Design: In this phase we design entire system which means we done DB design, Screens, forms.

Architecture Design: In Architecture design phase the architecture of system is done. Means whether it is web application, desktop application or it is client server architecture.

Module Design: In this phase we individual modules are designed.

Coding: In coding phase actual coding is done. Software programmers will do the programming of the given application.

Module Testing: In module testing the programmers test the module by their itself. Here no QA/QC is involved.

Integration Testing: In this stage actual testing is done to make sure that after various modules integrating of the system as whole is properly working and the referential integrity is maintained or not.

System Testing: This is the final stage of testing before delivering, in this phase entire system is tested by different types like performance testing, usability testing, stress testing, etc.

User Acceptance Testing: This is basically done by user. They verified that whether their requirements are met by system or not.