IBM Software Group - The Open...

®

IBM Software Group

© 2009 IBM Corporation

Using TOGAF™ 9 as a Tool’s Common Metamodel

Scott DarlingtonSenior Product Manager, Enterprise [email protected]

IBM Software Group | Rational software

2© 2009 IBM Corporation

AgendaHistory of System Architect

New Requirements

TOGAF 9 Metamodel & Extensions

Summary



History of System Architect

Popkin Software – System ArchitectFounded in 1986Acquired by Telelogic in 2006Telelogic acquired by IBM in 2008

Steady addition of new features and frameworks over many years



Founded: 1986



DoDAF 2.0

June 2009

2002C4ISR Framework

1999

DoDAF 1.0

2007

DoDAF 1.5 2008

MODAF 1.2 / NAF 3

UPDM

2009

2005

MODAF 1.0

EA FrameworksDoDAFFEAFIAFMODAFNAFTOGAFZachmanetc.

EA FrameworksDoDAFFEAFIAFMODAFNAFTOGAFZachmanetc.

Support for many frameworks & versions added to System Architect over the years

Many implemented independently, following the fragmentary nature of framework evolution itself

Finally time to renovate?

Support for many frameworks & versions added to System Architect over the years

Many implemented independently, following the fragmentary nature of framework evolution itself

Finally time to renovate?

Framework Evolution




New Requirements


Summary



New Requirements: The Usual Suspects

Feature requests from customers

New techniques / diagrams to support

New releases of EA frameworksDoDAF 2, TOGAF 9, etc.

New frameworks to support such as UPDM and the IBM EA Method’s framework



New Requirements: A Common Metamodel

To make framework support more efficient, we’d like to map our supported frameworks to a common metamodel

The TOGAF 9 Metamodel is broad in scope, open, extensible

We expect other frameworks to broaden

Base Metamodel

Metamodel Extensions

Individual Frameworks



New Requirements: Fitting into Big Blue

Software Group: A broad portfolio of tools & runtimes related toEA

DB2, Data Architect, Cognos Business Intelligence & ReportingCollaboration such as Instant Messaging, Notes, Web ConferencesTools for application development, change & configuration management, requirements management, portfolio managementOperations tools such as managed deployment, discovery, CMDBApplication servers, BPM tools & runtimes

Servers & Systems

IBM Corporate IT, Business Transformation / CIO

Global Services organization Includes a strong EA practice in Strategy & Change organization



Enterprise Strategy

Fire and hope!

Enterprise Architecture

Business Operating Environmentand IT Infrastructure

TransitionPlanning

G ro u p IT A r c h i t e c t u r e D e f in i t io n

I n f r a s t r u c t u re D e s ig n & P la n n i n g

E s t a b lis h IT C o m p e t e n c y C e n t re

E n d U s e r I n f r a s t r u c t u r e U p g r a d e

In t e r - c o m p a n y W A N ( i m p le .)

O u t s o u r c e N e w C o re s y s t e m s

O u t s o u r c e H e lp d e s k a n d D e s k t o p

O u t s o u rc e n e t w o rk

O u t s o u r c in g I n i t i a t iv e s

C o m p e t e n c y C e n t re In i ti a t iv e s

E l e c t r o n ic S e r v i c e D e li v e r y

D a t a W a r e h o u s e

C u s t o m e r S e r v i c e C e n t r e

WA N in fr a s tru c tu r e

In tr a n et /M a il in f ra s tr u ct u re

C u s to m e r S e rv ic e

D a ta

Wa re h o u s e

G ra p h ic a l I S

B . U .

B . U .

D o cu m en t M an a g e me n t

S y s te m s Ma n a g e me n t

Mid d le w a r e

N E T W O R K

P la n n in g /D e s ig n In i t i a t iv e s

In f r a s t ru c t u r e In i ti a tiv e s

O t h e rB u s i n e s s U n it S y s te m sK i o s k sT e l e m e t r y s y s t e m se tc

In i t ia t iv e s f o c u s e d o n m i g r a t i n g t o t h e n e w d e liv e ry e n v ir o n m e n t

P la n n in g /D e s ig nI n f ra s t ru c t u reO u t s o u rc in g

In i t ia t iv e s f o c u s e d o n im p le m e n t in g t h e v i s i o n

P la n n in g /d e s ig nI T C o m p e t e n c y c e n tre

K e y G r o u p D e c is i o n P o in t s

ArchitectureGovernance

Bus Arch’ture IT Architecture

AEICorporate

YankeeGroup

SaturnGroup

YarnDivision

KnitsDivision

SenecaPlant

RaleighPlant

CashManagement

Shipping

Accounting

ComponentDesign

Yarn Buying

Order Entry

ComponentScheduling

YarnDyeing

Inventory

AssortmentPlanning

ComponentKnitting

Tagging & Packing

Business Structure

Business Locations

IBM EA Method: ContextPr

ogra

m f

ocus

Ente

rpris

e w

ide

focu

s

Strategy

Planning

Designand

Delivery

Change Programs

Soln Outline Macro Design Micro Design Devt, etc.

Program ArchitectureG r o u p I T A r c h i te c tu r e D e fi n it io n

I n fr a s t r u c tu r e D e s i g n & P l a n n i n g

E s ta b li s h IT C o m p e t e n c y C e n t re

E n d U s e r In f ra s t ru c t u r e U p g r a d e

In t e r - c o m p a n y W A N (i m p le .)

O u ts o u r c e N e w C o r e s y s t e m s

O u ts o u r c e H e lp d e s k a n d D e s k t o p

O u ts o u r c e n e tw o r k

O u t s o u r c i n g I n i t ia t iv e s

C o m p e t e n c y C e n t r e In i t ia t i v e s

E l e c t r o n ic S e r v ic e D e li v e r y


C u s to m e r S e r v ic e C e n t r e

W AN infr astr uctu reI ntra net/ Mai l inf rast ruct ure

C ust om er S ervic eDat a Wa reho use

Gra phic al I S

B. U. B.U .

Do cu men t M ana gem en t

Sys tem s M an age me nt

Mid dle war e

N E T W O R K

P l a n n i n g / D e s i g n In i t ia t i v e s

I n f r a s t r u c t u r e I n i t ia t iv e s

O t h e rB u s i n e s s U n i t S y s t e m sK i o s k sT e l e m e t r y s y s t e m se t c

I n i t i a t i v e s f o c u s e d o n m i g r a t i n g t o t h e n e w d e l i v e r y e n v i ro n m e n t

P l a n n i n g / D e s i g nI n f r a s t r u c t u r eO u t s o u r c in g

I n i t i a t i v e s f o c u s e d o n i m p l e m e n t i n g t h e v i s i o n

P l a n n i n g / d e s i g nI T C o m p e t e n c y c e n t r e

K e y G r o u p D e c is io n P o in t s


Program ArchitectureG r o u p I T A r c h i t e c t u r e D e f i n i t i o n

I n f r a s t r u c t u r e D e s i g n & P l a n n i n g

E s t a b l i s h I T C o m p e t e n c y C e n t re

E n d U s e r I n f ra s t ru c t u r e U p g r a d e

I n t e r - c o m p a n y W A N ( i m p l e . )

O u t s o u r c e N e w C o r e s y s t e m s

O u t s o u r c e H e l p d e s k a n d D e s k t o p

O u t s o u r c e n e t w o r k



E l e c t r o n i c S e r v i c e D e l i v e r y





Gra phic al I S

B. U. B.U .



Mid dle war e

N E T W O R K









Enterprise Architecture= “the city plan”

System Design= “the buildings”

Strategy= “the city’s purpose & goals”Technology

AvailabilityBusiness

OpportunityBus Strategy IT Strategy

10



The IBM EA Method

Centered on a client engagement model

Contributed to early TOGAF versions

Business Architecture

Technology Architecture

Governance

Strategic Gap Analysis

Transition

Enterprise Capabilities

IS Architecture

Current Environment

Proposal and Engagement PlanningClientObjectives

EmergingOpportunities

Business Event List

Locations

IT NodesIT Components

EA Neighborhoo

d Gaps Ident’n

EA Capability Assessment

EA Neighborhoo

d Assessments

Transition Initiatives

Transition Management

Strategy Integrated Transition

Plan

Management Action Plan

Decision Model

Principles, Policies & Guidelines

Architecture Management

Processes

Business Activity Mdl

Business Structure

Architecture ManagementRoles / Resp

Architecture Management

Metrics

Critical issues,

opportunities & rec’ns

Technology Reference Architectures

Application Groups

User GroupsIS Reference Architectures

Capability Model

ResourcesEA

Overview Diagram

Strategic CBM

Business Directions

EA Guiding Principles

Business Scenarios

Deployment Unit Matrices

DataStores Deployment

Units (IS)

Placement Guidelines

Standard Use Cases

Enterprise KPIs

Standard NFRs

Roles

Usage Matrice

s

Business Reference Architectures

Enterprise Information

Model



Mapping IBM’s EA Framework onto TOGAFIBM EA MethodTOGAF

Architecture Vision

BusinessArchitecture

InformationSystems

Architecture

TechnologyArchitecture

Migration Planning

ImplementationGovernance

EADevelopment

& Maintenance

RequirementsManagement

Opportunities & Solutions



The IBM EA Framework

EnterpriseCapabilities


InformationSystemsArchitecture


Functional Aspect of Architecture

People Activities Data

External to architecture

IT Components (s/w & h/w)

Business Structure

Business Activity Mdl

Component Business ModelSkills

Business Services Model

Standard Use Cases

Standard IS NFRS

IT Nodes

Technology Functional Reference Architectures

RolesEnterprise Info Model

Usage matrices

Usage matrices

Usage matrices

ApplicationGroups

DataStores

AC MapFunction Data

Application Services ModelUser Groups

Deployment Units IS)

Placement Guidelines

Deployment Unit Matrices

Information Activities

Presentation Services

ApplicationServices

DataServicesIT Systems

Management WPs

IT Systems Operational

WPs

Locations Model

Business Event List

Locations List

Enterprise KPIs

Business Scenarios

Activity Resources

Skills Resources

Information Resources

EventsStrategy

Strategic CBM

EA Guiding Principles

IS Strategy WPsIS Strategy

WPsIS Strategy WPsIS Strategy

WPs

IT Strategy WPsIT Strategy

WPsIT Strategy WPsIT Strategy

WPs

Business Operational RAsBusiness Functional Reference Architectures

Technology Operational RAs

Bus Strategy WPsBus Strategy

WPsBus Strategy WPsBus Strategy

WPs

IS Functional Reference Architectures IS Operational RAs

OperationalAspect of

Architecture

Location

And/or

And/or



Mapping IBM’s EA Framework onto TOGAF





Functional Aspect of ArchitectureExternal to architecture

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product


ArchitecturePeople Activities DataEventsStrategy Location

IBM EA Framework

Architecture Vision


InformationSystems

Architecture


Migration Planning


EADevelopment

& Maintenance



TOGAF



Mapping IBM’s EA Framework onto TOGAF





Functional Aspect of ArchitectureExternal to architecture

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product

Work Product


ArchitecturePeople Activities DataEventsStrategy Location

IBM EA Framework

Architecture Vision


InformationSystems

Architecture


Migration Planning


EADevelopment

& Maintenance



TOGAF

Can we use a common base to support both?

Can we use a common base to support both?



Connection of EA to Change Programs and OperationsEnterprise Strategy

Fire and hope!

Enterprise Architecture

Business Operating Environmentand IT Infrastructure

TransitionPlanning

G ro u p IT A r c h i t e c t u r e D e f in i t io n

I n f r a s t r u c t u re D e s ig n & P la n n i n g

E s t a b lis h IT C o m p e t e n c y C e n t re

E n d U s e r I n f r a s t r u c t u r e U p g r a d e

In t e r - c o m p a n y W A N ( i m p le .)

O u t s o u r c e N e w C o re s y s t e m s

O u t s o u r c e H e lp d e s k a n d D e s k t o p

O u t s o u rc e n e t w o rk

O u t s o u r c in g I n i t i a t iv e s

C o m p e t e n c y C e n t re In i ti a t iv e s

E l e c t r o n ic S e r v i c e D e li v e r y



WA N in fr a s tru c tu r e

In tr a n et /Ma il in f ra s tr u ct u re

C u s to me r S e rv ic e

D a ta

Wa re h o u s e

G ra p h ic a l I S

B . U .

B . U .

D o cu m en t M an a g e me n t

S y s te m s Ma n a g e me n t

Mid d le w a r e

N E T W O R K

P la n n in g /D e s ig n In i t i a t iv e s

In f r a s t ru c t u r e In i ti a tiv e s

O t h e rB u s i n e s s U n it S y s te m sK i o s k sT e l e m e t r y s y s t e m se tc

In i t ia t iv e s f o c u s e d o n m i g r a t i n g t o t h e n e w d e liv e ry e n v ir o n m e n t

P la n n in g /D e s ig nI n f ra s t ru c t u reO u t s o u rc in g

In i t ia t iv e s f o c u s e d o n im p le m e n t in g t h e v i s i o n

P la n n in g /d e s ig nI T C o m p e t e n c y c e n tre

K e y G r o u p D e c is i o n P o in t s

ArchitectureGovernance

Bus Arch’ture IT Architecture

AEICorporate

YankeeGroup

SaturnGroup

YarnDivision

KnitsDivision

SenecaPlant

RaleighPlant

CashManagement

Shipping

Accounting

ComponentDesign

Yarn Buying

Order Entry

ComponentScheduling

YarnDyeing

Inventory

AssortmentPlanning

ComponentKnitting

Tagging & Packing

Business Structure

Business Locations

Prog

ram

foc

usEn

terp

rise

wid

e fo

cus

Strategy

Planning

Designand

Delivery

Change Programs

















Gra phic al I S

B. U. B.U .



Mid dle war e

N E T W O R K

























Gra phic al I S

B. U. B.U .



Mid dle war e

N E T W O R K









TechnologyAvailability

BusinessOpportunity

Bus Strategy IT Strategy



Building blocks, rules, patterns,

constraints


constraints

Enterprise ArchitectureEnterprise

Architecture

Strategy, purpose, objective, vision, etc.Strategy, purpose,

objective, vision, etc.

Are we still moving in the

right direction?

Are our target architectures

still right?

This is the way things should be architected

& designed

EA Governance

EA Governance

Are we doing these things the way we said we want

them done?

The EA Lifecycle

Solution Development & DeliverySolution Development & Delivery

Programs & ProjectsStrategic Delivery

Strategic Delivery

EA Transition Planning


Project Prioritization & Planning


These are the things we should do

These are our roadmaps

UPSTREAM EAIdentifying viable projects

that help realise the enterprise architecture

DOWNSTREAM EAEnsuring projects can exploit the enterprise

architecture




constraints


constraints

Enterprise ArchitectureEnterprise

Architecture

Strategy, purpose, objective, vision, etc.Strategy, purpose,

objective, vision, etc.

Are we still moving in the

right direction?

Are our target architectures

still right?

This is the way things should be architected

& designed

EA Governance

EA Governance

Are we doing these things the way we said we want

them done?

The EA must be a partnership with the Solution teams

Solution Development & DeliverySolution Development & Delivery

Programs & ProjectsStrategic Delivery

Strategic Delivery





These are the things we should do

These are our roadmaps



EA: Making the Developers’ Lives Easier

Views of hardened solution asset published to catalog

View of hardened solution asset is harvested into SA

Solution asset published to RAM

SASystem

Architect

Rational Asset Manager

EA Repository

EA Artifacts

SCM Repository

Sol’n Artifacts

RSA

RSA Product Family

RAM UI

RAM User Interface

EA Site

1

2

EA Browser

Vision: Developer finds desired solution asset in EA browser and drags it into her project. Behind the scenes, full asset is extracted from RAM and placed in selected project



EA: Making the Developers’ Lives Easier

Views of hardened solution asset published to catalog

View of hardened solution asset is harvested into SA

Solution asset published to RAM

SASystem

Architect

Rational Asset Manager

EA Repository

EA Artifacts

SCM Repository

Sol’n Artifacts

RSA

RSA Product Family

RAM UI

RAM User Interface

EA Site

1

2

EA Browser

Vision: Developer finds desired solution asset in EA browser and drags it into her project. Behind the scenes, full asset is extracted from RAM and placed in selected project

The metamodel must support harvesting more information from the solution tools and

providing architecture building blocks and guidance integrated with the tools

The metamodel must support harvesting more information from the solution tools and

providing architecture building blocks and guidance integrated with the tools




New Requirements


Summary



Core TOGAF 9 Metamodel in System Architect

ControlNew SA Name

"Is Control?" Property onBPMN Process andGateway Definition inBPMN

Business ServiceLegacy SA Name

Business Service

Stakeholder PositionNew SA Name

Stakeholder Position

Stakeholder GroupLegacy SA Name

Stakeholder Group

CapabilityLegacy SA Name

Capability

Platform ServiceNew SA Name

Platform Service

Physical TechnologyComponent

Legacy SA NameTechnology

Logical TechnologyComponent

New SA NameLogical Technology

Physical ApplicationComponent

New SA NamePhysical Application

Physical Data ComponentNew SA Name

Physical Data Component

Logical Data ComponentNew SA Name

Logical Data Component

EntityLegacy SA Name

Entity

Application ComponentLegacy SA Name

ApplicationNew SA Name

IS ServiceNew SA Name

IS Service

ContractNew SA Name

Contract

MeasureLegacy SA Name

Performance Measure

ObjectiveLegacy SA Name

Business Objective

Stakeholder/ViewpointNon-Key Attributes

InvolvementClass

EventLegacy SA Name

BPMN EventNew SA Name

Competency

TOGAF 9 ViewpointLegacy SA Name

This is the set of metamodel

StakeholderLegacy SA Name

Stakeholder

Work PackageNew SA Name

Work Package

GapNew SA Name

Gap

RequirementLegacy SA Name

Requirement

AssumptionLegacy SA Name

Assumption

ConstraintLegacy SA Name

Business Constraint

PrincipleLegacy SA Name

Principle

TacticLegacy SA Name

Tactic

Business RuleLegacy SA Name

Business Rule

VisionLegacy SA Name

Vision

DriverLegacy SA Name

Strategy

Business PolicyLegacy SA Name

Business Policy

MissionLegacy SA Name

MissionOrganization UnitLegacy SA Name

Organizational Unit

Service QualityNew SA Name

Service Quality

LocationLegacy SA Name

Location

GoalLegacy SA Name

Business Goal

ProductLegacy SA Name

Product

ProcessLegacy SA Name

BPMN Process

FunctionLegacy SA Name

Function

RoleLegacy SA Name

Role

ActorLegacy SA Name

Participant is removed

Legends

Existing SA Metamodel Objects available toTOGAF

TOGAF Services Extensions

TOGAF Process ModelingExtensions

TOGAF Motivation Extensions

TOGAF Infrastructure ConsolidationExtensions

TOGAF Governance Extensions

TOGAF Data Extensions

TOGAF Core

may have

needs

is dependent on

belongs to

holds

may have

is represented in

delivers

performs task in

orchestrates

participates in

is required by a

is resolved bygenerated by

generates

is produced by

operates in

is realized by

is tracked against

aconsumes

communicates with

orchestrates

is resolved by

applies to

governs

applies to

operates in

participates in

is produced by

owns

has

may have

a

belongs to

orchestrates

is owned and governed by

is realized through

is realized through

is realized through

is a property on

is processed by

provides/consumessupplies/consumes

resides within

is mapped from

hostsresides within

is realized by

hosts

is implemented on

is realized by

hosts

is supported by

supplies

exists for

creates

driven by

creates

is set for

satisfies

supports

executes



TOGAF 9 Metamodel – Motivation Extension

GoalLegacy SA Name

Business GoalNew SA Name

GoalOrganization UnitLegacy SA Name

Organizational UnitNew SA Name

Organization Unit

ObjectiveLegacy SA Name

Business Objective

DriverLegacy SA Name

StrategyNew SA Name

Strategy

Business ServiceLegacy SA Name

Business Service

ContractNew SA Name

Contract

Service QualityNew SA Name

Service Quality

TacticLegacy SA Name

Tactic

Business RuleLegacy SA Name

Business Rule

VisionLegacy SA Name

Vision

Business PolicyLegacy SA Name

Business Policy

MissionLegacy SA Name

Mission

Legends

Existing SA Metamodel Objects available to TOGAF

TOGAF Motivation Extensions

TOGAF Governance Extensions

TOGAF Core

is dependent on

is owned and governed by

communicates with

applies to

governs

executes

supports

satisfies

may have

is set for

creates

creates

driven by

applies to

has

exists for



Actors, Roles, and Competencies

Additional content from System Architect

In this case, we have an existing metamodel element in System Architect, Competency, that is blended into the

TOGAF Core metamodel

In this case, we have an existing metamodel element in System Architect, Competency, that is blended into the

TOGAF Core metamodel



Actor / Role Matrix

The Actor / Role matrix shows which roles map to which actors (people in this case)



Role to Competency Matrix

The Role / Competency matrix shows which roles map to which competencies



Inferring Relationships – Request

Now we can infer relationships from this information



Inferring Relationships – Result

Now we can see the competencies each actor must have




New Requirements


Summary



Summary

System Architect around for a long timeSupport for many EA frameworks has been added, mostly independentlyLooking for development efficiencies in supporting EA frameworks

We’re now part of IBMA broad portfolio of tools in IBM can enhance EA through harvesting and using EAIBM EA Method to support, connects to change programs, operations

Desire for a common metamodelTOGAF 9 metamodel is broad in scope, open and extensibleWe can use the extension mechanism to support existing SA concepts and new concepts not in the TOGAF 9 metamodel

To avoid ivory tower syndrome, make the EA helpful to the change programs and ensure the metamodel can support the vitality process and tool integrations

We still have work to do on our prototype, but so far it’s very promising



© Copyright IBM Corporation 2009. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

Learn more at:IBM Rational softwareRational launch announcementsRational Software Delivery PlatformJazz.net Accelerate change & deliveryDeliver enduring quality

Targeted solutionsRational trial downloadsdeveloperWorks RationalIBM Rational TVIBM Business PartnersIBM Rational Case Studies

Enable enterprise modernizationEnsure Web security & complianceImprove project successManage architectureManage evolving requirementsSmall & midsized business

IBM Software Group - The Open...

Documents

Transcript of IBM Software Group - The Open...