Defining a Task Architecture

In AutoFOCUS3, a Component Architecture is used to define a system's logical architecture and its behavior in an implementation independent way in the logical viewpoint. The Task Architecture is part of the technical viewpoint and allows to specify the entities to which the components of a logical architecture are mapped during the deployment to an execution platform.

To create an empty Task Architecture, at least one Component Architecture must exist in the project. Then, open the context menu of the project and select Task Architecture.

To model the constituent Tasks of a task architecture, drag them from the Model Elements library to the task architecture. The interface of tasks is defined using either of the following ports:

In order to model the data flow between tasks, task ports can be connected using Signals by means of a left-drag while the ALT key is pressed. The following constraints apply:

In order to define a mapping of one or more logical Components to a Task (n:1), a Components-to-Tasks allocation must be added. It also allows to define the mapping of logical ports to task ports.

AutoFOCUS3 provides an automatic transformation from a Component Architecture to a Task Architecture that associates every Component to exactly one Task. The transformation also generates the corresponding 1:1 Components-to-Tasks allocation.

In order to define the platform-specific attributes of tasks, a hardware platform architecture and a corresponding Task-to-Hardware allocation must be present that (it may be empty). First, the Task-to-Hardware has to be selected

and the task architecture editor has to be restarted.

Then, the following attributes can be defined in the corresponding tabs of the editor.