V-MODEL

• The V-model is a form of SDLC model in which processes are executed in a V-

shape in a sequential way. It is also known as the Verification and Validation
model. It is based on the assignment of a testing phase to each matching
development step. The progress of every stage is closely related to the testing
phase. The next step begins only once the preceding phase has been
completed, i.e. there is a testing activity for each development activity.
VERIFICATION:

• It entails a static analysis approach (review) that is performed without

executing code. It is the process of determining whether defined
requirements are met throughout the product development phase.
 VALIDATION:

• It includes dynamic analysis techniques (functional and non-functional) and

code execution testing. Validation is the process of evaluating software after it
has been developed to see whether it satisfies the customer's expectations
and needs.
• So the V-Model features Verification stages on one side and Validation phases
on the other. In a V-shape, the verification and validation stages are linked by
the coding phase. As a result, it is known as the V-Model.
DESIGN PHASE: 

• Requirement Analysis: This phase includes extensive discussion with the

consumer to ascertain their needs and expectations. This is known as the
Requirement Gathering step.
• System Design: This phase includes the system design as well as the entire
hardware and communication setup for developing the product.
• Architectural Design: The system design is further subdivided into modules that
perform various functions. Data transport and communication between internal
modules and the outside world (other systems) are well understood.
• Module Design: During this phase, the system is divided into tiny modules. The
exact design of modules, also known as Low-Level Design, is given (LLD).
TESTING PHASES: 

• Unit Testing: During the module design phase, unit test plans are created. These
Unit Test Plans are carried out in order to eliminate defects at the code or unit level.
• Integration testing: Integration testing follows the completion of unit testing. The
components are combined and the system is tested during integration testing. The
Architecture design process includes integration testing. This test ensures that
modules communicate with one another.
• System Testing: System testing examines the whole application, including its
functionality, interdependence, and communication. It also analyzes the functional
and non-functional requirements of the produced program.
• User Acceptance Testing (UAT): UAT is carried out in a user environment that is
similar to the production environment. UAT ensures that the provided system satisfies
the needs of the user and is suitable for usage in the real world.
• Industrial Challenge: As the industry has progressed, technologies have gotten more
complicated, quicker, and ever-changing; nonetheless, there remains a set of
fundamental ideas and concepts that are as relevant now as they were when IT was in
its infancy.
• Accurately define and refine user requirements.
• Design and build an application according to the authorized user requirements.
• Validate that the application they had built adhered to the authorized business
requirements.
PRINCIPLES OF V-MODEL: 

• Large to Small: In V-Model, testing is done in a hierarchical perspective. For

example, requirements identified by the project team, create High-Level
Design, and Detailed Design phases of the project. As each of these phases is
completed the requirements become more and more refined and detailed.
• Data/Process Integrity: According to this idea, the effective design of every
project involves the assimilation and integration of both data and procedures.
At each need, process elements must be identified.
• Scalability: This principle argues that the V-Model idea is adaptable to any IT
project, regardless of size, complexity, or length.
• Cross Referencing: Direct correlation between requirements and
corresponding testing activity is known as cross-referencing.
• Tangible Documentation: According to this idea, every endeavor must
produce a document. Both the project development and support teams require
and use this material. Once the program is in a production environment,
documentation is needed to maintain it.
WHY PREFERRED? 

• It is easy to manage due to the rigidity of the model. Each phase of V-Model
has specific deliverables and a review process.
• Proactive defect tracking – that is defects are found at early stage.
WHEN TO USE? 

• Where requirements are clearly defined and fixed.

• The V-Model is used when ample technical resources are available with
technical expertise.
ADVANTAGES: 
• This is a highly disciplined model and Phases are completed one at a time.
• V-Model is used for small projects where project requirements are clear.
• Simple and easy to understand and use.
• This model focuses on verification and validation activities early in the life
cycle thereby enhancing the probability of building an error-free and good
quality product.
• It enables project management to track progress accurately.
DISADVANTAGES: 

• High risk and uncertainty.

• It is not a good for complex and object-oriented projects.
• It is not suitable for projects where requirements are not clear and contains
high risk of changing.
• This model does not support iteration of phases.
• It does not easily handle concurrent events.