(4 slides per page) - Updated

Overview
Phase 10
Phase 11
Phase 12
Introduction
Procedure
Summary
Overview
Phase 10
Phase 11
Phase 12
Summary
Remarks
The acceptance test should not be done by the developer.
The test environment can be developed in parallel to the
last phases.
The test environment has to interact with the external
interfaces of the machine. Hence the technical interfaces
also consist of hardware.
What do we gain by defining such a process? II
Various possibilities for tools support:
UML tools available.
Tool for generating sequence diagrams available.
Model checker for UML state machines available.
Other tools conceivable.
Component-based development is supported.
Hardware as well as software components can be part of
the developed system (machine).
Specific attention is paid to the analysis phase and the
modeling of the environment. (Environment models yield
test cases.)
Non-functional (quality) characteristics can be taken into
account (in particular, safety and security; by specific
architectures and problem frames).
85 / 89
87 / 89
Overview
Phase 10
Phase 11
Phase 12
Summary
Overview
Phase 10
Phase 11
Phase 12
Summary
What do we gain by defining such a process? I
Sequence of well-defined steps helps developers to focus
attention on relevant parts of the task (and fake a rational
design process ;-).
Developed models and their interrelations can be checked
in each step.
Validation is integral part of the process:
Validationconditionsaredefinedforeachstep.
Systematic test case generation is part of the process.
Certification according to safety- and security standards
(IEC 61508 and Common Criteria) is supported.
What do we gain by defining such a process? III
Systematic evolution of existing systems is supported
(traceability links between different models / documents).
Problem decomposition is performed explicitly and
systematically. Relations between subproblems are
exploited to compose partial solutions of subproblems.
Using patterns in various phases support re-use of existing
knowledge and (partial) automation:
Problem Frames for analysis
Architectural patterns for software design
Code patterns for implementing state machines
Process emerged from industrial practice, uses
well-established languages and techniques. Hence, no
ivory-tower invention.
86 / 89
88 / 89