CMAD Group Workbook 3.1 Op Model Enable

11

Workbook 4 Workbook 1

Authored by: Alexander Doré August 14, 2010

Workbook 3.1

Architecture Services Mobilization Operational Model – Enablement - Delivery Process

Business Architecture Program Business Enterprise Architecture Governance (BEAG)

Confidential

C-MAD Group Inc Computer Science & Engineering Architecture Consulting Services

22

1 Introduction Enterprise Architecture Delivery Process: Architecture Delivery Process (ADP) Architecture Design Document (ADD)

33

Architecture Deliverables

Architecture Design Document (ADD): Increases effectiveness as the primary artifact

Requirements & Analysis Design Construct Test Deploy

SDLC Non-SDLC

Sample Architecture Deliverables

Architecture Design Document (ADD)

Architecture Governance and Review Documents

1

Business Context Diagram*

Conceptual Architecture

Logical Architecture

Application Architecture

Information Architecture

Integration Architecture

Infrastructure Architecture

Architecture Blueprints

Architecture Options Analysis

Application Rationalization

Analysis

Vendor Product Analysis

Structural Design Pattern (SDP) Virtual Management Layer

1 2

* Will be created by Architecture team until business teams are able to provide this

Physical Architecture

System Architecture

Security Architecture

Zachman/RUP Hybrid Architecture

Framework

3

2

3

TOGAF Components

As-Needed Applicability

44

Architecture Delivery Process (ADP): Guides ADD creation part of improvement process

Construct , Test , Deploy

Enterprise and Domain Architecture Models and Standard

Requirements & Analysis Design

ProjectCharter B

iz S

ME

Conceptual Future State Architecture

Lead

Arc

h

Business Context Diagram

BA High Level

Use Cases

BA Business and

Technical Requirements

BA

Deployment Architecture -Infrastructure I n

fra

Arc

h

Platform Implementati

on Plan I nfr

a E

ng

Physical Data Model D

ev

DB

A

Deployment Architecture -Integration

Int

Ar c

h

Conceptual Current State Architecture

Lead

Arc

h Logical Application Architecture A

pp

Ar c

h

Logical Information Architecture I n

fo A

rch

Logical Infrastructure Architecture In

f ra

Ar c

h

Logical Integration Architecture A

pp

Arc

h

Architecture Governance

Review

EA

Technical Design A

pp

De

v

Application Code A

pp

De

v

ServicesCode

I AS


Review

EA Architecture Governance

Review

EA

Services Design

IAS

Definition

Conceptual architecture model provides an understandable picture of the overall purpose of the proposed solution to business stakeholders. The solution components can be “layered” on top of a process, functional or “tiered” (presentation, business, data) view.

CreationProcess

• Review the charter and business context diagram(s) and develop a detailed understanding of situation

• Review the high use cases and requirements to understand the direction of the future state

• Identify the solution components that would enable the future state solution

• Socialize with business stakeholders and get buy-in

Author Lead Architect

EPMM Stage Planning

SDLC Phase Requirements and Analysis

Project Architecture Delivery Context

Relevance for Architecture Delivery

ARCHITECTURE DELIVERABLE

The conceptual architecture is a primaryarchitecture artifact and is used as a model to communicate the future state solution with business stakeholders .

ProjectCharter B

iz S

ME

Conceptual Future State Architecture L

ea

d A

r ch

Business Context Diagram

BA High Level

Use Cases

BA

Conceptual Current State Architecture L

ea

d A

r ch

��

��

��

��

��

��

��

��

��

��

��

��

��

��

�� –��

��

�� –��

��

��

��

��

��

Project Architecture Delivery Process (ADP) – • Outlines the architecture deliverables created during different phases of the SDLC • Assigns responsibilities for each architecture deliverable • Defines inputs required for key deliverable s and clarifies the role in the architecture delivery process • Facilitates optimal use of architecture resources during the SDLC

Architecture Delivery Process

Artifact Definitions

Roles and Responsibilities

ADP takes an architecture view of deliverables, and defines roles and responsibilities in the context of delivering the solution architecture for a project.

55

Project Architecture Delivery Process – Proposed Future State

CTO - Architecture CTO - IAS Non CTO



Design


Lead

Arc

hBusiness Context Diagram B

us

Arc

h

Use Cases & High -level

Requirements

BA Business and

Technical Requirements B

A /

BS

A

Deployment Architecture -Infrastructure In

fra

Arc

h


on Plan Inf r

a E

ng


ev

DB

A


Int

Arc

h


L ea d

Arc


pp

Arc

h

Logical Information Architecture In

fo A

r ch


fra

Arc

h


pp

Arc

h


Review Lea

d A

r ch

Technical Design A

pp

De

v

Application Code A

pp

De

v

ServicesCode

IAS


Review Lea

d A

rch

Services Design

I AS

Requirements and Analysis

ProjectCharter S

ponsor

66

ADP Delivers Solution Architecture for Architecturally Significant Projects

Initiate Project

CTO Activity

Project Manager Activity

Involve Architect?

Request for Architect

Involvement

Calculate Architecture Significance

Determine Project Type

Assign Architect

Architecture Significance Model

Calculate Significance by evaluating multiple factors including business impact, technology impact, process changes, portfolio impact, etc. Architecture Significance Score should be used to determine if architects should play a role in a project. A higher assessment means that the architecture needs to be engaged at a greater level.

Project Typing Framework

Uses Architecture Significance and project costs to determine “Type”. Project Type determines the level of architect assigned on a project. Type 4 and Type 3: Projects that enable strategic capabilities Type 2: Projects that enable key capabilities, but are not as strategic as Type 4 & Type 3 projects Type 1: Projects that have fairly low architecture significance

Receive Architecture

Estimates

Proc

ess

Fram

ewor

ks

Yes

A B

A B

Receive Response from

Architecture

No

Create solution architecture using the Architecture Delivery Process

Decision made by Architecture Leadership (all disciplines)

77

Key Benefits of the ADP

•  Enables CTO to develop a more effective partnership with the business, clearly linking desired business capabilities to technical implications

•  Dispels the “ivory tower” view of enterprise architecture by ensuring accountability of architects to project delivery

•  Supports enterprise efforts (e.g. governance) as well as agendas of the individual lines of business

•  Provide clear roles and responsibilities

•  Maximizes value from architects through effective use and communication of standards and governance

The goal of the ADP is to maximize value of architecture throughout the project delivery lifecycle.



Design


Lead

Ar c

h

Business Context Diagram B

us

Arc

h

Use Cases & High -level

Requirements

BA Business and

Technical Requirements B

A /

BS

A

Deployment Architecture -Infrastructure In

f ra

Arc

h


on Plan Inf r

a E

ng


ev

DB

A


I nt

Arc

h


Lead

Ar c


pp

Arc

h

Logical Information Architecture In

fo A

r ch


f ra

Arc

h


pp

Arc

h


Review Le a

d A

r ch

Technical Design A

pp

De

v

Application Code A

pp

De

v

ServicesCode

IAS


Review Lea

d A

r ch

Services Design

I AS

Requirements and Analysis

ProjectCharter S

ponsor

CMAD Group Workbook 3.1 Op Model Enable

Documents

Transcript of CMAD Group Workbook 3.1 Op Model Enable