Enterprise Architecture Rapid Assessment

Colin Wheeler – Principal Consultant

2009

Introduction

Purpose This presentation focuses on delivering rapid assessments of

the enterprise architecture capability of an enterprise. It works from the following basis: The EA framework selected is TOGAFTM

The assessment gauges the following: The readiness of the enterprise to deliver EA The maturity of any existing EA artefacts and processes within the

enterprise The suitability and integration points with other crucial enterprise

functions such as the project office, operations management and risk management

The assessment is based on industry best practices as well as innovative and pragmatic new methods for delivering the best value to money EA effort.

What is Enterprise Architecture? What is an Enterprise?

TOGAF 8.1.1 says: “A collection of organizations that has a common set of goals such as a Government agency or entire corporation, division of a corporation or single department or geographically distributed organizations under common ownership”

What is Architecture? TOGAF 8.1.1 says: “A formal description of a system, or a detailed plan of the

system at component level to guide its implementation.” Officially

An enterprise paraphrased according to the Oxford English Dictionary is one or more individuals that strive for a common goal.

An architecture according to the Oxford English Dictionary is the art or practice of designing and constructing buildings or the conceptual structure and logical organisation of a computer system.

The common theme then comes to that enterprise architecture is the practice of designing and constructing enterprise systems. The changing industry point of view is that this is not restricted to enterprise computers systems.

What is TOGAFTM? TOGAFTM is a framework for the

design and implementation of an enterprise architecture

TOGAFTM helps an enterprise design, evaluate, and build the right architecture

Key to TOGAFTM is the Architecture Development Method (ADM) which is shown on the right.

TOGAFTM ensures effective design and procurement specifications that facilitate open systems implementation Enable benefits of open systems to

accrue with reduced risk A key to the TOGAFTM method are

building blocks, explained on the next slide.

A.Architecture

Vision

H.Architecture

Change Management

G.Implementation

Governance

C.Information

Systems Architectures

B.Business

Architecture

D. Technology Architectures

E.Opportunities and Solutions

F.Migration Planning

Requirements Management

Prelim:Framework and

Principles

A building block is defined by TOGAFTM as a package of functionality defined to meet business needs. Often the words “component”, “artefact” or “object” can be used to describe a building block.

Building blocks should be seen in the wider scope of a defined and bound object or component which must have the following: Defined contents and boundaries Interfaces Metrics

In architecture, building blocks represent systems and represent the components used to build systems.

In conducting architecture, the architecture itself and the framework that it is governed by are also represented as building blocks. For instance, a process, principle or policy would be seen as a building block.

Most building blocks interoperate with other building blocks Building blocks are a useful concept not only from an architectural point of

view but also from an implementation and governance point of view. Building block should have metrics associated with them in both the

Enterprise and the Solutions Continuums Building blocks are found in all four of the architecture domains that are

shown on the next slide

What are Building Blocks?

Business Architecture Defines business strategy, governance, organization, and key

business processes Data Architecture

Describes structure of logical and physical data assets and data management resources

Application Architecture Provides a blueprint for individual application systems to be

deployed, interactions with one another, and relationships to core business processes

Technology Architecture Describes physical software and hardware capabilities required

to support deployment of business, data, and application services

Security Architecture Defines security considerations throughout the entire enterprise

and across all domains. In most cases this domain is considered a cross domain function rather than a separate domain.

What are the Architecture Domains?

Enterprise Architecture Readiness Assessment

Method The method used to conduct the assessment has the following foundation:

A industry standard EA framework is utilised, in this case TOGAFTM is chosen

Sets of required deliverables are discovered and distilled into cohesive components (in the TOGAFTM case, building blocks)

Through integration with other frameworks and crucial enterprise functions such as programme and operations management these building blocks are rationalised into a single set Thus the architecture becomes part of important programme management

documents such as the PID (project initiation document) Chosen metrics are then applied to the building blocks to ensure their

suitability Thus each architecture building block can be tracked according to its maturity

or cost/benefit or key risk indicators Existing building blocks are identified and the capability to deliver the

required building blocks is examined A gap analysis is conducted A plan and report are generated, enabling the EA effort to move

forward

Deliverables The deliverables (building blocks) that are examined through this

assessment are based on the TOGAFTM framework They are then expanded, examined and then rationalised using

other industry frameworks depending on the specific enterprise. Examples of these frameworks could include PRINCE2, ITIL and COBIT.

Metrics are used to gauge the deliverables, enabling proper management of EA Architecture assets (building blocks) are expensive to develop and

maintain and through providing metrics we can assess on an ongoing basis both the value of having those building blocks as well as having an architecture for them.

Recommendations are made on repositories for deliverables and processes surrounding the lifecycle of those deliverables Repositories are logical, structured storage for architecture. They

enable us to trace and analyse the very complex structures that enterprise architecture creates as well as enabling efficient maintenance

Process This is not a linear process

but rather a set of steps with predecessors.

A number of these activities will take place in parallel

This process is designed to fit with the TOGAF ADM as well as industry standard architecture development processes

Other Functions and Frameworks Other frameworks and functions within the enterprise cannot be ignored

during the assessment The programme office form a vital component within the EA lifecycle and

must be fully integrated into the process and must buy-in to the requirements for the EA deliverables

Operations management deliver the real world benefits of EA through operating the assets and capabilities designed through architecture. Operations management are also responsible for delivering key information that feeds back into the EA lifecycle to sustain it.

Risk management must input into the types of deliverables that are required to enable pragmatic and successful risk management

Governance must be integrated into the EA effort from two points of view: Outward – architecture forms part of implementation and operations

governance Inward – architecture frameworks, processes and deliverables must be

governed externally to the architecture effort

Rationalise and Measure Deliver of a rationalised set of deliverables enable all functions to

understand the enterprise wide scope of EA, while creating a highly supportive environment for EA This focuses on the delivery of assets such as integrated project architecture and

project documents as well as living architecture building blocks being used in operational management

Important metrics are applied to the deliverables ensuring (examples are provided in brackets): The deliverable value is understood (cost/benefit) The current and future requirements (maturity, completeness) The current and future state (life-cycle and relevance) The current and future integration with other functions (compliance)

Business based metrics such as CSF, KPI and KRI are utilised to ensure that business understanding and appreciation of the architecture deliverables are achieved.

Mature and industry standard frameworks such as COBIT are utilised to ensure completeness of the exercise

Existing Assets Existing EA deliverables are examined for their applicability

and measured according to the previous steps. This ensures that any deliverables that are brought forward are done on a cost/benefit and risk mitigation basis

Existing repositories of assets that may exist such as programme office libraries, operations management CMDBs (Change Management Database) and KDBs (Knowledge Database) are examined for integration and existing asset values

Existing functions are examined for process and deliverables that will support the EA effort.

This step is important in facilitating the creation of the most efficient EA effort possible.

Analyse and Report A gap analysis will reveal the

required EA deliverables to drive the selected effort forwards as well as highlight any requirements for ongoing effort and capability creation

This effort focuses on the delivery of significant details with the TOGAF phases highlighted on the right

The reports are distilled into practical business focused presentations with clear and cohesive action plans

A.Architecture

Vision

H.Architecture

Change Management

G.Implementation

Governance

C.Information

Systems Architectures

B.Business

Architecture

D. Technology Architectures

E.Opportunities and Solutions

F.Migration Planning

Requirements Management

Prelim:Framework and

Principles

Offering Our lead consultant offers significant experience in the EA and

TOGAF fields having implemented, consulted on, trained and coached EA for more than 8 years and has around 20 years of industry experience, delivering consistently and pragmatically.

The offering also supports the long term development of the EA capability within the enterprise through: Ongoing consultancy Offering point contract resources that may be required Offering training and coaching to enterprise resources Offering best of breed, ongoing framework development and full EA

lifecycle support We would strongly suggested that you have a half day

introduction to TOGAF and that a half day workshop on the assessment are conducted as soon as possible.