Activity Numbering - Best Practice?

[Guy Manning]

This is a bit of a newbie question...

Normally we number our activities in a flow to show the rough sequence (not sure if this is best practice or not...)

However, in EA, creating AS IS and TO BE diagrams, where Activity Elements are to be shared...pulling through an AS IS element onto the TO BE flow will include that number which now may NOT be correct in terms of the sequence.
So question is, what is best practice? use the EA sequence (as ordered in package and forget the numbering)?

Obviously if an Activity is the SAME for both flows I would prefer it to remain the same single entity for both.

Is there a better way of doing both maybe? using Alias in some way or other?

Ta
 
Guy

[Uffe]

Hi Guy,


Best practice for Activity reuse is actually not to reuse them in the way you describe, but to make Actions of them instead, one for each instance of reuse.

This way the "reused" elements are local to the diagram you're working in, so you can rename them, add/delete connectors and even delete the element itself without it affecting any other diagrams. From the Action you can also dive into the Activity's composite diagram, if it has one.

In terms of numbering, my general advice tends to be "don't bother", because you'll end up spending a lot of time managing the numbers themselves. If it's very important, then do it in a structured manner. Use a tagged value for the number, consider a hierarchical numbering scheme ("partition.activity") and set up some scripts or an Add-In to manage the renumbering.

Cheers,

/Uffe