Architecture Modeling - SPES 2020
Architecture Modeling - SPES 2020
Architecture Modeling - SPES 2020
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Architecture</strong> <strong>Modeling</strong><br />
computing capacity the SchedulerSlot receives from a Scheduler. In the role<br />
executionTime a Task can aggregate multiple declarations of its execution time,<br />
that has been measured/analysed. Provided a task would have exclusive access to a<br />
ComputingResource the execution time is the time from starting the task until it finishes.<br />
As the execution time may vary depending on the kind of the computing device, one can<br />
specify multiple execution times, each with a unique identifier. An example specification of an<br />
execution time, would be: {ARM7;500us;1ms}. Where 500us is the best base execution time<br />
and 1ms is the worst case execution time.<br />
RichComponent<br />
Resource<br />
+ isActive: Boolean<br />
+ isProtected: Boolean<br />
+ resMult: int [0..1] = 1<br />
Task<br />
ConcurrencyResource ProcessingResource SchedulerSlot<br />
+executionT ime<br />
SchedulerPort<br />
SchedulerRPort<br />
0..* +required<br />
0..*<br />
Constant<br />
ExecutionTimeSpec<br />
ComputingResource<br />
SchedulerPort<br />
SchedulerPPort<br />
+provided 0..*<br />
+ isPreemptible: Boolean = true<br />
Figure 3.14: Meta-model integration of the concept ComputingResource<br />
CommunicationResources: The concept CommunicationResource shown in Figure<br />
3.15 models an abstraction of a communication device of an execution platform<br />
capable of transferring information from one location to another. The attributes of<br />
CommunicationResource are used to describe its most relevant properties needed for<br />
timing analysis of a technical architecture. Being derived from ProcessingResource a<br />
CommunicationResource may be subject to scheduling of its communication capacity.<br />
A frame is a data item, which is transmitted by a CommunicationResource. The concept<br />
FrameTriggering models the triggering and identification of a frame transmitted by<br />
a CommunicationResource. As the concept is derived from ConcurrencyResource,<br />
it can be connected to a SchedulerSlot, thus using the communication capacity the<br />
SchedulerSlot receives from a Scheduler.<br />
SchedulerPort +required<br />
SchedulerRPort 0..*<br />
ConcurrencyResource<br />
FrameTriggering<br />
Resource<br />
Resource<br />
ProcessingResource<br />
+ transmMode: T ransmModeKind<br />
CommunicationResource<br />
SchedulerSlot<br />
Resource<br />
+ isPreemptible: Boolean = true<br />
+provided<br />
SchedulerPort<br />
0..* SchedulerPPort<br />
Figure 3.15: Meta-model integration of the concept CommunicationResource<br />
Describing data encapsulation in communication stacks: We consider the technical<br />
architecture as a network of ComputingResources, that are interconnected by<br />
means of CommunicationResources. The frames, that are transmitted by that<br />
CommunicationResources are however not the data items, that would be sent directly<br />
by some application task. Instead in most execution platforms an application programming<br />
25/ 156