| ... | ... | @@ -20,3 +20,9 @@ The package diagram provides a general overview of the existing model including |
|
|
|
* Processor Binding Diagram
|
|
|
|
* Structure Diagram
|
|
|
|
* Package Diagram
|
|
|
|
|
|
|
|
To get a precise definition on each specific diagram type, one should look up the OSATE AADL specification on diagram types, as these are not discussed in detail in this wiki. From a practical point of view, the package diagram and the implementation diagram/structure diagram are the most useful, as the package diagram allows a bright overview of a model and its components while the implementation diagram/structure diagram also shows the internal composition of components and their connections (connections between features, connections to subcomponents, information control flow, etc…). The sub bullet points of the diagram listing indicate that if the creation of an associated diagram was selected, one of the four possible diagram types (custom diagram, mode diagram, processor binding diagram or structure diagram) may be created for example.
|
|
|
|
|
|
|
|
To initially create a package diagram for an AADL model called “overview.aadl” for example, select the “Open Diagram” label or the “Create Diagram…” label inside the context menu, choose a name for the diagram and select “Package Diagram” from the drop-down menu which creates a package diagram for the selected model.
|
|
|
|
|
|
|
|
 |
|
|
\ No newline at end of file |
