Information Technology Reference
In-Depth Information
2
Proposed Methodology
Taking into account the current design and properties of state-of-the-art de-
velopment in the automotive domain (such as ISO 26262 and RESPONSE 3
Code of Practice
[8]), DeSCAS has developed a methodology for the devel-
opment of assistance and automation systems. In addition to interweaving
interdisciplinary development activities of the automotive domain by rea-
soning about domain knowledge, a formal base is essential for the DeSCAS
process framework. Most of the state-of-the-art standards lack a formal rep-
resentation as they primarily consist of glossary-based, natural language text
descriptions, informal checklists or questionnaires, complemented by some
graphics and tables. As a consequence, inconsistencies concerning both the
use of technical terms and the dependencies between process elements be-
come visible when analyzing these standards in terms of a formal definition.
The nomenclature is partially unclear or even ambiguous, as are some con-
nections between process elements and requirements [3]. For that reason, the
process model as part of the entire DeSCAS process framework builds upon
a generic and formally defined process meta-model.
2.1
Interweaving Development Streams
The essential parts of the DeSCAS meta-model are constituted by the
devel-
opment streams
which combine related design activities of an interdisciplinary
system development to be synchronized via iterations within a V-Model. Con-
cerning the development of AAS in the automotive domain, the DeSCAS
process model defines the following three main development streams:
1.
Human factors
: Continuously involving human behavior and interaction
with the system during system development (see RESPONSE 3
Code of
Practice
).
2.
Functional development and architecture
: The classical hardware and
software development of AAS is highly affected by the other two streams.
3.
Safety measures
: Compliance with standards such as ISO 26262 is in-
evitable for ensuring the functional safety of safety critical systems.
Interweaving these three development streams represents the interdisciplinary
collaboration during the design of AAS. A detailed description of the DeSCAS
process model and its process meta-model can be found in [4]. The knowledge
deduction within the streams
functional development and architecture
and
safety measures
will be focused in the following by means of an example
application.
2.2
Formalization of Domain Knowledge
Each development stream of the DeSCAS process model comprises stream-
specific ontologies which precisely capture knowledge and expertise within a
