You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visualization and editing of behavior annex state automata, except for expressions.
The high-level state machine will be displayed and edited in the OSATE graphical editor alongside other AADL model elements. Behavior specifications will be represented by a behavior diagram element. Like other model elements, the user will be able to set the “in modes” clause and other attributes using the Eclipse Properties view. States, transitions, and variables will be represented inside the behavior specification element.
The label for behavior specification diagram element will be based on the containing classifier and the mode(s) to which they apply. If the diagram element is contained within a classifier, the label may be shortened to avoid redundancy.
A Behavior Specification diagram type will be introduced which will show states and transitions by default.
Additionally, adjust setup to stop hiding the org.osate.ge.ba project and start including it with OSATE.
Ensure copy and pasting works for BA elements.
The text was updated successfully, but these errors were encountered:
Added initial support for visualizing and editing behavior annex. Closes#2130
Co-authored-by: Ryan Mcilnay <rm0016@uah.edu>
Co-authored-by: Lutz Wrage <lutz.wrage@gmail.com>
Visualization and editing of behavior annex state automata, except for expressions.
The high-level state machine will be displayed and edited in the OSATE graphical editor alongside other AADL model elements. Behavior specifications will be represented by a behavior diagram element. Like other model elements, the user will be able to set the “in modes” clause and other attributes using the Eclipse Properties view. States, transitions, and variables will be represented inside the behavior specification element.
The label for behavior specification diagram element will be based on the containing classifier and the mode(s) to which they apply. If the diagram element is contained within a classifier, the label may be shortened to avoid redundancy.
A Behavior Specification diagram type will be introduced which will show states and transitions by default.
Additionally, adjust setup to stop hiding the
org.osate.ge.ba
project and start including it with OSATE.Ensure copy and pasting works for BA elements.
The text was updated successfully, but these errors were encountered: