0% found this document useful (0 votes)
94 views20 pages

4.V Model

The V-model is a software development process that relies on verification and validation activities at each phase of development to ensure requirements conformance before proceeding to the next phase. It involves testing at each stage of the development lifecycle from requirements, high level design, low level design, implementation, coding, unit testing, integration testing, validation, and acceptance testing. The V-model is best suited for small to medium projects with clearly defined requirements where simple technical resources and expertise are available.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
94 views20 pages

4.V Model

The V-model is a software development process that relies on verification and validation activities at each phase of development to ensure requirements conformance before proceeding to the next phase. It involves testing at each stage of the development lifecycle from requirements, high level design, low level design, implementation, coding, unit testing, integration testing, validation, and acceptance testing. The V-model is best suited for small to medium projects with clearly defined requirements where simple technical resources and expertise are available.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

V MODEL

28/06/21 1
ECU
• An electronic control unit (ECU) is any embedded system in
automotive electronics that controls one or more of the electrical
systems or subsystems in a vehicle.

28/06/21 2
ECU

28/06/21 3
Types of ECU
• Door Control Unit
• Engine Control Unit
• Brake Control Unit
• Airbag Control Unit
• Battery Management System etc

28/06/21 4
28/06/21 5
What is a V Model
• It means verification and validation .
• Just like WATER FALL,AGILE model, The life cycle of the V model is a
sequential path of the execution of the process.
• Each phase must be completed before the next phase begins.
• The testing of the product is planned in parallel with corresponding
phase of development.

28/06/21 6
When V model is used?
• It should be used for small to medium size
projects where requirements are clearly defined.
• It should be chosen when simple technical
resources are available with needed technical
expertise.

28/06/21 7
V - model

28/06/21 8
IBM
Rational Target Vehicle
Global DOORS
System Owner Vehicle System test Expert
SRS
System test
System Requirement Analysis &
System Acceptance test
Management
VIL
Software Architect
Integration test System test

Software High Level Design(HLD) HIL

Software & Hardware


Software Lead integration Test
System Architecture & interface

Module test
Software Low Level Design(LLD), Model
Software Integration Test
Development
SIL
MIL
BSW Files UNIT
Code Generation Software Test
Test

Test C

28/06/21 9
Phases
vRequirements
vThe High Level Design
vThe Low Level Design
vImplementation
vCoding

28/06/21 10
Requirements
• In this model the requirements are gathered
before its development and a system test
plan is created.
• The plan test focuses on meeting the
functionality specified in the requirements
gathering.

28/06/21 11
The High Level Design
• It focuses on system architecture and design.

• It provide overview of the solution, platform system,


product and services/process.
• An integrated test plan is created here as well as in order to
test the pieces of the software system ability to work
togather
.

28/06/21 12
The Low Level Design
• Here the actual software components of software are design . It
defines the actual logic for each and every component of the system.
• Component test are created in this phase as well.

28/06/21 13
Implementation
• It is that phase where all the coding take place.
• Once coding is complete, the path of execution up the right side of the
V where the test plans developed earlier are now put to use.

28/06/21 14
Coding
• This is at the bottom of the V-model.
• Module design is converted into code by developer

28/06/21 15
28/06/21 16
Clay Model

28/06/21 17
Clay Model

28/06/21 18
Advantages
• Simple and easy to use.
• Testing activities like planning, test design happens
well before coding.
• This saves a lot of time.
• Avoids the down word flow of the defects.
• Works well for small projects where requirements are
easily understood.

28/06/21 19
Disadvantages

• Very rigid and cost flexible.


• Software is developed during the implantation
phase, so no early prototypes of the software are
produced.
• If any changes happens, then the test requirement
documents has been updated.
28/06/21 20

You might also like