Skip to main content
Jump to: navigation, search

Papyrus/Oxygen Work Description/Refactoring/SequenceTimingCommunicationRefactoring


In order to allow customization of the sequence timing and communication diagrams as others, refactoring is needed.
It consists to connect the code of all 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, the task [1] has been implemented.
  • Specific element has been re-implemented, in order to be compatbile with the GMF generation, and element types :
    • Time Constraint
    • CombinedFragment and Interaction operand [2]
    • Action/behaviorExecutionSpecification [3]
    • Gates [4]
    • State Invariant[5]
    • DurationConstraint[6]
    • Duration Observation [7]
    • Interaction Use
    • Coregion
    • General Ordering
  • Some tests need to be fixed about
    • General ordering
    • DurationObservation
    • DurationConstraint
    • About some moves of messages
  • In this version, new features has 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 element in hte sequence diagram, a grid (use as referential) has been added in order to fix the folowing 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 new 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 taks 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 like aslo to implment Bug 507493 [Sequence Diagram] Lifelines should always be visually identifiable

Back to the top