V model software engineering

V-MODEL -SDLC
Software Engineering
prepared by
MUHAMMAD-ASIF(Kanju)
MIT (2017-2019)
UOS-Sub-Campus
Bhakkar

What is V model
Phases of V-Model
Steps In V-Model
When to use V model
Merits
Demerits

What is V model
V- model means Verification and
Validation model.
Just like WATER FALL model.
It is next version of Water Fall model.
Each phase must be completed before
the next phase starts.

Phases of V-Model
There are two phases
Verification Phase
Validation Phase

Verification Phase;
= check it proper Steps are Followed to
develop Software.
It is confirm software is built in a Right way.
Validation Phase;
= it check if the software is made as per user
Requirement.
Validation confirm “Right Software “.

Requirements
Analysis
System
Requirements
Analysis:
Low Level
design
System design
Coding
System
testing
Integration
testing
Unit testing
User
acceptance
testing
User accept test Cases
Quality team
System Test Cases
Quality team
Integration Test
Development
team
Unit Test
De-team
Steps In V-Model

Requirements Analysis;
= In this model the all requirements are
gathered from the user. The Developer go to the user and say that tell all
complete information about project .
System Requirement Analysis:
= System analysis include hardware and software, different
tools. in the system Analysis we preparing the all documents . Basically,
systems analysis involves techniques that allow you to understand how a
system works.
Verification Phase

System design;
= In difference computer between what is the
integration what is the data flow. How to enter the input and output in all
things we describe in the System Architecture design.
Low Level design;
= in Low Level design we Complete the coding works. The
low level design document or program
specifications will contain a detailed functional logic of
the module, in pseudo-code.
Coding;
= coding phase we start the actual works .This is at the bottom of
the V-Shape model. Module design is converted into code by developers.

Validation Phase
Unit testing:
= who we make a system we check separate all parts
of the system testing.
Integration testing:
= Integration Test Plans are developed
during the Architectural Design Phase. we starts combining the
unit and testing.

System testing:
= who we design a system, its works the user
Requirements or not. If he work the user Requirements . We give
the system to customer.
User acceptance testing:
= we match the customer Requirements
input equal to User acceptance testing output . If the match our
project is complete no error.

When to use V model
The V-shaped model should be used for small to medium
sized projects where requirements are clearly defined and
fixed.
High confidence of customer is required for choosing the V-
Shaped model.

Merits of V-model
Simple and easy to use.
Works well for small projects where
requirements are easily understood.
Testing Planned parallel to
Development.
Bug detection in early phase.
Easy to manage as each phase.

Demerits of V-model
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.
Cost is more.

V model software engineering

More Related Content

What's hot (20)

Similar to V model software engineering (20)

Recently uploaded (20)

V model software engineering