V-Model:

As soon as customer requirements are gathered, all the requirements will undergo first through In-process Review that is the team will perform all the inspection walk-through and reviews so that at the end of the requirement phase manger will perform the Phase End Review to take the decision can we start the next phase by making the requirements baseline. As soon as requirements are baseline the team will start preparing the acceptance test plan i.e. how the acceptance testing will be conducted when the software as a whole will be ready to release.

Since the Requirements are baseline, it indicates the starting of next phase i.e. Functional Specification. As soon as the functional specification are ready it will under go In-process review that is the team will perform all the inspection walk-through and reviews so that at the end of the Functional Specification phase manger will perform the Phase End Review to take the decision can we start the next phase by making the Functional Specification baseline. As soon as Functional Specification are baseline the team will start preparing the System test plan i.e. How the system testing will be conducted when system as whole will be ready.

Since the System specifications are baseline, It indicates the starting of next phase i.e. HLDS. As soon as the HLDS are ready it will under go In-process review that is the team will perform all the inspection walk-through and reviews so that at the end of the HLDS phase the manger will perform the Phase End Review to take the decision can we start the next phase by making the HLDS baseline. As soon as HLDS are baseline there is enough information to prepare the Integration test Plan i.e. how the Integration testing will be conducted when the modules will be ready.

Since the HLDS are baseline, it indicates the starting of next phase i.e. LLDS. As soon as the LLDS are ready it will under go In-process review that is the team will perform all the inspection walk-through and reviews so that at the end of the LLDS phase the manger will perform the Phase End Review to take the decision can we start the next phase by making the LLDS baseline. As soon as LLDS are baseline there is enough information to prepare the Plan for Unit testing i.e. how the Unit testing will be conducted when the Small peace of code is will be ready.

Since the LLDS are baseline, it indicates the starting of next phase i.e. coding. As soon as the Code is ready it will under go In-process review that is the team will perform all the inspection walk-through and reviews so that at the end of the Coding phase the manger will perform the Phase End Review to take the decision can we start the next phase by making the Code baseline.

As soon as the code is baseline the team will start the unit testing according to the Unit test plan to meet the LLDS.
After the successful unit testing team will start combining the units to build the module since the modules are getting created the team will perform the Integration testing according to the Integration test plan to meet the HLDS.
After the successful Integration testing the System as a whole will be ready which indicates the start of System testing. In System testing team will perform both functional and non-functional testing according to the System test plan to meet the System Specification.
After the successful completion of System testing System is now ready to release but before releasing the system the team will perform the User acceptance testing with customer according to the Acceptance test plan to meet the Requirements.

The V-Model (or VEE model) is a systems development model designed to simplify the understanding of the complexity associated with developing systems.[2][3][4] In systems engineering it is used to define a uniform procedure for product or project developmen

Hello all,

V Model is software development life cycle model which incorporates testing to be done in phases along with each phases of software development. So, mainly V Model is a combination of two life cycle models one for development and one for testing :-
1) Software Development Life Cycle - Software development.
2) Software Testing Life Cycle - Software Testing.

Software development life cycle includes 4 phases of software development such as - Documentation of user requirements , Documentation of system requirements , Designing the global structure and Designing the detailed structure.

Software testing life cycle also includes 4 phases of testing each of which associated with the respective phases of SDLC. They are :-
a) Acceptance test execution (associated with Documentation of user requirements)
b) System test execution (associated with Documentation of system requirements)
c) Integration test execution (associated with Designing the global structure)
d) Component test execution (associated with Designing the detailed structure)

Regards
Sitam