Scribd
Upload
41 views21 pages

Embedded Systems Engineering and Testing: Prof. Victor Grigoras

This document outlines an embedded systems engineering and testing course. It introduces the V-model, a systems development methodology where each stage of testing corresponds to a stage of development. The course covers topics like engineering models, embedded programming, testing procedures, and a laboratory component. It emphasizes a top-down design approach, the connection between design and testing, and using the V-model to minimize risks and improve quality.

Uploaded by

Andrei Caza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
41 views21 pages

Embedded Systems Engineering and Testing: Prof. Victor Grigoras

This document outlines an embedded systems engineering and testing course. It introduces the V-model, a systems development methodology where each stage of testing corresponds to a stage of development. The course covers topics like engineering models, embedded programming, testing procedures, and a laboratory component. It emphasizes a top-down design approach, the connection between design and testing, and using the V-model to minimize risks and improve quality.

Uploaded by

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

Faculty of Electronics Signals, Circuits and Systems

“Gheorghe Asachi”
Telecommunications and laboratory
Technical University of
Iasi, Romania Information Technology

Embedded Systems
Engineering and Testing

Prof. Victor Grigoras

1
Contents
 V-model
 General structure
 Objectives
 Topics
 Details
 Streams
 References

2
Course guide
 Lectures
 Engineering models
 General architecture of embedded systems
 Embedded programming
 Programming platform
 Automotive implementation requirements
 General testing procedures
 Structure of software test programs
 Hardware-software connection; influence on testing
 Project planning aspects

3
Course guide
 Laboratory
 Programming platform
 Embedded programming examples
 Sensors and actuators access
 Programs testing elements
 Software test programs
 Automotive embedded testing
 Implementation and performance criteria
 Project themes, steps, planning and programing
 Project testing;
4
References
 Oshana - Software Engineering for Embedded
Systems. Methods, Practical Techniques
 Spillner - Software Testing Foundations
 ORegan - Introduction to Software Quality
 Pressman – Software Engineering a
Practitioner’s Approach
 Noergaard - Embedded Systems Architecture
 Standards (IEEE, ISO, IEC, …)

5
Reference sources

6
Engineering models
 Waterfall model
 analysis  

 design, 

 build, 

 testing, 

 deployment

 maintenance.

 V-model
 Same steps

 Highlights connections between steps

7
Waterfall model

8
V-Model

9
V-Model
 The V-model is a graphical representation of
a systems development lifecycle
 development methodology used during a Software
Development Life Cycle (SDLC)
 In software development, the V-model represents
a development process 
 testing phase for each corresponding development
stage
 extension of the waterfall model

10
V-Model

 Verification and Validation model


 produce rigorous development lifecycle models
 project management models

11
V-Model

 summarizes the main steps to be taken


 corresponding deliverables
 computerized system validation framework,
 project life cycle development
 describes the activities to be performed
 the results that have to be produced 

12
V-Model

 The left side of the "V" represents the


decomposition of
 requirements

 creation of system specifications

 The right side of the "V" represents


 integration of parts

 validation of parts

13
Objectives
Provides guidance for the planning and
realization of projects:
Minimization of project risks

Improvement and guarantee of quality

Reduction of total cost over the

 entire project
 system life cycle
Improvement of communication between
all stakeholders
14
V-model topics
 Systems engineering and verification

15
Design <-> testing

16
Design
 Top – down
 Systemic
 Orderly
 Well understanding
 Bottom – up
 Practical
 Know system structure
 Module design - test

17
The two streams

 Specification stream
 User requirement specifications
 Functional requirement specifications
 Design specifications

18
The two streams

 Testing stream
 Installation qualification (IQ)
 Operational qualification (OQ)
 Performance qualification (PQ)

19
Conclusion

 Follow the steps


 Document the achievements
 Exchange opinions
 Design for testing
 Modify according to test results
 Team project

20
References

 Oshana - Software Engineering for Embedded


Systems. Methods, Practical Techniques
 Spillner - Software Testing Foundations
 ORegan - Introduction to Software Quality
 Pressman – Software Engineering a
Practitioner’s Approach
 Noergaard - Embedded Systems Architecture
 Standards (IEEE, ISO, IEC, …)

21

You might also like