◄◄◄ Previous Page         

 

          Next Page ►►►

In order for people to understand POETs fundamental structural and transformational ontology, here we map the names of common documents/models/artefacts etc, that many people are familiar with (although perhaps, not everyone defines them in the same way!)

Business Model

Corresponds to the Enterprise Context level. Since this information is part of the Direction domain, the specific ontologies used are defined in POED. Any metamodels actually used are very business dependant (and dependent upon the C-Suite’s experience) but typically utilise things like the Business Model Canvas (BMC) as illustrated here.

Business Motivation Model

Corresponds to the Contextual level of MAGMA. It defines (at a high level) what the enterprise wishes to achieve (Ends), and how it proposes to achieve them (Means).

Operating Model

Corresponds to the Contextual level of MACE. It defines the highest level view of the structure of the Enterprise required to enable the Business Model and the objectives defined in the Business Motivation Model.

Roadmap Model

Corresponds to the Conceptual level of MAGMA. It defines the actions that must be taken to structurally change the Enterprise from the current Structural state, through Intermediate Structural states, towards the Target Structural state.

Capability Model

Corresponds to the Conceptual level of MACE. It defines the fundamental capabilities required to support and enable/operationalise the Operating Model.

 

The remaining levels of Transformational information (as defined by MAGMA) tend to be considered more in terms of the type of information existing rather than centred around the levels themselves. People generally talk of Requirements, Plans, Principles etc, Metrics and (hopefully but not generally) the rationale for decisions, which map directly to the Motivation, Actions, Guidance, Metrics and Assessment domains of MAGMA.

Solution Architecture

Corresponds to the Logical level of MACE. It defines (for each solution/project) the logical designs.

Detailed Design

Corresponds to the Physical level of MACE. It defines (for each solution/project) the physical designs.

Enterprise Strategy, Transformation Strategy.

From these basic models, it can be clearly seen how the Enterprise Strategy and Transformation Strategy are composed.

¨      The Enterprise Strategy consists of the Business Motivation Model and Operating Model set in the context of the Business Model.

¨      The Transformation Strategy consists of the Roadmap Model and Capability Model, set in the context of the Business Motivation Model  and the Operating Model.

 

Where does your Enterprise’s Business Model, Business Motivation Model, Operating Model, Roadmap and Capability Model fit into your Enterprises Transformation domain?

Do you have the required basic information, in a usable format, to allow your Enterprise to produce the Business Motivation Model and Operating Model?

Do you have the required basic information, in a usable format, to allow your Enterprise to produce the Roadmap and Capability models?

 

 

◄◄◄ Previous Page          

          Next Page ►►►





 

© 2008-2018 Pragmatic EA Ltd