implement full state machine explorer in derived capsules

Please change the implementation of the capsule state machine explorer in the Project Explorer so that it displays the entire state machine and its transitions in a derived capsule. The current implementation displays only the top level state or sub-states and transitions that have been overridden.

RSA RT offers a significant improvement over Rose RT with the state machine navigator that is contained inside the capsule explorer in the Project Explorer. It provides a very effective mechanism for exploring all the states and transitions associated with a state machine in one convenient view. By using the state machine navigator, the user can quickly locate states of interest and view the relevant transitions and their triggers. It is a much quicker and more efficient way to explore a state machine compared to navigation by drilling into the corresponding diagrams. It saves substantial time.

However, this convenience is lost when the user derives a capsule from another capsule that has a complex state machine. When you open the state machine explorer in the derived capsule, only the top level state is displayed: none of the sub-states and transitions are displayed. In order to navigate into the sub-states inherited by the capsule, the user is required to use the state diagram to create a State Machine diagram for all of the sub-states. This process becomes very time consuming and tedious for a complex state machine when the user is navigating to sub-states in order to override some behavior. The problem becomes greatly magnified when the user is implementing a framework that relies on inheriting a base state machine.

I assume that this representation was selected so that the user would be presented only with the state machine behavior that has been changed in the derived capsule. However, this could be also be viewed with the inheritance explorer. In general the representation of a state machine is sufficiently complex to justify a mechanism for navigating and viewing the entire state machine directly in every capsule regardless of inheritance. The ability to easily navigate and examine the state machine is the most important feature because it considerably enhances the productivity of the user. It's unfortunate that user is required to revert to the much less efficient technique of navigating a state machine through the state diagrams in the derived capsule. Most tools that support derived state machines provide an explorer for the entire state machine in the derived class, not just the changed behavior.