Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A AADL_OPCUADDSGateway
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • FORA
  • AADL_OPCUADDSGateway
  • Wiki
  • Best Practice (Tips & Tricks)

Best Practice (Tips & Tricks) · Changes

Page history
Update Best Practice (Tips & Tricks) authored Apr 23, 2020 by dramsauer's avatar dramsauer
Show whitespace changes
Inline Side-by-side
Best-Practice-(Tips-&-Tricks).md
View page @ d9cdd9b2
......@@ -21,9 +21,9 @@ The package diagram provides a general overview of the existing model including
* 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.
In order 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.
In order 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.
![OSATE Open Diagram](uploads/bae0f8d4b18daa34019da5e5153ea898/OSATE_open_diagram.PNG)
......@@ -31,7 +31,7 @@ Once the package diagram was created, we get a graphical overview of the model.
![Package Diagram](uploads/f3554d03563822846cb16f53f36c8028/packageView.PNG)
To further inspect the implementation details of the system or a subcomponent for example, open the context menu of the intended component or system implementation, choose the “Open” label and select a diagram type of your choosing. Once the “Create New Diagram” window pops up, provide a diagram name and the specific diagram type to create the diagram.
In order to further inspect the implementation details of the system or a subcomponent for example, open the context menu of the intended component or system implementation, choose the “Open” label and select a diagram type of your choosing. Once the “Create New Diagram” window pops up, provide a diagram name and the specific diagram type to create the diagram.
![Open Implementation Diagram](uploads/9e51e8e8e86b998db2e8e6b6182ef583/open_implementation_diagram.PNG)
......
Clone repository
  • AADL Introduction
  • Best Practice (Tips & Tricks)
  • Problems
  • Home