search

osate / osate-ge

Old Graphical editor for OSATE repository, kept for reference
6 stars 3 forks source link

Support for displaying the bindings between descendant software and execution platform components #197

Closed philip-alldredge closed 7 years ago

philip-alldredge commented 7 years ago

If the elements involved in the bindings are not shown in could be helpful to abstract out the bindings to show them as bindings between the containers. The graphical notation needs to be clear that what is being shown is not an actual binding declaration but a generalization of 1 or more bindings to subcomponents.

Include tooltips too.

See osate/osate2-core#773

philip-alldredge commented 7 years ago

Implemented in db341ff5f3bbf807cd577b41775dda41f2e213f4.

philip-alldredge commented 7 years ago

Implementation Details

The concept of “abstracted connections” was added during a previous task. These depict graphical relationships between model elements which do not have a 1 to 1 relationship with an AADL model element or do not display all the details of the model element that they represent. They have a different graphical presentation than the typical graphical connections from which they derive. One example of this is an AADL connection which references features inside of a feature group. If the AADL connection is enabled but the feature group’s contents are not enabled, the connection will be shown with the abstracted connection notation. This indicates to the user that there is a connection between the elements but that what is being shown does not contain all the details. A tooltip for the graphical connection will display details about the AADL connection.

It became apparent that this concept needed to be extended to bindings between model elements. Assume there is a subcomponent a.b being bound to c.d. If the diagram contains just subcomponents a and c, users were expecting a relationship to be shown between them. The solution that was developed will show an abstracted connection between a and c. Tooltips will show additional details. If the contents of a and c are enabled, the graphical connection will update accordingly. Additionally, if there are multiple bindings which would have identical graphical representations, these are represented as a single graphical connection. This capability works for all AADL reference properties rather than just binding related properties.