Professional Documents
Culture Documents
Automotive Systems
Eckard Bringmann and Andreas Krmer
ICST08
Multidisciplinary Business
Model-based Development
Became Popular
System
Improves
communication
with
multidisciplinary
stakeholders
Improves
communication
with customers
and with suppliers
F2
F3
F1
F5
F4
Reduces costs by
early validation
via simulation
and testing
5
Model-based Development
Became Popular
System
F2
F3
F1
F5
F4
Abstract models
describing the behavior
of the system.
Model-based Development
Became Popular
System
F2
F3
F1
F5
F4
Detailed software
models which consider
all software-related
aspects
7
Validation Stages
MiL: Model in the loop
F2
F3
F1
F5
F4
Models run in a
virtual environment
Functional models
at the system level
Implementation models
at an individual module and
a whole system levels
Validation Stages
MiL: Model in the loop
F2
F3
F1
F5
F4
Validation Stages
MiL: Model in the loop
F2
F3
F1
F5
F4
10
Validation Stages
MiL: Model in the loop
F2
F3
F1
F5
F4
11
Validation Stages
MiL: Model in the loop
F2
F3
F1
F5
F4
Test Rig
The environment
PiL: Processor
in theofloop
consist
physical
components (electrical,
mechanical, hydraulic)
12
Validation Stages
MiL: Model in the loop
F2
F3
F1
F5
F4
Test Rig
Car
13
Outline
1. Motivation: challenges of in-car
software development process
2. Requirements for testing
3. TPT tool for automotive model-based
testing
4. Experience report
5. Future work
6. Summary and discussion
15
Example: Exterior
Headlight Controller
1.
2.
3.
4.
17
1. Test Language
18
1. Test Language
More features
(hierarchical state
machines, junctions,
actions on transitions, )
are available
No dependency on
software implementation
or ECU
can run on an arbitrary
platform, given the
appropriate adapter
19
1. Test Language
20
Headlight signal
remains off
21
22
Variation Points
23
24
25
Highly compact
byte code,
executed by a
dedicated TPT-VM
virtual machine
26
TPT VM executes
the tests and
communicates with
SUT via adapters
Recorded
Test
Signals
28
Offline using
assessment
scripts provided
for each test
29
30
Outline
1. Motivation: challenges of in-car
software development process
2. Requirements for testing
3. TPT tool for automotive model-based
testing
4. Experience report
5. Future work
6. Summary and discussion
32
Experience
Initially developed in Daimler Software
Technology Research
In cooperation with many production vehicle
development projects
Future Work
Interaction with version and configuration
management
Interaction with test management
Product families
Model-based testing on integration levels
Relationship to component models
Utilization of architectural models
34
Summary
35
Discussion
Seems to be very useful in practice
Some important details are omitted, e.g.,
How to design and manage assessment scripts?
How difficult is it to build adapters?
Thank You!
37
Backup
38
In the automotive industry [the term MBT] is normally used to describe all
testing activities in the context of model-based development projects
39
Car
MiL
Test Rig
40
41