09.08.2013 Views

Architecture Modeling - SPES 2020

Architecture Modeling - SPES 2020

Architecture Modeling - SPES 2020

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Architecture</strong> <strong>Modeling</strong><br />

of the logical perspective to elements of the technical perspective results in a hardwaresoftware<br />

partitioning.<br />

Geometrical perspective In the geometrical perspective(↑) the physical layout of the system<br />

is considered. While in the technical perspective some resource is modelled in terms of<br />

its properties, its interfaces and its behaviour, in the geometrical perspective its spatial dimensions<br />

are modelled. The geometrical perspective deals for example with cable lengths<br />

and space limitations.<br />

The concept of different perspectives and abstraction levels is inspired by partitions of EAST-<br />

ADL abstraction levels [6] and meetings with industrial partners of the <strong>SPES</strong><strong>2020</strong> project. Taking<br />

a look at EAST-ADL one can see that one distinct EAST-ADL architecture level is split<br />

into different perspective models: The Design Level contains a Functional Design <strong>Architecture</strong><br />

as well as a Hardware Design <strong>Architecture</strong>. We generalized that concept by means of the<br />

perspectives allowing the partitioning of architectures in each level of abstraction.<br />

The entities and their interfaces defined in different perspectives do not need to be compatible<br />

to each other. For example, three interacting functions defined at the functional perspective<br />

may be modelled as two components in a logical perspective. The palette of actually used<br />

perspectives can be different at each abstraction level. In early design stages for example, when<br />

the functions of the system are to be defined, the target platform (modelled in the technical<br />

perspective later on) need not necessarily be of interest.<br />

2.3 Heterogeneous Rich Components<br />

The meta-model of Heterogeneous Rich Components (HRC), which originates from the European<br />

SPEEDS project [42], constitutes the core of the architecture meta-model proposed in<br />

<strong>SPES</strong>. This section gives a short introduction into its concepts.<br />

2.3.1 Component Model<br />

The paradigm of component-based design is well established and used in many different application<br />

domains. In standards like EAST-ADL [6] and AUTOSAR [9], a component is the basic<br />

design-entity structuring any model. A component(↑) has a well defined interfaces and is the<br />

Component<br />

Port<br />

C1<br />

aspect<br />

specification<br />

aspect<br />

realization<br />

conforms<br />

to<br />

Figure 2.5: Components, aspect specification and realization<br />

basic entity of any model. The interfaces allow to abstract from the internals of a component<br />

and to reuse it in different design contexts. The notion of components can be established independently<br />

of any design domain. That is, a component can model a reusable piece of software,<br />

9/ 156

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!