V-Model methodology involves development and testing with similar information in hand at the same time. The V model shows the development phases on the left hand side and the testing phase on the right hand side.
As seen the above fig; left arm of the V model is traditional waterfall model and the right arm is for corresponding testing phases. Each verification activity has its corresponding validation activity.
The development team follows the Do Procedure for achieving the goals of the enterprise; where as the testing team follows the Check Procedure for verification.
It describes how the test approach is developed so that it can be executed in parallel with the designing and development/build phases. Testing phase as per the v-model starts as soon as the SRS is available from the design phase.
Activities running in parallel:
a. Design: Determine business requirements
Testing: Review requirements, Analyse test requirements
b. Design: Determine system requirements
Testing: Review solution, Develop Master Test Plan
c. Design: Design solution
Testing: Develop Detailed Test Plan/s
d. Design: Design component solution
Build: Buy / build components
Testing: Test components
e. Build: Integrate components
Testing: Test integration of components
f. Build: Install system
Testing: Test against system requirements
g. Build: Accept system
Testing: Test against business requirements
Nice blogpost. Really useful for me to understand about v model testing. New information for me. software testing training in Bangalore
ReplyDelete