eTrice comprises several models:
-
the ROOM model (*.room) — defines model classes and the logical structure of the model
-
Config model (*.config) — defines configuration values for attributes
-
Physical model (*.etphys) — defines the structure and properties of the physical system
-
Mapping model (*.etmap) — defines a mapping from logical elements to physical elements
In the following diagram the models and their relations are depicted. The meaning of the arrows is: uses/references.
In the following sections we will describe those models with emphasis of their cross relations.
The ROOM model defines classes for Data, Protocols, Actors, SubSystems and LogicalSystems.
Thereby the three latter form a hierarchy. The
LogicalSystem is the top level element of the structure. It contains references to
SubSystemClass elements. The
SubSystemClass in turn contain references to
ActorClass elements which again contain (recursively) references to
ActorClass elements. The complete structural hierarchy implies a tree which has the
LogicalSystem as root and where each reference stands for a new node with possibly further branches.
Let’s consider a simple example. It doesn’t implement any meaningful and completely omits behavioral and other aspects.
When a
LogicalSstem is instantiated then recursively all of the contained referenced elements are instantiated as instances of the corresponding class. Thus the instance tree of above example looks like this (the third line in the white boxes shows some mapping information, s.b.):
