Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: SomersetGraham on January 07, 2014, 10:21:04 pm
-
Hi
I have a large sequence diagram and am looking for a way to split it into several smaller diagrams
Is there an easy way to achieve this?
Thanks
-
I would try to copy the diagram and then remove the unwanted parts.
You might have to experiment a bit with the copy/paste options of diagrams (deep, shallow, smart) to make sure the result is what you need.
Geert
-
ok thanks
-
for splinting the sequence diagram you can use concept of "interaction ".
here you can divide the seuance diagram base on the function call. please follow below steps.
- Decide the function which has generated biggest flow.
- make a smart copy of diagram.(i.e. Copy_Dia).
- Delete decided function from original diagram.
- Delete any other connectors form copy_Dia.
- now , in original diagram right click and select new Element or Connector > Interaction
- Place this interaction box at the place where decided function flow must happen.
- now select and right click on interaction. then select New Child Diagram > composite
- then from browser window select the copy diagram
- click OK.
cheers !
your diagram is now divided in two parts. when you click on created interaction , other diagram will be opened.
if you want more splittings follow same steps every time.
:)
-
I split the interaction into several manageable interaction (sequence) diagrams.
Then to refer to one my "lower level" diagrams.
Drag the diagram to be referred to onto the "higher level" diagram and select "Interaction Occurrence"
This creates a rather ugly floating box linked to the "lower level" diagram
Right click this Interaction Occurrence" and select "Advanced > Show as Timeline" from the menu
You now have a lifeline with the heading ref the "lower level" diagram name, which you can send and receive messages to / from (as per usual lifeline). Double-clicking this drills down the levels.
You can refer to the same "lower level" diagram more than once on the "higher level" diagram if required
Phil