BPMN Model folder structure

[slowlearner]

Hi, I have never understood the folder structure that EA creates when I generate a new model.
For example, when I create a new BPMN2 Process model, it generates the following hierarchy:

BPMN 2.0 Business Process View (Package)
__ <<Business Process>> BPMN 2.0 Business Process View
____ diagram and sample elements follow

I don't understand the 2nd level.  What purpose does it serve?  Any help much appreciated, or if you can point me at the relevant documentation.

Thanks, Rainer

[Eve]

The second level is the process as defined in the BPMN specification. The nested diagram and contents are where you define how that process is performed. The top level is just a container required by the EA model pattern architecture. Generally speaking I would have multiple processes in one package. It would also generally hold the global types that are used by those processes.

[slowlearner]

Thanks for the clarification Simon.  Sometimes it just needs to be spelt out for me.   

[OpenIT Solutions]

Hi,

I think I'd qualify Simons advice. If you are creating a small (less than 10 diagrams) process mode,l then fine put everything in a single folder. If however you are documenting the processes for a medium to large business, you should think about using a Process Classification Framework (PCF) (see APQC for example) and creating a folder structure based on the PFC. I'd also recommend that you create a separate folder(s) for any elements that are reused across your model. Finally I'd recommend having a look at this webinar on the Sparx site:

http://www.sparxsystems.com/resources/webinar/partners/bpmn/bpmn-enhancements-cephas.html

Which gives a good overview on Sparx BPMN modelling.

[Eve]

I think I'd qualify Simons advice. If you are creating a small (less than 10 diagrams) process mode,l then fine put everything in a single folder. If however you are documenting the processes for a medium to large business, you should think about using a Process Classification Framework (PCF) (see APQC for example) and creating a folder structure based on the PFC. I'd also recommend that you create a separate folder(s) for any elements that are reused across your model.

Absolutely, I wouldn't recommend to put every process in the same package.  Equally, when managing re-useable/global elements¹ you want to make sure that you can find them. There are multiple strategies for how to split everything into packages. Personally, I would be trying to classify by different business areas and then use the model views to provide virtual folders for each type. (eg. Partners, Resources, Messages)

¹ Pools, Lanes, Events etc are not re-useable. If in doubt, drop something onto a diagram inside a process. If EA doesn't move it out to the package level it probably isn't meant to be re-useable.