CMAD Group Workbook 3.2 Op Model Enable

11

Workbook 4 Workbook 1

Authored by: Alexander Doré August 14, 2010

Workbook 3.2

Architecture Services Mobilization Operational Model – Enablement - Definitions

Business Architecture Program Business Enterprise Architecture Governance (BEAG)

Confidential

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

22

2

Artifact Definitions

Project Charter Business Context Diagram Use Cases and High-level Requirements Conceptual Architecture Business and Technical Requirements Logical Application Architecture

Logical Integration Architecture Logical Information Architecture Logical Infrastructure Architecture Deployment Architecture - Integration Deployment Architecture - Integration Technical Design

33

Artifact Definitions Project Charter

Definition

Project Charter documents the business goals, scope and impact of the project. It identifies/articulates the capabilities that will be enabled by the project and conveys how the project aligns with the strategic and operational business architecture.

Creation Process

•  Identify business needs, issues and/or pain points

•  Identify the capabilities that will enable the development of the identified capabilities and address the issues/pain points

•  Develop a business case to support the capability build out

•  Create the charter document with the above information

Author Business Sponsor

EPMM Stage Planning

SDLC Phase Pre-SDLC

Project Architecture Delivery Context

Relevance for Architecture Delivery

KEY INPUT

The project charter acts as a primary input to two key deliverables – the business context diagram and the current state conceptual architecture.

Business Context Diagram B

us A

rch

Conceptual Current State Architecture L e

ad A

rch

ProjectCharter Sp

onso

r

44

Artifact Definitions Business Context Diagram

Definition

Business context diagram provides a view of value chain and the business functions impacted by the project scope. It servers as a context for all stakeholders on how their work fits in the overall operating context.

Creation Process

•  Review the project charter and identify the business areas that are impacted by the scope of the project

•  Conduct interviews/discussions with key business stakeholders and develop further understanding of the context

•  Create the business context diagram

•  Include relevant information context diagram

•  Socialize with business stakeholders and get buy-in

Author Business Architect

EPMM Stage Planning

SDLC Phase Requirements and Analysis



KEY Deliverable

Defines who, what, and where for a project to enable better understanding of business functions and activities.

Business Context Diagram Bu

s Ar c

h

Use Cases & High-level

Requirements

B A

Conceptual Current State Architecture Le

ad A

rch

ProjectCharter Sp

onso

r

55

Artifact Definitions Use Cases and High-level Requirements

Definition

A Use Case is a requirements gathering and documentation tool that describes how an actor uses a system to achieve a goal and what the system does for the actor to achieve that goal. It tells the story of how the system and its actors collaborate to deliver something of value for at least one of the actors.

Creation Process

•  Review the set of capabilities to developed as part of the project and identify a list of business scenarios

•  Use the scenarios to develop a list of use cases

•  Conduct workshops and define high-level narrative of system and user interactions. These narratives for the basis of detailed use cases

Author Business Analyst

EPMM Stage Planning




KEY INPUT

Use Cases articulate the user-system interactions and are a key input for developing the future sate conceptual architecture.

Conceptual Future State Architecture Le

a d A

r ch


u s A

r ch


Requirements

BA

Business and Technical

Requirements BA /

BSA


ad A

rch

ProjectCharter Sp

onso

r

66

Artifact Definitions Conceptual Architecture

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.

Creation Process

•  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

•  Define conceptual information models

•  Socialize with business stakeholders and get buy-in

Author Lead Architect / Info Architect

EPMM Stage Planning




ARCHITECTURE DELIVERABLE

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

Conceptual Future State Architecture Le

a d A

r ch


u s A

r ch


Requirements

BA


Requirements BA /

BSA


ad A

rch

ProjectCharter Sp

onso

r

77

Artifact Definitions Business and Technical Requirements

Definition

The Business and Technical Requirements Document (BTRD) is the primary requirements document. It contains the high-level as well as detailed requirements that enable the capabilities desired by project stakeholders.

Creation Process

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

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

•  Identify detailed business and technical requirements that will enable the project to deliver the desired capabilities

Author Business Analyst (BA) and Business System Analyst (BSA)

EPMM Stage Planning




KEY INPUT

Business and Technical requirements are a key input for developing the future state logical architecture models.

Conceptual Future State Architecture L

ead

Arc

h


Requirements

BA Business and

Technical Requirements B

A / B

SA

Conceptual Current State Architecture L

e ad

Arc

h Logical Application Architecture A

pp A

rch

Logical Information Architecture In

fo A

rch

Logical Infrastructure Architecture In

fra A

rch

Logical Integration Architecture A

pp A

rch

88

Artifact Definitions Logical Application Architecture

Definition

Logical Application Architecture model describes architecturally significant application components of the future state solution and the high-level interactions between them.

Creation Process

•  Review the future state conceptual architecture

•  Review the business and technical requirements

•  Identify application components that will enable the future state solution

•  Create a set of logical level models that clearly articulates the boundaries for application designers

Author Application Architect

EPMM Stage Execution

SDLC Phase Design




The logical application architecture is a primary architecture artifact and is used to communicate the future state with application designers and other technology stakeholders.


ead

Arc

h


Requirements BA

/ B

SA

Deployment Architecture-Infrastructure I n

fra A

rch

Deployment Architecture-Integration

Int A

rch

Logical Application Architecture A

pp A

rch


fo A

rch


fra A

r ch


pp A

rch

Technical Design A

pp

Dev

Services Design

I AS

99

Artifact Definitions Logical Integration Architecture

Definition

Logical Integration Architecture model identifies and documents integration standards, patterns and frameworks to be used in the project. These models, developed using Structural Design Pattern (SDP), facilitate consistent development and deployment of integration components and services.

Creation Process

•  Review the future state conceptual architecture and business and technical requirements

•  Indentify the integration patterns, standards and services to be used in the solution

•  Develop logical model and the component context diagrams (CCD) to capture components, component placement and interconnections

Author Application Architect


SDLC Phase Design




The logical integration architecture is a primary architecture artifact and is used to communicate the future state with IAS.


ead

Arc

h


Requirements BA

/ B

SA


fra A

rch


Int A

rch


pp A

rch


fo A

rch


fra A

r ch


pp A

rch

Technical Design A

pp

Dev

Services Design

I AS

1010

Artifact Definitions Logical Information Architecture

Definition

Logical Information Architecture model articulates the concepts outlined in the conceptual architecture in the form of information objects/entities. It enables standard definitions of the information objects to support business vocabulary and semantics.

Creation Process



•  Identify the information objects that are relevant for the scope of the project

•  Develop detailed information specifications and flows that will act as primary input for the physical data models

Author Information Architect


SDLC Phase Design




The logical information architecture is a primary architecture artifact and is used to communicate the future state with Data Modelers and Database Administrators.


ead

Arc

h


Requirements BA

/ B

SA


fra A

rch


Int A

rch


pp A

rch


fo A

rch


fra A

r ch


pp A

rch

Technical Design A

pp

Dev

Services Design

I AS

1111

Artifact Definitions Logical Infrastructure Architecture

Definition

Logical Infrastructure Architecture models depict the architecture domains/zones and, among them, the infrastructure components and their connectivity.

Creation Process



•  Identify infrastructure components that will enable the future state solution

•  Create a logical infrastructure level models

Author Infrastructure Architect


SDLC Phase Design




The logical infrastructure architecture is a primary architecture artifact and is used to communicate the future state with Infrastructure Management and other technology stakeholders.


ead

Arc

h


Requirements BA

/ B

SA


fra A

rch


Int A

rch


pp A

rch


fo A

rch


fra A

r ch


pp A

rch

Technical Design A

pp

Dev

Services Design

I AS

1212

Artifact Definitions Deployment Architecture - Integration

Definition

Deployment Integration Architecture models depict the underlying integration technologies that support the target integration architecture for the project.

Creation Process

•  Review the logical integration and infrastructure architecture models

•  Identify integration deployment patterns and research the exceptions by working the enterprise architecture governance process

•  Identify technology components that will enable the logical integration model

•  Create a deployment integration level models

Author IAS (Integration Architecture)


SDLC Phase Design




The integration deployment architecture is a primary architecture artifact and is used to communicate the physical integration elements in the future state.

Deployment Architecture-Infrastructure In

fra

Arc

h

Platform Implementati

on Plan Infra

Eng

Physical Data Model D

ev D

BA


Int A

rch


pp A

rch


fo A

rch


fra

Arc

h


pp A

rch

Technical Design A

p p D

ev

Application Code A

pp D

ev

ServicesCode

IASServices

Design

I AS

1313

Artifact Definitions Deployment Architecture - Infrastructure

Definition

Deployment Infrastructure Architecture models depict the underlying technologies that support the target solution environment including networks, storage, platforms, middleware, information, access management, security, etc.

Creation Process

•  Review the logical infrastructure architecture

•  Identify suitable standard deployment patterns and research the exceptions (by working with TSB and the CTO governance process)

•  Identify technology components that will enable the logical infrastructure model

•  Create a deployment infrastructure level models

Author Infrastructure Architect


SDLC Phase Design




The infrastructure deployment architecture is a primary architecture artifact and is used to communicate the technology details involved in the target implementation.


fra

Arc

h


on Plan Infra

Eng


ev D

BA


Int A

rch


pp A

rch


fo A

rch


fra

Arc

h


pp A

rch

Technical Design A

p p D

ev

Application Code A

pp D

ev

ServicesCode

IASServices

Design

I AS

1414

Artifact Definitions Technical Design

Definition

Technical Design uses the Logical Architecture models and the detailed requirements to describe the detailed specifications for system components. These specifications comprise of object design, sequence diagrams, interaction diagrams, etc.

Creation Process

•  Review the future state conceptual and logical architecture models


•  Identify the system components that would enable project to meet the requirements

•  Develop detailed specifications/design

•  Review with Lead Architect to ensure alignment

Author Application Development Team


SDLC Phase Design



CONSUMER OF ARCHITECURE

Logical Architecture models are the primary input for developing detailed design. Technical design team should use these models to ensure that design is aligned from an architecture standpoint.


fra

Arc

h


on Plan Infra

Eng


ev D

BA


Int A

rch


pp A

rch


fo A

rch


fra

Arc

h


pp A

rch

Technical Design A

p p D

ev

Application Code A

pp D

ev

ServicesCode

IASServices

Design

I AS

CMAD Group Workbook 3.2 Op Model Enable

Documents

Transcript of CMAD Group Workbook 3.2 Op Model Enable