Using a Domain Model to Precisely Describe function ...

Using a Domain Model to Precisely Describe function-agnostic Electric/Electronic – Architectures Lisa Braun, Michael Armbruster, Ludger Fiege, Eric Sax © istockphoto.com/nadla

…the way from functional to non-functional model – based design Challenges of extensible e/e-architectures

Semi – formal domain model approach

Functional requirements are no longer well-defined at the time of development as apps could be added later

Hierarchic decomposition of the e/e-architecture based on nine architectural layers

The separation of function, runtime environment and hardware breaks the existing dependency of physical structures and functional connections

Core of the model: distinction of level VII e/e-platform and level VI network to describe functions separately from a function-agnostic Computing Platform

Cross-functional, nonfunctional properties like failoperational characterize the design

Timing and integrity of the platform is configurable and assessable independent of specific functions

Consequences for model – based design

Benefit of new model approach

Models must allow to describe a function-agnostic computing platform besides of automotive functions

Support the design of a function-agnostic platform as Safety Element out of Context (ISO26262)

The physical structure can no longer be derived from the previously defined set of functional requirements

Allows a structured, semi-formal description of the e/e-architecture independent of functional requirements