In recent months, at this very large organisations with a large repository using multiple notations and methodologies (current and legacy), a team of business analysts has produced several dozen BPMN models (process & collaboration; not conversation or choreography) primarily for communication with business stakeholders, i.e. the models are formally non-executable BPMN2.
Model validation, adherence to formalities and traceability/connectivity to other artefacts were not priorities.
We now have to formalise these models, maximise traceability and element reuse, and provide architecture teams with reports identifying data flows to/from specific systems, while respecting BPMN formalities because they need to be exported to XPDL (the diagrams should at least validate) for import into another system. (Policy is that EA must remain our primary architecture & model repository)
The question is, how best to do this efficiently and appropriately in EA (v12.1) and BPMN2.0 given the following:
• All messages, data objects, pools & lanes were created on an ad hoc basis (commonality may be inferred from similarity of names)
• BPMN <<BusinessProcess>>es were reused by dragging and dropping from the project explorer, creating Action instances (which do not validate and were linked "by hand"… because they're not valid BPMN as such)
• The system elements that are the resources of some activities, or that should be represented by pools, were modelled as Archimate
• BPMN requires that certain elements be correctly placed (owned) in the element hierarchy in the project browser - so reuse of any "library" of elements looks as though it has to be by copy/paste in the project (which is very slow here)
I think we're trying to do process and system modelling at the same time in BMPN...
What would you recommend?
Thanks, Julian