Using TOGAF™ to architect The Open Group’s systems

30
Drinking our own champagne Using TOGAF™ to architect The Open Group’s systems (C) The Open Group 2009 Allen Brown President & CEO [email protected] 44 Montgomery Street Suite 960 San Francisco, CA 94104 USA Tel +1 415 374 8280 Fax +1 415 374 8293 www.opengroup.org

Transcript of Using TOGAF™ to architect The Open Group’s systems

Page 1: Using TOGAF™ to architect The Open Group’s systems

Drinking our own champagne

Using TOGAF™ to architect

The Open Group’s systems

(C) The Open Group 2009

Allen BrownPresident & CEO

[email protected]

44 Montgomery StreetSuite 960

San Francisco, CA94104 USA

Tel +1 415 374 8280Fax +1 415 374 8293

www.opengroup.org

Page 2: Using TOGAF™ to architect The Open Group’s systems

(C) The Open Group 2009

It’s a consortium

It’s about UNIX®

It manages consortia

It’s a certification authority

It’s about TOGAF™

It’s a standards body

It’s about Interoperability

It’s about Security

It’s Open Standards

It’s about ArchiMate®

It’s about people skills

It’s about Real-time and Embedded

Enterprises join a Council

You join a Forum

Consensus process

It’s Silver, Gold, Platinum

Elected roles

There is a professional body

Page 3: Using TOGAF™ to architect The Open Group’s systems

The Open Group in a

Boundaryless world

(C) The Open Group 2009

Finite resources

Lack of investmentcapital

IncreasedOperational risk

NewProducts & Entities

GrowingSecurity threats

Growing Compliance issues

DevelopExisting staff

Seekmember support

Quest forlow cost solutions

Maintain legacy untilalternative in place

Page 4: Using TOGAF™ to architect The Open Group’s systems

Achievements …. so far

What Benefits Status

Replaced obsolete finance

system

Reduced risk

Reduced effort

Improved readiness for

SOX compliance

Enhanced capability

Enhanced capability being

rolled out

Outsourced credit card

handling

PCI Compliance

Reduced security

vulnerability

Complete

Off-sited servers Reduced operational and

security risk

Partial

CRM Ability to deliver individual

membership

New event registration

system

AOGEA live

Membership live

Event registration in beta

CMS Ability to federate web site

content updates

Undergoing pilot

(C) The Open Group 2009

Page 5: Using TOGAF™ to architect The Open Group’s systems

How we do architecture

Documentation strategy

Corporate intranet

“Plato” site

Guidance from

members

Chris Greenslade

TOGAF

Chris Armstrong

UML, BPMN

(C) The Open Group 2009

Page 6: Using TOGAF™ to architect The Open Group’s systems

How we do architecture

Framework and Principles

Framework Definition

IT Governance

(C) The Open Group 2009

Page 7: Using TOGAF™ to architect The Open Group’s systems

Operating model

Highlights the operational services and the phase of

migration in which they would be addressed

Facilitates federation / parallel activity in a governed manner

Avoid the centralized activity bringing everything else to a halt

(C) The Open Group 2009

Page 8: Using TOGAF™ to architect The Open Group’s systems

Principles

Based on TOGAF model Title

Statement

Rationale

Implications

Developed by Internal Architecture Board Business continuity

Custodianship

Citizenship

Anyplace, anytime

Self-serve (gas pump)

One source

De-customization

Preference for standards

Painless user experience

(C) The Open Group 2009

Page 9: Using TOGAF™ to architect The Open Group’s systems

Phase A - Vision

Inputs Outputs

Outputs from Preliminary Phase Refined

Business priorities Scope for this iteration

Business Constraints Constraints

High level business scenario Refined business scenario

Legacy architecture assets Baseline & Target Architectures

(C) The Open Group 2009

Page 10: Using TOGAF™ to architect The Open Group’s systems

Business Goals and Drivers

Business drivers and

principles are critical

Constraints can get out of

hand

You need experience to be

SMART

Pilot everything

(C) The Open Group 2009

SMART objectives

Page 11: Using TOGAF™ to architect The Open Group’s systems

Statement of architecture work

(C) The Open Group 2009

Objectives & Priorities

Major milestones

GANTT

Page 12: Using TOGAF™ to architect The Open Group’s systems

Business Architecture

(C) The Open Group 2009

Business Scenario

UML Use Case

MembershipBaseline & target

Page 13: Using TOGAF™ to architect The Open Group’s systems

Enterprise continuum - internal

(C) The Open Group 2009

Legacy from

early work

A reference

collection of

enterprise

architecture

assets

Continuously

enriched

Page 14: Using TOGAF™ to architect The Open Group’s systems

Enterprise continuum - external

Best practices

Technical reference model

(C) The Open Group 2009

Page 15: Using TOGAF™ to architect The Open Group’s systems

Business Architecture

(C) The Open Group 2009

Business Processes Business Services

Page 16: Using TOGAF™ to architect The Open Group’s systems

Applications Architecture

(C) The Open Group 2009

Service interaction model

Baseline

Gap analysis

Page 17: Using TOGAF™ to architect The Open Group’s systems

Data Architecture

(C) The Open Group 2009

Core data entities

Entity relationships

Page 18: Using TOGAF™ to architect The Open Group’s systems

3 September 2009 18

Technology Architecture

Views

Current technology

Remote user

Network

Business Application

Baseline – Reading only

Target –data center only

(C) The Open Group 2009

Page 19: Using TOGAF™ to architect The Open Group’s systems

Phase E:

Opportunities & Solutions

Establish evaluation criteria Relevant principles

Business goals and drivers

Painpoints

Cost

Ability to deliver architecture

Evaluate Solution selection against evaluation criteria

Evaluation Report and recommendations

Governance Review (go – no go – next steps)

Results Selected LAMP based CRM solution

(C) The Open Group 2009

Page 20: Using TOGAF™ to architect The Open Group’s systems

Evaluation Report

(C) The Open Group 2009

Issues

Recommendation

Page 21: Using TOGAF™ to architect The Open Group’s systems

3 September 2009 21

Phase F: Migration Planning

Challenge:

The legacy Membership Database is host to 23+

applications and moving all of these simultaneously was

considered to involve an unacceptable degree of risk

Strategy to overcome challenge:

Create a synchronization mechanism between the new CRM

and the legacy Membership Database

Architectural benefit:

Maintains control of scope

(C) The Open Group 2009

Page 22: Using TOGAF™ to architect The Open Group’s systems

Phase G

Implementation Governance

Ensure approvals are in

place

Architecture Compliance

Review Template

(C) The Open Group 2009

Page 23: Using TOGAF™ to architect The Open Group’s systems

Pilot review and evaluation

(C) The Open Group 2009

Meeting Objectives

Attendees

Agenda

Outcome / Actions

Date

Page 24: Using TOGAF™ to architect The Open Group’s systems

Requirements Management

(C) The Open Group 2009

Application “owner”

Phase H:Architecture Change Management

Initial prioritizationby end user

Principles filterfor enhancements

Bug / enhancementvalidation

Findings reported to BU VP

Constraintscheck

Appeals process

Page 25: Using TOGAF™ to architect The Open Group’s systems

Phase H

Architecture Change Management

(C) The Open Group 2009

Page 26: Using TOGAF™ to architect The Open Group’s systems

Key challenges

Live within existing resources No budget to:

Hire or contract staff for the activity Invest in architecture tools

Business goal Develop existing staff

Recognize that lack of prior experience is an acceptable trade-off

Business reality Give priority to revenue related work

Recognize that architecture work will often be put back

Insufficient resources to complete every detail of the ADM

Life goes on

The world does not stand still while we do this

Stakeholders have day jobs

(C) The Open Group 2009

Page 27: Using TOGAF™ to architect The Open Group’s systems

TOGAF Benefits

Forces you to think at all levels / phases

Avoids the leap to solution space

Prevents build when buy is better

Prevents “fixes” that have unforeseen

consequences

Encourages re-use

Legacy systems all had different registration

processes

(C) The Open Group 2009

Page 28: Using TOGAF™ to architect The Open Group’s systems

Challenges to a small enterprise

Access to affordable expertise

Access to affordable architecture tools

Access to examples, sample materials etc

(C) The Open Group 2009

We could not have achieved half of what we have, without TOGAF to guide us.

Page 29: Using TOGAF™ to architect The Open Group’s systems

BACK-UP

(C) The Open Group 2009

Page 30: Using TOGAF™ to architect The Open Group’s systems

Cube of complexity

(C) The Open Group 2009

Global coverage

Narrow

Broad

Intangible nature

Commonlyunderstood

Tough toexplain

Business model

Forprofit

Nonprofit