V- model means Verification and Validation model.

Just like the waterfall model, the VShaped life cycle is a sequential path of execution of processes. Each phase must be
completed before the next phase begins. Testing of the product is planned in parallel with a
corresponding phase of development.
The various phases of the V-model are as follows:
Requirements like BRS and SRS begin the life cycle model just like the waterfall model.
But, in this model before development is started, a system test plan is created. The test
plan focuses on meeting the functionality specified in the requirements gathering.
The high-level design (HLD) phase focuses on system architecture and design. It provide
overview of solution, platform, system, product and service/process. Anintegration test plan
is created in this phase as well in order to test the pieces of the software systems ability to
work together.
The low-level design (LLD) phase is where the actual software components are designed.
It defines the actual logic for each and every component of the system. Class diagram with
all the methods and relation between classes comes under LLD. Component tests are
created in this phase as well.
The implementation phase is, again, where all coding takes place. Once coding is
complete, the path of execution continues up the right side of the V where the test plans
developed earlier are now put to use.
Coding: This is at the bottom of the V-Shape model. Module design is converted into code
by developers.
Advantages of V-model:

Simple and easy to use.

Testing activities like planning, test designing happens well before coding. This

saves a lot of time. Hence higher chance of success over the waterfall model.
Proactive defect tracking that is defects are found at early stage.
Avoids the downward flow of the defects.

Works well for small projects where requirements are easily understood.

Disadvantages of V-model:

Very rigid and least flexible.

Software is developed during the implementation phase, so no early prototypes of

the software are produced.

If any changes happen in midway, then the test documents along with requirement
documents has to be updated.

When to use the V-model:

The V-shaped model should be used for small to medium sized projects where

requirements are clearly defined and fixed.

The V-Shaped model should be chosen when ample technical resources are
available with needed technical expertise.

High confidence of customer is required for choosing the V-Shaped model approach. Since,
no prototypes are produced, there is a very high risk involved in meeting customer
expectations.

The V - model is SDLC model where execution of processes happens in a

sequential manner in V-shape. It is also known as Verification and Validation
model.
V - Model is an extension of the waterfall model and is based on association
of a testing phase for each corresponding development stage. This means
that for every single phase in the development cycle there is a directly
associated testing phase. This is a highly disciplined model and next phase
starts only after completion of the previous phase.

V- Model design
Under V-Model, the corresponding testing phase of the development phase
is planned in parallel. So there are Verification phases on one side of the .V.
and Validation phases on the other side. Coding phase joins the two sides of
the V-Model.

The below figure illustrates the different phases in V-Model of SDLC.

The V-Model, also called the Vee-Model, is a product-development process

originally developed in Germany for government defense projects. It has
become a common standard in software development. The V-Model gets its
name from the fact that the process is often mapped out as a flowchart that
takes the form of the letter V.

One of the major handicaps ofwaterfall STLC model was that, defects were found at a very
later state of the development process, since testing was done at the end of the
development cycle. It became very challenging and costly to fix the defects since it were
found at a very later stage. To overcome this problem, a new development model was
introduced called the V Model
V model is now one of the most widely used software development process. Introduction of
V model has actually proved the implementation of testing right from the requirement
phase. V model is also called as verification and validation model

Model is an enhanced version of the classic waterfall model whereby each level
of the development life-cycle is verified before moving on to the next level. With
this model, software testing explicitly starts at the very beginning, i.e. as soon as
the requirements are written.
Here, by testing we mean verification by means of reviews and inspections, i.e.
static testing. This helps in identifying errors very early in the life-cycle and
minimizes potential future defects appearing in the code later in the life-cycle.
Each level of the development life-cycle has a corresponding test plan. i.e. as
each phase is being worked on, a test plan is developed to prepare for the
testing of the products of that phase. Be developing the test plans, we can also

define the expected results for testing of the products for that level as well as
defining the entry and exit criteria for each level.
In the V Model the test activities are spelled out to the same level of detail as
the design activities. Software is designed on the left-hand (downhill) part of the
model, and built and tested on the right-hand (uphill) part of the model. Note
that different organizations may have different names for the development and
testing phases.
The correspondences between the left and right hand activities are shown by
the lines across the middle of the V, showing the test levels from component
testing at the bottom, integration and system testing, and acceptance testing at
the top level.

V Model Advantages

in V Model, Each phase has specific deliverables.

Higher chance of success over the waterfall model due to the

development of test plans early on during the life cycle.

Time concern in comparison with the waterfall model is low or

even we can say 50% less.

Works well for small projects where requirements are easily

understood.

Utility of the resources is high.

V Model Disadvantages

Very rigid, like the waterfall model.

Little flexibility and adjusting scope is difficult and expensive.

Software is developed during the implementation phase, so no

early prototypes of the software are produced.

V Model doesnt provide a clear path for problems found during

testing phases.

When To Use The V Model

As per my knowledge I personally think / feel where time and

cost is the constraints of the project then we can use such

models for quick and cost effective delivery.

In comparison with waterfall model, V Model is more or less the

same but the activity of testing starts very early, which leads to
less time, and cost of the project.