Peter,
Could you please point us to the user requirements as to what users need to see in a “class diagram” like visualization of capsules, ports, protocols, capsule parts, etc., and the action they are expected to take on such a diagram?
If this already exists as a set of user stories, that would be even more useful as the reason behind each would also be provided.
Thank you!
Regards,
Charles Rivet Senior Product Manager, Papyrus-RT product lead
Hi Ernesto,
I think that we really should look into this about "class diagram"-style. I expect that we will have customized version of class diagram for these kinds of diagrams. We have discussed this before Ernesto, and I feel that we go in the wrong direction if we use ordinary Papyrus UML class diagrams (since they do not support what we need from these diagram, like the visualization of port and capsule parts). Sure you can use them for generalization and dependency, but then we will "fool" people into using the wrong diagram type (as a short term solution they could probably be used).
If we have such a strong need for class diagram style of diagrams, then we should really plan for the introduction of this new diagram type in Papyrus-RT.
/Peter Cigéhn
_______________________________________________ papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|