ACCOUNTING

INFORMATION SYSTEM
V-Shaped Model System
Development

02/08/2022 1
AIS GROUP ASSIGNMENT

Name ID NO.

1 Agegnehu Enyew GSE/9104/14

2 Afomia Abebe GSE/8233/14

3 Amina Abdella GSE/7676/14

4 Amir Edris
5 Brook Ephraim GSE/2953/14

02/08/2022 2
 Articles
 Moahmmed Sami. The validation and verification model,
Melsatar Blog, August 2018
 Gaurav Kumar and Pradep Bhatia, comparative analysis of
system development models, research gate, Feb 2014
 Kim R.fowler, developing and managing embedded system
and products, science direct, March, 2015
 Elizabeth Wamich, V-Shaped Model in SDLC Methodology,
Study.com, 2018
 Dharmendra Kumar, software engineering SDLC V-Model,
Geeks for Geeks, May 2019

02/08/2022 3
 V-shaped system development methodology

V Model is one of the most commonly used system

development model. It is also known as the

Validation and Verification System Development

Process Model. Just like Water Fall model It is based

on the association of a testing phase for each

corresponding development stage. Development of

each step directly associated with the testing phase.

02/08/2022 4
 V-shaped system development methodology

 The following diagram is a simple representation of the

V-Shaped of development. As shown clearly, the figure
marks five phases of the process. How verification and
validation steps connect between the various activities
across phases is clearly shown. Validation seeks to
demonstrate that the product meets the original intent,
while, verification is an objective set of tests to confirm
that the product meets the metrics of the requirements.

02/08/2022 5
V-shaped system development methodology

02/08/2022 6
Diagram of V-model:

02/08/2022 7
 V-shaped system development methodology

 In V-Shaped, any phase in the development process begins only if

the previous phase is complete and has a correspondent related

testing phase performed against each phase completion. Similar to

the Waterfall Model, V-Shaped System Development Method does

not go back to the previous phase and ulter the process to handle

changes in requirement.
 V shape refers to the technical aspect of the project cycle starting

with the business needs and requirments on the upper left and

ending with the user acceptance testing on the upper right.

02/08/2022 8
 V-shaped system development methodology

 A limitation of the V-Shaped is that it implies that

the requirements are complete in the conceptual or
preliminary stage. This is certainly not reality in
most, if not all, product developments.
Requirements, design, and evaluation often iterate
several times before final integration and
acceptance. This iterative situation leads to spiral
development as a defined discipline, which is next.

02/08/2022 9
Example:

02/08/2022 10
 V-shaped system development methodology
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 V-Shaped model

The V-shaped model should be used for small to medium sized projects where

requirements are clearly defined and fixed

The usage of V-Shaped can fall under the projects which do not focus on

changing the requirements, where requirements are clearly defined and fixed.
The V-Shaped is used when ample technical resources are available with

technical expertise.

02/08/2022 11
 V-shaped system development methodology

Phases in V- Shpaed System Development

The V-Shaped Model comprises of verification, coding and validation Phases

Verification / Design Phase encompasses the various design and coding

activities that are required in the software development process. These steps

are also referred to as the 'developer's life cycle and they include,
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.

02/08/2022 12
 V-shaped system development methodology

 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 dowm
into small modules. The detailed design of modules is
specified, also known as Low-Level Design (LLD).

02/08/2022 13
 V-shaped system development methodology

 Validation Phase; While verification focuses on development, validation ensures that all that

development was carried out correctly. This process is very dynamic and a great deal of

testing takes place. These steps are also referred to as the 'tester's life cycle and they

include;

 Unit Testing

 The Unit testing is the testing at the code level and helps eliminate issues at an early stage,

mainly the developer is responsible to perform the unit test for his code while not all the

defects cannot be discovered at the unit testing.

 Functional Testing

 Functional testing is associated with the low-level design phase which ensures that

collections of codes and units are working together probably to execute new function or

service.

02/08/2022 14
 V-shaped system development methodology
 Integration Testing
Integration testing is associated with the high-level design phase. Integration
testing ensures the integration between all system modules after adding any
new functions or updates.
 System Testing

System testing is associated with the system requirements and design phase. It

combines the software, hardware, and the integration of this system with the

other external systems.

 User Acceptance Testing
User Acceptance testing is associated with the business and operations analysis
phase. The customer users are the main performers of this testing based on
test cases and scenarios that cover the business requirements to ensure that
they have delivered the right software as per the specifications.

02/08/2022 15
 V-shaped system development methodology

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, they are defining become more and more refined and detailed.
Data/Process Integrity: This principle states that the successful design of any

project requires the incorporation and cohesion of both data and processes.

Process elements must be identified at each and every requirements.

Scalability: This principle states that the V-Shaped concept has the flexibility to

accommodate any IT project irrespective of its size, complexity or duration.

02/08/2022 16
 V-shaped system development methodology

 Cross Referencing: Direct correlation between

requirements and corresponding testing activity is known
as cross-referencing.
 Tangible Documentation: This principle states that every
project needs to create a document. This documentation is
required and applied by both the project development
team and the support team. Documentation is used to
maintaining the application once it is available in a
production environment.

02/08/2022 17
 V-shaped system development methodology

Pros of V-Shaped system development

Simple and easy to use
Each phase has specific deliverables.
Higher chance of success over the waterfall model due to the development of test plans early on during

the life cycle (saves a lot of time).

Works well for where requirements are easily understood.
V-Shaped Improves the quality and reliability of the software.
It reduces the amount of re-work because of the early detection of defects and issues.
It provides better management for project risks.
The V-Shaped concept can be combined with other models, for example, the iterative and agile models.
Testing Methods like planning, test designing happens well before coding.
Proactive defect tracking – that is defects are found at early stage.

02/08/2022 18
 V-shaped system development methodology

Cons of V-Shaped system development

Very inflexible, like the waterfall model.
Adjusting scope is difficult and expensive.
The software is developed during the implementation phase, so no early prototypes of

the software are produced.

The model doesn’t provide a clear path for problems found during testing phases.
Moreover, It is costly and required more time, in addition to a detailed plan
If any changes happen in midway, then the test documents along with requirement

documents has to be updated.

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

02/08/2022 19