V model

Submitted by: Morris Rillon
Albert Loui John R. Alejandre
Section: BSIT-3C

 V-Model is also called Verification and Validation model.
 The V-model is an SDLC model where execution of processes happens in a sequential
manner in a V-shape.
 The V-Model is a unique, linear development methodology used during a software
development life cycle(SDLC).
 Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of
processes.
 V-Model is one of the many software development models. Testing of the product is
planned in parallel with a corresponding phase of development in V-model.

Requirements
System Design
Architecture
Design
Module Design
Implementation/Coding
Acceptance Testing
System Testing
Integration Testing
Unit Testing
Phases of V-Model

 Requirements
 Gather as much information as possible about the details & specifications of the desired software from the
client.
 System Design
 Utilizing feedback and user requirement documents created during the requirements phase, this next
stage is used to generate a specification document that will outline all technical components such as the
data layers, business logic, and so on.
 Architecture Design/High level design(HLD)
 During this stage, specifications are drawn up that detail how the application will link up all its various
components, either internally or via outside integrations. Often this is referred to as high-level design.
 Module Design/Low level design(LLD)
 This phase consists of all the low-level design for the system, including detailed specifications for how all
functional, coded business logic will be implemented, such as models, components, interfaces, and so forth.
 Implementation/Coding
 At this point, halfway through the stages along the process, the actual coding and implementation occur.
This period should allot for as much time as is necessary to convert all previously generated design and
specification docs into a coded, functional system.

 Unit Testing
 Unit testing is the testing at code level and helps eliminate bugs at an early stage, though all defects
cannot be uncovered by unit testing.
 Integration Testing
 Integration testing is associated with the architectural design phase. Integration tests are performed to
test the coexistence and communication of the internal modules within the system.
 System Testing
 System testing is directly associated with the system design phase. System tests check the entire system
functionality and the communication of the system under development with external systems. Most of the
software and hardware compatibility issues can be uncovered during this system test execution.
 Acceptance Testing
 Acceptance testing is associated with the business requirement analysis phase and involves testing the
product in user environment. Acceptance tests uncover the compatibility issues with the other systems
available in the user environment. It also discovers the non-functional issues such as load and
performance defects in the actual user environment.

 Simple and easy to use
 Ideal for Time Management
 Suited for Restricted Projects
 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.

 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.
 Lacks Adaptability
 Timeline Restrictions
 Ill-Suited for Lengthy Life Cycles

 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.

 The left side of the model is
Software Development Life
Cycle - SDLC
 The right side of the model is
Software Test Life Cycle -
STLC
 The entire figure looks like a
V, hence the name V - model

Sources:
http://istqbexamcertification.com/what-is-v-model-advantages-disadvantages-and-
when-to-use-it/
https://www.guru99.com/software-testing-lifecycle.html
http://www.softwaretestingclass.com/v-model/
https://airbrake.io/blog/sdlc/v-model
https://www.tutorialspoint.com/sdlc/sdlc_v_model.htm

V model

More Related Content

What's hot (20)

Similar to V model (20)

Recently uploaded (20)

V model