SOFTWARE
ENGINEERING
18CBC205J(R)
V - MODEL
PRESENTED BY GUIDED BY
BHOOMIKA M MS.DHARANI
INTRODUCTION
• The V-model is an SDLC model where
execution of processes happens in a
sequential manner in a V-shape.
• It is also known as Verification and
Validation model.
3
SE
PHA
ON
ATI
LID
VA
E
AS
PH
N
V MODEL
TIO
I CA
RIF
VE
4
VERIFICATION
It involves a static analysis method (review) done without executing code. It is the process of
evaluation of the product development process to find whether specified requirements meet.
VALIDATION
It involves dynamic analysis method (functional, non-
functional), testing is done by executing code. Validation
is the process to classify the software after the
completion of the development process to determine
whether the software meets the customer expectations
and requirements.
V-MODEL 5
DESIGN PHASE
Requirement Analysis: This phase contains detailed communication with
the customer to understand their requirements and expectations. This stage
is known as Requirement Gathering.
System Design: This phase contains the system design and the complete
hardware and communication setup for developing product.
Architectural Design: System design is broken down further into
modules taking up different functionalities. The data transfer and
communication between the internal modules and with the outside world
(other systems) is clearly understood.
Module Design: In this phase the system breaks down into small
modules. The detailed design of modules is specified, also known as Low-
Level Design (LLD).
V MODEL 6
TESTING PHASE
Unit Testing: Unit Test Plans are developed during module design phase.
These Unit Test Plans are executed to eliminate bugs at code or unit level.
Integration testing: After completion of unit testing Integration testing is
performed. In integration testing, the modules are integrated and the system
is tested. Integration testing is performed on the Architecture design phase.
This test verifies the communication of modules among themselves.
System Testing: System testing test the complete application with its
functionality, inter dependency, and communication. It tests the functional
and non-functional requirements of the developed application.
User Acceptance Testing (UAT): UAT is performed in a user environment
that resembles the production environment. UAT verifies that the delivered
system meets user’s requirement and system is ready for use in real world.
V-MODEL 7
ADVANTAGES
• Easy to Understand.
• Testing Methods like planning, test designing happens
well before coding.
• This saves a lot of time.
• Works well for small plans where requirements are
easily understood.
V-MODEL 8
DISADVANTAGES
• Very rigid and least flexible.
• Not a good for a complex project.
• It does not easily handle concurrent events
• If any changes happen in the midway, then the test
documents along with the required documents, has to be
updated.
THANK YOU!
