FileFormat

File Format

The Schedule Visualization tool expects the specification or schedule in XML format. It is based on OpenDSE. An example specification can be found here. A specification is defined by the 4 parts architecture, application, mappings and routings. The OpenDSE framework allows to generate specifications in JAVA.

Architecture

Defines the resources, i.e., nodes and buses. A resource is defined by its unique id. Links establish connections between resources, i.e., commonly node resources are linked to a bus resource.

Application

Defines tasks and messages as task and communication, respectively, each with a unique id.
Each task and communication can have a user-defined set of attributes of which the tool requires the execution time and a period. The tool allows to define the attribute name in its settings. In the example, "e" and "p" represent the execution time and the period, respectively.
If a schedule should be predefined, additionally the start-time needs to be defined for each task and message, here denoted as "st".
To reflect task and message data-dependencies, dependency allows to define relations between tasks and messages. To define attributes for tasks and messages sharing data-dependencies, function allows to define attributes for connected tasks and messages by providing an anchor to one of the tasks. To generate schedules a maximal end-to-end delay needs to be defined for each function, here denoted as "maxdelay".

Mappings

Define a task and communication mapping to resources. A mapping has to be defined for each task and message.

Routings

Additionally, routings might be defined for each message. Defining the bus it is transmitted on as well as sender and receiver resources.
Note: Defining routings is currently not necessary and simply defining empty routings is sufficient.