Author Topic: Copying diagrams without duplicating elements (Read 7682 times)

malmoth · « **on:** March 17, 2006, 11:41:07 am »

I'd like to be able to copy diagrams without duplicating the diagram elements.
That is when I draw use case scenarios with sequence diagrams. I'm used to copy the nominal scenario and modify it into an alternate scenario. At this state, I usally have only two lifelines (the user and the system). When I've copied the nominal scenario many times, I find myself with many instances of the system lifeline in the use case where I only need one lifeline linked to all the diagrams.
The deep copy provides the ability to copy every elements in a diagram. A light copy could just link the new diagram elements to the existing elements.

sargasso · « **Reply #1 on:** March 19, 2006, 03:39:44 pm »

Actually light and deep copies sort of exist at the moment. But they dont do what you want.

There is a way to (sort of) fake it though.

Lets say we want a "veryshallow" copy of diagram "Failed Test Process" in package "InnerProcesses".

1. In your WIP view (you do have a WIP view dont you?) create two packages SPIN and SPOUT (for Scratchpad in and out).

2. Drag the original "Failed test process" diagram into SPIN.

3. Context menu : "Copy diagram to Clipboard"

4 Click on SPOUT package and context menu: "Paste Diagram..."

5. Select "Shallow copy" and OK

SPOUT will now contain a diagram and the minimal set of elements EA considered are "Owned" by the diagram.

Clean it up and drag it to its desired home.

hth (sortof)
Bruce

malmoth · « **Reply #2 on:** March 20, 2006, 01:22:36 am »

Quote

1. In your WIP view (you do have a WIP view dont you?)

Nope

. I don't even know what a WIP view is. Could you enlighten me, please.

thomaskilian · « **Reply #3 on:** March 20, 2006, 02:26:43 am »

WIP = work in progress

sargasso · « **Reply #4 on:** March 20, 2006, 05:01:14 pm »

WIP is a view that I suggest everyone add to their model repository where you do the actual work of modelling. Its the draftsmans desk. When the model is complete then migrate the finished product to the proper pace in your formal model structure.

9 times out of 10 I find that I end up with several goes at modelling something (or trying to do something in EA

) By using a WIP structure if it doesn't work/ doesn't answer the question I can just delete the whole package without mucking up my formal model.

bruce

malmoth · « **Reply #5 on:** March 21, 2006, 12:03:44 am »

Quote

WIP is a view that I suggest everyone add to their model repository where you do the actual work of modelling. Its the draftsmans desk. When the model is complete then migrate the finished product to the proper pace in your formal model structure.

Well, I was used to work in a completly different model to try things in EA and reproduce the right procedure in my real model file. I'll try the WIP view.

Thanks.

malmoth · « **Reply #6 on:** March 21, 2006, 01:25:37 am »

Quote

SPOUT will now contain a diagram and the minimal set of elements EA considered are "Owned" by the diagram

I want to be sure I got it right. You mustn't delete the copied element in SPOUT ? Overwise, you diagram copy will be emptied ?
After some iterations, you SPOUT is full of unwanted elements, but you don't care because you're in the WIP view, right ?

Jan ´Bary´ Glas · « **Reply #7 on:** April 11, 2006, 05:47:41 am »

Not only WIP is usefull. I use RecycleBin to avoid deleting something I might need later.

thomaskilian · « **Reply #8 on:** April 11, 2006, 10:41:56 am »

That's true. I even call it Attic and very seldom clear the contents.

Sparx Systems Forum

News: