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.

3.2.2 Functional Perspective<br />

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

<strong>Modeling</strong> the functional perspective of the system serves identifying the functional needs of the<br />

system. Derived from an analysis of the operational context of the system in the Operational<br />

Perspective, its behavior is specified from a user-centric point of view, establishing a blackboxview<br />

of the functions of the system. Subsequently these top-level functions are refined by<br />

sub-functions that together realize the top-level system functionality. Ideally, functions are<br />

completely independent of any architecture.<br />

Elements of an operational model defined at the same or a higher abstraction level can be<br />

allocated on the defined functions. This way, the contribution of a function to an activity of<br />

an actor can be explicated, which allows to investigate whether each activity is supported by<br />

system-functions, and whether the design goals can be accomplished.<br />

+part 0..*<br />

RichComponentProperty<br />

+component 1<br />

+type<br />

«isOfT ype» 1<br />

RichComponent<br />

Function<br />

+aspect<br />

SystemArtefact Aspect<br />

Requirement<br />

+ rationale: String [0..*]<br />

SystemRequirement<br />

0..*<br />

+stakeholder<br />

0..*<br />

Stakeholder<br />

Figure 3.6: Meta-model integration of the concepts for specifying the functional perspective<br />

The architecture meta-model provides the concept of a Function (see Figure 3.6) to model<br />

functions of the system. Function is a specialized RichComponent and thus can have<br />

behavior. Inputs and outputs of a function are represented by ports. Functional as well as<br />

non-functional specifications are defined and assigned to the modelled functions by means of<br />

SystemRequirements (contracts).<br />

3.2.3 Logical Perspective<br />

The logical perspective constitutes the decomposition of a system into reusable components<br />

and specifies their interaction. Additionally, the environment is modelled with respect to the<br />

interfaces of the system, which includes both syntactical interfaces and behavioral interaction.<br />

That way, the logical parts of the system and their relationships are identified. Technical aspects<br />

and choices of any technology are typically not considered in the logical perspective. The<br />

logical perspective is the entry to the design of the system. Functions modelled within the<br />

functional perspective can be spread across the defined logical components.<br />

Logical components of a system are modelled by the architecture meta-model concept<br />

LogicalComponent (see Figure 3.7). LogicalComponent is a specialized<br />

RichComponent, and thus can have behavior. Ports typed by PortSpecifications<br />

specify the interaction points of the component. Functional as well as non-functional requirements<br />

can be formulated as SystemRequirements. A LogicalComponent can<br />

be instantiated in a given context of other component instantiations by using the concept<br />

RichComponentProperty. The behavior of the component instance is determined by its<br />

type.<br />

The concepts EnvironmentComponent models a component of the environment interacting<br />

with the System. Conceptionally an actor is also part of the environment.<br />

19/ 156

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

Saved successfully!

Ooh no, something went wrong!