Scribd
Upload
263 views14 pages

V Model

1. The V-model is a software development lifecycle model that depicts the relationships between each phase of the development process and its associated phase of testing. 2. The key phases of the V-model include requirement analysis, system design, architecture design, module design, unit testing, integration testing, system testing, and user acceptance testing. 3. The V-model emphasizes testing at each phase of development, with testing phases mirroring the corresponding development phases in a V shape. This allows issues to be identified and resolved at the earliest stages of the development lifecycle.

Uploaded by

kumavatvedanti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
263 views14 pages

V Model

1. The V-model is a software development lifecycle model that depicts the relationships between each phase of the development process and its associated phase of testing. 2. The key phases of the V-model include requirement analysis, system design, architecture design, module design, unit testing, integration testing, system testing, and user acceptance testing. 3. The V-model emphasizes testing at each phase of development, with testing phases mirroring the corresponding development phases in a V shape. This allows issues to be identified and resolved at the earliest stages of the development lifecycle.

Uploaded by

kumavatvedanti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

V model

Presentation by:-
Vedanti Ishvar Kumavat
V model
Verification phases
Verification Phases

1. Requirement Analysis

2. System Design

3. Architecture Design

4. Model Design
Requirement Analysis

In the requirements analysis phase, the first step in the


verification process, the requirements of the system are
collected by analyzing the needs of the users
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.
Architecture Design

The baseline in selecting the architecture is that it


should understand all which typically consists of the list
of modules, brief functionality of each module, their
interface relationships, dependencies, database tables,
architecture diagrams, technology detail, etc. The
integration testing model is carried out in a particular
phase.
Module Design

In the module design phase, the system


breaks down into small modules. The detailed
design of the modules is specified, which is
known as Low-Level Design
validation Phases

. validation Phases

1. Unit Testing

2. Integration testing

3. System testing

User Acceptance
Unit Testing

In the V-Model, Unit Test Plans (UTPs) are


developed during module design phase. These
UTPs are executed to eliminate bugs at code
level or unit level. A unit is the smallest entity
which can independently exist, e.g. a program
module.
Integration testing
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: 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

User Acceptance Testing (UAT), or application testing,


is the final stage of any software development or change
request lifecycle before go-live.
Advantage of v model

1. Easy to Understand.
2. Testing Methods like planning, test designing happens well before
coding.
3. This saves a lot of time. Hence a higher chance of success over the
waterfall model.
4. Avoids the downward flow of the defects.
5. Works well for small plans where requirements are easily understood.
Disadvantage of v model

1. Not a good for a complex project.


2. Software is developed during the implementation stage, so
no early prototypes of the software are produced.
3. If any changes happen in the midway, then the test
documents along with the required documents, has to be
updated.

You might also like