Scribd
Upload
39 views6 pages

V-Shape Model in Software Development

The V-shape model describes the relationship between phases of the software development life cycle and corresponding testing phases. In the V-shape model, development phases are represented on one arm and testing phases on the other to form a V shape. Each development phase has a corresponding testing phase - verification involves static testing to check specifications are met while validation uses dynamic testing like functional testing to ensure user needs are met.

Uploaded by

tyv89783
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
39 views6 pages

V-Shape Model in Software Development

The V-shape model describes the relationship between phases of the software development life cycle and corresponding testing phases. In the V-shape model, development phases are represented on one arm and testing phases on the other to form a V shape. Each development phase has a corresponding testing phase - verification involves static testing to check specifications are met while validation uses dynamic testing like functional testing to ensure user needs are met.

Uploaded by

tyv89783
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

V-Shape Model

Cont..
• V-shape Model is a type of software
development process that describes the
relationship between each phase of the
development life cycle and its corresponding
testing phase.
• The V-shape model is named after its shape,
which resembles the letter “V.” In the V-shape
model, we divide the software development life
cycle into phases and each phase is associated
with a corresponding testing phase.
Cont..
Verification phase
• involves static analysis techniques, such as reviews that are done
without executing code. Verification helps to ensure that the
software conforms to the specifications and standards
• This is the process of checking that a software system meets
specifications and standards and it fulfills the required purpose
a) Requirement Analysis:
 This is the process of defining and documenting the user’s needs
and expectations for the software system. It involves analyzing,
validating and managing the requirements
b)System Design:
 This is the process of defining the overall structure and behavior of
the software system. It involves identifying the components,
interfaces, data flows, functions and constraints of the system.
c) High-Level Design:
Verification phase
 This is the process of defining the architecture and
design of each component of the software system. It
involves decomposing the system into modules.
d) Low-Level Design:
 This is the process of defining the detailed design and
implementation of each module of the software
system
e) Code:
 This is the process of writing, testing and debugging
the source code of the software system
Validation Phase
• Validation involves dynamic analysis techniques, such as
functional testing, non-functional testing, or user acceptance
testing, that are done by executing code. Validation helps to
ensure that the software meets the user needs and expectations
a) Unit Testing:
 This is the process of testing each module or unit of code
independently to verify its functionality and quality. It involves
writing and executing test cases that cover all possible scenarios
and inputs.

You might also like