| [mdt-papyrus.dev] TR: On participating in New Papyrus |
|
FYI De : Øystein Haugen
[mailto:Oystein.Haugen@xxxxxxxxx] Sebastien and Kenn Referring to our conversation in Santa Clara in December, I
am interested to continue trying to get involved in the project on the New
Papyrus. What we want to contribute are the following plugins /
competence. 1. Competence on the Sequence Diagram editor We have made the version now in Old Papyrus, but it is not
as stable there as it used to be on RSM6 (for several reasons), and we believe
that putting much more effort into Old Papyrus sequence diagram editor is not
very useful for us now even though we plan to use it for some courses in
industrial settings as proof of concept for executable UML. Rayner Vintervoll will do his Master work on editors for
graphical languages and would like to contribute to the work on sequence
diagram editor in New Papyrus. He was my assistant teacher in my course last
semester and has excellent knowledge of the Old Papyrus with SeDi. Could you send the links and contact points for how to
contribute most effectively on this? We understand that the responsibility for
sequence diagram editor in New Papyrus has been given to somebody in Spain. We
have no problem with trying to work together with them for mutual benefits, but
we need some contact points. 2. Plugin: Back-in-time debugger Jonas Winje has made a "back-in-time" debugger for
UML working on top of our JavaFrame runtime system. This debugger works on
modeling level and can work with Papyrus, but is quite independent from
Papyrus. The idea is that at any time the debugger can be invoked and
sufficient information stored about the selected set of state machines to run
the execution back and forth. The atomic step is the transition. This plugin
was used successfully in my course last semester. 3. Plugin: ConsistencyChecker Bjorn Brandshoi did his Master work on a plugin comparing
sequence diagrams and state machines to reveal inconsistencies. This, too, was
used with success in my course last year. He is now doing some improvements and
enhancements. This software is also well integrated with Old Papyrus, but is
logically independent from it as it works on the UML2 model as basis. Also for points 2 and 3 we would like to know what is the
adequate way to provide these as contributions to the open-source community. Regards, Oystein ---- Dr. Oystein Haugen Senior Researcher SINTEF |