| Re: [papyrus-rt-dev] Improvements regarding the Papyrus-RT Diagram support in EMF Compare |
Hi,When it comes to user requirements regarding this, I guess the best we have so far is the Work Package I have written in Tuleap: https://forge.ericsson.net/plugins/tracker/? aid=11037 I do know that we have one Work Item (formulate as a user story) also https://forge.ericsson.net/plugins/tracker/?aid=6819 But apart from that I do not think that we have anything more defined (since it has so far been very low attention on this diagram type).Getting back to Philips original question, I still think that the initial focus for Philip's work should be on the UML-RT Capsule Structure Diagram, followed by the UML-RT State Machine Diagram.Since we have not even started with the work of customizing the "class diagram"-style diagram, it would possibly be some waste of time (and probably also confusion) if the ordinary Papyrus UML class diagram behaves differently, e.g. with respect to the visualization of compartments for capsule and protocols, including the lack of support for visualizing ports and capsule parts, the I am just afraid that we "do the wrong things" in the customization of EMF Compare if we base the work on the wrong diagram type./Peter CigéhnOn 9 November 2016 at 20:07, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote: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!On 2016-11-09, at 11:21 , Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote: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______________________________On 9 November 2016 at 17:13, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:In addition to UML-RT Capsule Structure Diagrams and UML-RT State Machine Diagrams, I expect people will use Class Diagrams. I use them, in particular to specify Generalization and Dependency relations.In the git repo, under the 'models' folder you'll find several examples. The ones under models/tests are intended to be tests, mainly used by codegen (I don't know if anyone else is using them), but it includes more basic examples, and patterns, i.e. not quite what an actual user would create. Under models/samples you should find some more "realistic" models, but I think those have been created mostly with older versions of Papyrus-RT, so the diagrams may still be the old ones.Charles can describe these models better.--Ernesto PosseZeligsoftOn Wed, Nov 9, 2016 at 9:31 AM 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
_______________________________________________
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
_______________________________________________
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