Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Oxygen Work Description/Refactoring/SequenceTimingCommunicationRefactoring"
m (Fixed links) |
|||
| Line 1: | Line 1: | ||
== Goals == | == Goals == | ||
| − | In order to allow customization of the sequence timing and communication diagrams | + | In order to allow customization of the sequence, timing and communication diagrams, refactoring is needed. |
| − | It consists | + | It consists in connecting the code of these diagrams on the element type framework. |
The code is also refactored in order to be more maintainable. | The code is also refactored in order to be more maintainable. | ||
===Sequence Diagram=== | ===Sequence Diagram=== | ||
| − | *In order to make it customizable, | + | *In order to make it customizable, task [https://bugs.eclipse.org/bugs/show_bug.cgi?id=489116] has been implemented. |
| − | * Specific element | + | * Specific element have been re-implemented, in order to be compatible with the GMF generation, and element types : |
** Time Constraint | ** Time Constraint | ||
| − | ** CombinedFragment and Interaction operand [ | + | ** CombinedFragment and Interaction operand [https://bugs.eclipse.org/bugs/show_bug.cgi?id=514836] |
| − | ** Action/behaviorExecutionSpecification [ | + | ** Action/behaviorExecutionSpecification [https://bugs.eclipse.org/bugs/show_bug.cgi?id=482411] |
| − | ** Gates [ | + | ** Gates [https://bugs.eclipse.org/bugs/show_bug.cgi?id=515375] |
| − | ** State Invariant[ | + | ** State Invariant[https://bugs.eclipse.org/bugs/show_bug.cgi?id=489116] |
| − | ** DurationConstraint[ | + | ** DurationConstraint[https://bugs.eclipse.org/bugs/show_bug.cgi?id=489116] |
| − | ** Duration Observation [ | + | ** Duration Observation [https://bugs.eclipse.org/bugs/show_bug.cgi?id=489116] |
** Interaction Use | ** Interaction Use | ||
** Coregion | ** Coregion | ||
| Line 27: | Line 27: | ||
** About some moves of messages | ** About some moves of messages | ||
| − | *In this version, new features | + | *In this version, new features have been added: |
| − | ** Bug 487501 - [SequenceDiagram] Cannot move messages easily leading to poor usability <span style="color:orange">To verify</span> | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=487501 Bug 487501] - [SequenceDiagram] Cannot move messages easily leading to poor usability <span style="color:orange">To verify</span> |
| − | ** Bug 507409 - [SequenceDiagram][Usability] Automatic creation of execution specification when creating a message <span style="color:#01F801">Done</span> | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507409 Bug 507409] - [SequenceDiagram][Usability] Automatic creation of execution specification when creating a message <span style="color:#01F801">Done</span> |
| − | *In order to manage | + | *In order to manage elements in the sequence diagram, a grid (use as referential) has been added in order to fix the following tasks: |
| − | ** Bug 507348 - [Sequence Diagram][Usability] Differentiate between move and reorder in sequence diagrams <span style="color:orange">To verify</span> | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507348 Bug 507348] - [Sequence Diagram][Usability] Differentiate between move and reorder in sequence diagrams <span style="color:orange">To verify</span> |
| − | ** Bug 508193 - [SequenceDiagram] Ensure consistency between semantic and notation model for messages <span style="color:orange">To verify</span> | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=508193 Bug 508193] - [SequenceDiagram] Ensure consistency between semantic and notation model for messages <span style="color:orange">To verify</span> |
| − | ** Bug 507525 - [SequenceDiagram] Minimal space between elements <span style="color:orange">To verify</span> | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507525 Bug 507525] - [SequenceDiagram] Minimal space between elements <span style="color:orange">To verify</span> |
| − | ** Bug 507501 - [SequenceDiagram] Moving several elements together <span style="color:orange">To verify</span> | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507501 Bug 507501] - [SequenceDiagram] Moving several elements together <span style="color:orange">To verify</span> |
| − | **'''These tasks will be valited by us in the | + | **'''These tasks will be valited by us in the next few days.''' |
* Work in progress | * Work in progress | ||
| − | ** Bug 507472 - [SequenceDiagram] Dissociate Message sort and Message kind in the palette | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507472 Bug 507472] - [SequenceDiagram] Dissociate Message sort and Message kind in the palette |
| − | ** Bug 507476 - [SequenceDiagram] Automatic creation of reply message | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507476 Bug 507476] - [SequenceDiagram] Automatic creation of reply message |
| − | *Next | + | *Next tasks in next days before M7 |
| − | ** Bug 507365 - [Sequence Diagram][Usability] Split the single Message Async tool into one for asynchCall and one for asynchSignal | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507365 Bug 507365] - [Sequence Diagram][Usability] Split the single Message Async tool into one for asynchCall and one for asynchSignal |
| − | ** Bug 447889 - [SequenceDiagram] automatic creation of BES on source lifeline for sync msg | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=447889 Bug 447889] - [SequenceDiagram] automatic creation of BES on source lifeline for sync msg |
*Next tasks after M7: | *Next tasks after M7: | ||
| − | **Bug 508184 - [SequenceDiagram] Start and finish of execution specification must be in same interaction operand | + | ** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=508184 Bug 508184] - [SequenceDiagram] Start and finish of execution specification must be in same interaction operand |
| − | ** we would like | + | ** we would also like to implement [https://bugs.eclipse.org/bugs/show_bug.cgi?id=507493 Bug 507493] [Sequence Diagram] Lifelines should always be visually identifiable |
Latest revision as of 11:06, 10 May 2017
Goals
In order to allow customization of the sequence, timing and communication diagrams, refactoring is needed. It consists in connecting the code of these diagrams on the element type framework. The code is also refactored in order to be more maintainable.
Sequence Diagram
- In order to make it customizable, task [1] has been implemented.
- Specific element have been re-implemented, in order to be compatible with the GMF generation, and element types :
- Some tests need to be fixed about
- General ordering
- DurationObservation
- DurationConstraint
- About some moves of messages
- In this version, new features have been added:
- Bug 487501 - [SequenceDiagram] Cannot move messages easily leading to poor usability To verify
- Bug 507409 - [SequenceDiagram][Usability] Automatic creation of execution specification when creating a message Done
- In order to manage elements in the sequence diagram, a grid (use as referential) has been added in order to fix the following tasks:
- Bug 507348 - [Sequence Diagram][Usability] Differentiate between move and reorder in sequence diagrams To verify
- Bug 508193 - [SequenceDiagram] Ensure consistency between semantic and notation model for messages To verify
- Bug 507525 - [SequenceDiagram] Minimal space between elements To verify
- Bug 507501 - [SequenceDiagram] Moving several elements together To verify
- These tasks will be valited by us in the next few days.
- Work in progress
- Bug 507472 - [SequenceDiagram] Dissociate Message sort and Message kind in the palette
- Bug 507476 - [SequenceDiagram] Automatic creation of reply message
- Next tasks in next days before M7
- Bug 507365 - [Sequence Diagram][Usability] Split the single Message Async tool into one for asynchCall and one for asynchSignal
- Bug 447889 - [SequenceDiagram] automatic creation of BES on source lifeline for sync msg
- Next tasks after M7:
- Bug 508184 - [SequenceDiagram] Start and finish of execution specification must be in same interaction operand
- we would also like to implement Bug 507493 [Sequence Diagram] Lifelines should always be visually identifiable