Mind mapping Your Way Through 'SAP Enterprise Architecture' - Part 2 : Preliminary Phase

Preliminary Phase is part of 'Architecture Context' in the Enterprise Architecture projects.

In this Phase we decide on the Context of Architecture Engagement Project. The Project Deliverables & Artifacts depend on the type of engagement. in SAP EA Framework we focus on IT Centric engagements & aligning Business-IT Objectives.

This Preliminary Phase is about defining "how we do architecture" in the enterprise concerned. There are two main aspects:

1. Defining the Framework to be used

2. Defining the Architecture principles that will?guide any architecture work.

Defining the Framework: The Preliminary Phase therefore involves doing any necessary work to adapt the ADM to define an organization-specific framework, using either the TOGAF deliverables or the deliverables of another framework. Since we are talking about SAP EA Framework, in the context of this article we finalize that we have chosen to use SAP EA Framework?for our project.?During the Preliminary Phase, artifacts of the SAP Enterprise Architecture Methodology will be tailored in context of a given enterprise architecture project engagement. The Architecture project could be IT Centric or Business Centric or both. Hence the artifact deliverables would be dependent on the type of project.

Defining the Architecture Principles:?Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission.?Architecture principles define the underlying general rules and guidelines for the use and deployment of all IT resources and assets across the enterprise.

They reflect a level of consensus among the various elements of the enterprise and form the basis for making future IT decisions. Each architecture principle should be clearly related back to the business objectives and key architecture drivers. The objective of this exercise is to create a set of principles that all attendees have consensus and can live with.? They are chosen so as to ensure alignment of IT strategies with business strategies and visions.

The output would?be captured in the following format in a Architecture Principles Template:

Principal Name: Should both be the essence of the rule as well as be easy to remember

Statement: Should succinctly and unambiguously communicate the fundamental rule.

Rationale: Should highlight the business benefits of adhering to the principle, using business terminology.

Implications: Should highlight the requirements, both for the business and IT, for carrying out the principle - in terms of resources, costs, and activities/tasks.

To Be Continued ... Mind mapping Your Way Through 'SAP Enterprise Architecture' - Part?3 :?Architecture Vision Phase