|
|
|
todo |
|
|
\ No newline at end of file |
|
|
|
First off, OSATE provides a textual and a graphical mode to create and modify component types and component implementations and to grant an overview of the system model. As the textual view may be rather useful for a more detailed modification of a components type or implementation, the graphical view gives a bright overview of the system model and allows developers to check the correctness of the system model as well as the communication between different component or system instances from a visual point of view for example. For this reason, AADL provides several different types of diagrams depending on the intended graphical representation of the model. Before a diagram for an AADL model exists, only two different types of diagrams can be created though:
|
|
|
|
* Package Diagram
|
|
|
|
* Custom Diagram
|
|
|
|
The package diagram provides a general overview of the existing model including subcomponent types and existing subcomponent implementations. The custom diagram also provides an overview of the model but without any subcomponents such that the model can be completely customized. Once a diagram was created, further diagrams related to subsystem or subcomponent types and implementations may be created. The following diagram types are at choice:
|
|
|
|
* Associated Diagram
|
|
|
|
* Custom Diagram
|
|
|
|
* Mode Diagram
|
|
|
|
* Processor Binding Diagram
|
|
|
|
* Structure Diagram
|
|
|
|
* Type Diagram
|
|
|
|
* Structure Diagram
|
|
|
|
* Mode Diagram
|
|
|
|
* Custom Diagram
|
|
|
|
* Implementation Diagram
|
|
|
|
* Custom Diagram
|
|
|
|
* Mode Diagram
|
|
|
|
* Processor Binding Diagram
|
|
|
|
* Structure Diagram
|
|
|
|
* Package Diagram |
