Recent changes to FileFormat

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Mon, 30 Jun 2014 03:02:32 -0000

--- v9
+++ v10
@@ -1,6 +1,6 @@
 File Format
 ==========
-The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml). A specification is defined by the 4 parts architecture, application, mappings and routings.
+The Schedule Visualization tool expects the specification or schedule in XML format. It is based on [OpenDSE](http://opendse.sourceforge.net/). An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml). A specification is defined by the 4 parts architecture, application, mappings and routings. The OpenDSE framework allows to generate specifications in JAVA.

 Architecture
 ----------

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 06:31:02 -0000

--- v8
+++ v9
@@ -20,4 +20,4 @@
 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.
+**Note:** Defining routings is currently not necessary and simply defining empty routings is sufficient.

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 06:29:39 -0000

--- v7
+++ v8
@@ -20,3 +20,4 @@
 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.

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 04:14:53 -0000

--- v6
+++ v7
@@ -11,7 +11,7 @@
 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 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
 -----------

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 04:13:18 -0000

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 03:57:47 -0000

--- v4
+++ v5
@@ -1,17 +1,17 @@
 File Format
 ==========
-The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml). An specification is defined in the 4 parts architecture, application, mappings and routings.
+The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml). A specification is defined by the 4 parts architecture, application, mappings and routings.

 Architecture
 ----------
-Defines the resources like 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.
+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 task.
+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.

 Mappings
 -----------
@@ -19,4 +19,4 @@

 Routings
 -----------
-Additionally routings might be defined for each message. Defining the bus it is transmitted on as well as sender and receiver resources.
+Additionally, routings might be defined for each message. Defining the bus it is transmitted on as well as sender and receiver resources.

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 03:55:01 -0000

--- v3
+++ v4
@@ -1,15 +1,22 @@
 File Format
 ==========
-The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml).
+The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml). An specification is defined in the 4 parts architecture, application, mappings and routings.
+
+Architecture
+----------
+Defines the resources like 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
 ----------
-
-Architecture
-----------
+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 task.

 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.

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 03:37:19 -0000

--- v2
+++ v3
@@ -1,6 +1,6 @@
 File Format
 ==========
-The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here]().
+The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here](http://sourceforge.net/p/schedulevisualization/wiki/FileFormat/attachment/example.xml).

 Application
 ----------

FileFormat modified by Florian Sagstetter

Florian Sagstetter — Thu, 19 Jun 2014 03:36:15 -0000

--- v1
+++ v2
@@ -1,5 +1,6 @@
 File Format
 ==========
+The Schedule Visualization tool expects the specification or schedule in XML format. An example specification can be found [here]().

 Application
 ----------