Bug 513964 - [Tooling] Support implicit exclusion of pseudo-states
Summary: [Tooling] Support implicit exclusion of pseudo-states
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: readme
Depends on:
Blocks:
 
Reported: 2017-03-21 04:34 EDT by Peter Cigehn CLA
Modified: 2017-06-14 09:43 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cigehn CLA 2017-03-21 04:34:13 EDT 
To align with legacy tooling, implicit exclusion of pseudo-states is needed. 

Since pseudo-states are not redefinable in UML, and thus not excludable in UML-RT, the simple rule that if all incoming/outgoing transitions for a (inherited) pseudo-state is (explicitly) excluded, then that pseudo-state can be hidden from the state-machine diagram, in practice making it excluded.

If at least one of the incoming/outgoing transitions is re-inherited again, then the implicitly exluded pseudo-state is also (implicitly) re-inherited and is visualized (washed-out) in the state-machine diagram again.

This will reduce the graphical "clutter" with disconnected pseudo-states, and for the end-user this is "good enough" even if the pseudo-state itself is not explicitly excludable (in the semantic model).