Top Banner
Elements of a straight-foward approach to Enterprise Architecture OR… Why do we need an EA perspective? 2/15/2011 Christopher Geraghty Sr. Consultant, PSC Group, LLC [email protected]
22

Ea citag presentation final

Jan 23, 2015

Download

Technology

CITAG EA presentation deck for overview of three EA frameworks and practical tips in using EA
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Ea citag presentation   final

Elementsof a straight-foward approach

toEnterprise Architecture

OR… Why do we need an EA perspective?

2/15/2011Christopher GeraghtySr. Consultant, PSC Group, LLC

[email protected]

Page 2: Ea citag presentation   final

Agenda

PART I• Overview of EA Methods• What EA Addresses• Role for Technology Change• Role for Business Change

PART II• Practical Tips and Techniques

PART III• Interactive Group Discussion

Page 3: Ea citag presentation   final

Part I – Overview of EA Methods

TOGAFZachman

TMForum Frameworks/eTOM/SID/NGOSS

eTOM

SID

Page 4: Ea citag presentation   final

Part I – Overview of EA Methods

TOGAF

Business vision and

drivers

Business Capabilities

TOGAF Capability Framework

TOGAF Enterprise Continuum and Tools

Page 5: Ea citag presentation   final

Part I – Overview of EA Methods

TOGAF

Page 6: Ea citag presentation   final

Enterprise Architecture approach - TOGAF v9There are seven main parts to the TOGAF document:

1. PART I (Introduction) This part provides a high-level introduction to the key concepts of enterprise architecture and in particular the TOGAF approach. It contains the definitions of terms used throughout TOGAF and release notes detailing the changes between this version and the previous version of TOGAF

2. PART II (Architecture Development Method) This part is the core of TOGAF. It describes the TOGAF Architecture Development Method (ADM) - a step-by-step approach to developing an enterprise architecture

3. PART III (ADM Guidelines and Techniques) This part contains a collection of guidelines and techniques available for use in applying TOGAF and the TOGAF ADM

4. PART IV (Architecture Content Framework) This part describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable architecture building blocks, and an overview of typical architecture deliverables

5. PART V (Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise

6. PART VI (TOGAF Reference Models) This part provides a selection of architectural reference models, which includes the TOGAF Foundation Architecture, and the Integrated Information Infrastructure Reference Model (III-RM)

7. PART VII (Architecture Capability Framework) This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture function within an enterprise

The intention of dividing the TOGAF specification into these independent parts is to allow for different areas of specialization to be considered in detail and potentially addressed in isolation. Although all parts work together as a whole, it is also feasible to select particular parts for adoption whilst excluding others. For example, an organization may wish to adopt the ADM process, but elect not to use any of the materials relating to architecture capability.

Page 7: Ea citag presentation   final

Part I – Overview of EA Methods

Zachman

Page 8: Ea citag presentation   final

Part I – Overview of EA Methods

Zachman

Page 9: Ea citag presentation   final

There are six domains to the Zachman Framework:

1. Data - What

2. Function - How

3. Network - Where

4. People - Who

5. Time - When

6. Motivation - Why

There are five roles mapped to the six domains in the Zachman Framework:

1. Planner - Scope - Contextual

2. Owner - Business Model - Conceptual

3. Designer - System Model - Logical

4. Builder - Technology Model - Physical

5. Sub-Contractor - Detailed Representations – Out-of-context

Part I – Overview of EA Methods

Zachman

Page 10: Ea citag presentation   final

Part I – Overview of EA Methods

Zachman

Page 11: Ea citag presentation   final

Part I – Overview of EA Methods

tmforum

frameworks

Page 12: Ea citag presentation   final

Part I – Overview of EA Methods

tmforum

eTOM

Page 13: Ea citag presentation   final

Part I – Overview of EA Methods

tmforum

SID

Page 14: Ea citag presentation   final

Part I – What EA Addresses

• Technology and Business Strategy

• Roadmap alignment

• Standardization

• Future-proofing

Page 15: Ea citag presentation   final

Part I – Role for Technology Change

IT analyzes and recommends best solutions based on business needs

• ROI• Least COST• Grow Revenue• Contain costs• Outsource• Buy vs. Lease• COTS vs Opensource

Page 16: Ea citag presentation   final

Part I – Role for Business Change

EA provides a bridge for Business and IT alignment

• executive decision support• guiding principles• technology usage and guidance• idea generation by usage and enablement• collaboration

Page 17: Ea citag presentation   final

Part I – Develop a playbook

Playbook (EAEC)

• TOC• Who we are• What we do• Metric Scorecard and Breakout• Communication Plan• Appendix• Glossary• Library Location/Architecture Repository

Page 18: Ea citag presentation   final

Part II – Practical Tips and Techniques

• Pick an approach

• Define Guiding Principles

• Pick most important area of Technology

• Pick most important Business Requirements

• Pick most important change to the organization

Page 19: Ea citag presentation   final

Part II – Practical Tips and Techniques

Discovery Assessment Design Implementation ProcessImprovement

• Research• Collaboration• Discussion• Vendor mtgs• Industry mtgs

• Trends• Emerging Technology• Use Case application• Positions• Viewpoints

• Strategy Development• Roadmap Development• Solution component Design

• Facilitation• Coordination• Project Initiation• Approvals• Socialization• Education• (Architecture Review)• SDLC Gate Checks

• Monitoring• Metric Review• Process Review

• # Visits with vendors• # Visits with industry• # Stakeholder mtgs• # conferences attended• # exec briefings• # exec teleconferences• # trainings attended

• # trends identified• # technology standards reviewed• # use cases mapped• # position papers• # viewpoint papers• # emerging technologies identified

• # strategies developed• # roadmaps developed• # solution designs• # reference architectures• # transition architectures• # future architectures

• # standards approved• # mtgs facilitated• # PIPs• # education sessions• # architecture reviews• #SDLC gate checks approved• # deviations

• # standards monitored• # processes identified• # kpi’s monitored• Performance increase• Performance decrease• # days request turnaround

Tasks

Metrics

Examples:

Page 20: Ea citag presentation   final

Enterprise Architecture - References

TOGAF:http://www.opengroup.org/togaf/http://www.opengroup.org/architecture/togaf8-doc/arch/chap39.htmlhttp://www.opengroup.org/architecture/togaf9-doc/arch/

ZACHMAN:http://www.businessrulesgroup.org/BRWG_RFI/ZachmanBookRFIextract.pdf

TMFORUM:http://www.tmforum.org/

EAEC – Enterprise Architecture Executive Council:https://www.eaec.executiveboard.com/Public/Default.aspx

Page 21: Ea citag presentation   final

Part III – Interactive Group Discussion on topics pertinent to attendees

• Business Analysis and Requirements gathering/systems

• Data Mining and Business Intelligence

• Compliance and Security

• Framework adoption and application

Example topics:

Page 22: Ea citag presentation   final

Thank you for attending