Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Improvements regarding the Papyrus-RT Diagram support in EMF Compare

Using capsules in class diagrams is in MVP4 - Do it with class! - not yet assigned to a release (And MVPs may soon be replaced by something else).


Regards,

Charles Rivet
Senior Product Manager, Papyrus-RT product lead

On 2016-11-09, at 09:31 , Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

When it comes to which types of diagrams I suggest that you start focusing on the UML-RT Capsule Structure Diagram, and when more work has been done in the behavior modeling area that you look into the UML-RT State Machine Diagram. Those are basically the two major diagram types applicable for UML-RT.

There is also a third class-diagram-style of diagram, where you are able to show (customized) shapes for capsules and protocols, with dedicated compartments for attributes, operations, port and capsule parts respectively in, out, inOut protocol messages. Capsule parts and ports are visualized using the association notation between capsules and capsules respectively capsules and protocols. Of course you are able to show ordinary classes and relationships like generalization and dependencies in this diagram type. The implementation of this diagram type though is not started at all, and I am not sure to which MVP (if any yet) that this has been assigned.

When it comes to example models with structure and state-machine diagram types, I guess Charles have some models used for demoing in the Git repo. 

Charles, any suggestions?

/Peter Cigéhn

On 9 November 2016 at 14:25, Philip Langer <planger@xxxxxxxxxxxxxxxxx> wrote:
Hi,

we would like to start working on improving the Papyrus-RT diagram support in EMF Compare (e.g. grouping changes in diagrams, see also bug 507059). Therefore, I wanted to get your input on Papyrus-RT diagrams that we should use for testing.

Are there test diagrams available? Is there a source that you suggest for us to analyze in order to learn which diagram types will be used, which model elements will be placed on those diagrams typically, and thus which diagram changes may occur?

We'd like to systematically analyze those changes and derive a plan to address them.

Thanks a lot for your input!

Best wishes,

Philip

--
Dr. Philip Langer

Senior Software Architect / General Manager
EclipseSource Services GmbH

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


Back to the top