Integrating TOGAF ADM, ArchiMate, BPMN & UML into your SDLC (Part 2)

Attached initial product requirement specification (PRS V0.1) attached indicating the key artefacts and notations

Getting down to being pragmatic - how do you represent current and target architectures in ARIS? For example, is it valid in your view to have the Master model/object as the current architecture, and hold a variant model/object as the target architecture?

We already use variant management for distinguishing between our standard designs and our permitted variant designs (examples: localised process deployed as variant process flow of the standard process flow; product/service specific process flows)

So we're already overladen with the mentally taxing variant management. Are there alternative ways of holding target architectures alongside current architectures in the same database?

Or should I hold current in one db, target in another, then use MashZone (or other?) to compare the two, report differences, show the progress from current to target?

Or do I lose the argument for ARIS and we move to something else?

Gartner has a good article on this "Develop the Enterprise Solution Architecture" and summarized below. In short you have to identify your core master building blocks across the business layer, application layer, data layer and technology layer and tag them as master objects i.e. BA master = business architecture master.  You then build master enterprise solution architecture views using the master building blocks and tag them as master solution architecture building blocks and version them i.e. ESA for processing claims v1.0. Any solution architecture that is then developed (also using master building blocks) per project can then be compared with the master ESA using the ARIS compare functionality.

I noticed you have excluded EPC's.  Is this intentional?  Is it assumed that this is part of the Business Process framework which leads to the FAD?