Page History
| Warning |
|---|
This page is not completed yet. |
| Panel | ||||
|---|---|---|---|---|
| ||||
Responsible:
|
...
To work with C2DF you must be passed pass as the first source and a destination directory as an argument. C2DF generates then in the target directory for each annotated source file from the source directory or a subdirectory thereof a .KAOT-file. Also, a subdirectory called xml will be created in the target directory. This have to be deleted.
...
Labels can hold all characters, except quotation marks, commas, semicolons, at sign, asterisk asterisks with a backslash and backslashes with a asterisk.
...
Specification of data flows:
The specification of the data flows of an actor must be initiated by the keyword link:. Then follows the list of the data flows.
...
The ID of the source and the ID of the target
...
must be specified for each entry. Source and destination are separated by a right-leaning arrow indicating the direction of data flow. If source or destination are defined in
...
another actor
...
as the data flow, then the ID of the actor of the source or destination must be
...
specified. The ID of the actor is placed directly in front of the ID of the source or target, separated by a dot. Actors, in which source and destination are defined, may not differ by more than one hierarchical level. Other entries are separated with commas. The list of all data flows must be terminated with a semicolon.
| Code Block | ||
|---|---|---|
| ||
link: source -> context.target, context.source -> context.target, source -> target, ... ; |
...
The specification of the included actors of an actor must be initiated by the keyword content:. Then follows Followed by the list of the included actors. Each entry must be specified with the name of its represented function name in the source code. Followed by a unique ID in within the actor, which is separated from the function name with a colon. Optional behind the ID can be any label in quotation marks. Other entries are separated with commas. The list of all included actors must be terminated with a semicolon.
...
Specifying top-level actors:
The specification of the top-level actors of a data flow diagram must be initiated by the keyword toplevel:. The specification must be placed in the annotation of the represented function. The entry consists of an unique ID in the actor. Optional behind the ID can be any label in quotation marks. The entry must be terminated with a semicolon.
| Code Block | ||
|---|---|---|
| ||
toplevel:ID "label"; |
Special case:
It is possible to force data flows in contrary to the general specifications . This is particularly the case when there are multiple top-level actors. The specification of data flows between these actors is set to the specifications of other data flows. For the specification, all predecessors of the actor and the actor itself, which define the source and target, must be specified by IDs. For the specification the path to the source and to the destination must be specified. Both are separated by a right-leaning arrow. A path consists of the ID of the source (or destination) and the ID of the actor, in which it is defined, and the IDs of all textual comprehensive actors. The ID of the defining actors is placed in front of the ID of the source (or destination) and separated by a colon. The IDs of the textual comprehensive actors, are arranged in descending order, placed in front of the ID of the defining actor. The IDs of all actors in the path are separated
by underscores anotherfrom each other by an underscore . Source and destination can differ in more than one hierarchical level. All characters that are replaced with underscores in an ID must also be replaced with underscores in the specifying.
| Code Block | ||
|---|---|---|
| ||
link: source -> ID0_ID1_ID2_..._ID:target, ... ; |
kann
Overview
Content Tools