1 / 28

TBI and TOGAF Reconciliation Terence Blevins, VP and CIO 10:10 am / Monday May 24 th

Global EAI Summit 2004. TBI and TOGAF Reconciliation Terence Blevins, VP and CIO 10:10 am / Monday May 24 th DC Coleman Room. What Does Reconciliation Mean?. Reconciliation A reconciling or being reconciled Reconcile To bring together again in love or friendship

dinh
Download Presentation

TBI and TOGAF Reconciliation Terence Blevins, VP and CIO 10:10 am / Monday May 24 th

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global EAI Summit 2004 TBI and TOGAF Reconciliation Terence Blevins, VP and CIO 10:10 am/Monday May 24th DC Coleman Room

  2. What Does Reconciliation Mean? • Reconciliation • A reconciling or being reconciled • Reconcile • To bring together again in love or friendship • To induce to accept something disagreeable • To reach a compromise agreement about • To make or show to be consistent • We’ll focus on 4 today – we think that TOGAF and TBI are consistent

  3. Position • TBI and TOGAF ADM are both great candidates for a Global Integration Framework • Why TOGAF ADM • Any large effort requires enterprise architecture • Doing enterprise architecture requires an architecture development method • An enterprise architecture method will include consideration of integration given the appropriate situation – in most cases • An open architecture method is less likely to create new integration challenges • Why TBI • Any large project requires integration implementation plans • TBI is a proven method for dealing with integration details • What can be done downstream… harden the points of interaction between TOGAF ADM and TBI to ensure interoperability

  4. A Definition of Enterprise Architecture • The structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time • Enterprise architecture • Covers the components in an enterprise • organizations, processes, humans, data, applications, technology etc. • Enterprise means enterprise-wide, not everything in the enterprise … An enterprise architecture effort must address a specific problem, not all problems at once!

  5. The Role of Architecture • “Architecture is fast becoming one of the main instruments for improving Business IT Alignment.” • “It is time to broaden our view and build systems that last and that keep delivering value to the business. Business and IT Architecture play a pivotal role in achieving this goal..“ Raymond Slot M.Sc, MBA, Principal Consultant and Enterprise Architect for Cap Gemini Ernst & Young

  6. Pressures on IT … Understand where change is needed • Align Information Technology to Business • Increase accountability to improve cost performance • Drive accountability of spending • Ensure network availability • Ensure security • Drive standardization What direction is appropriate What process are in most need of support How do we keep alignment How do we impact what is being deployed How do we ensure information security Create Alignment How do we incorporate a new system How do we ensure that the technical components are fit How do we pick the right solutions and ensure support for stds

  7. Other Pressures … Understand where change is needed • Effective business process to reconcile and adequately govern • Short term spending • Short product life cycles • Rapid technological change • Sub-optimal spending • Dealing with “hidden” costs • Sub-optimal vendor management What direction is appropriate What process are in most need of support How do we keep alignment How do we impact what is being deployed How do we ensure information security Create Alignment How do we incorporate a new system How do we ensure that the technical components are fit How do we pick the right solutions and ensure support for stds

  8. And the Impact? Understand where change is needed • Proliferation of point solutions • High costs of integration • Not leveraging standards • Few discount deals • Higher support costs • Less responsive support • High costs and long lead times to deliver security • Higher risk of security • Disconnected decisions • Lack of effectiveness What direction is appropriate What process are in most need of support How do we keep alignment How do we impact what is being deployed How do we ensure information security Create Alignment How do we incorporate a new system How do we ensure that the technical components are fit How do we pick the right solutions and ensure support for stds

  9. Prelim: Framework and Principles AArchitecture Vision H ArchitectureChange Management BBusiness Architecture Requirements CInformation System Architectures G Implementation Governance F MigrationPlanning DTechnology Architecture EOpportunitiesand Solutions TOGAF 8 ADM • Designed to address key issues! • Lowering costs • Control costs • Delivering new value • Better operational efficiency of business • Better understand impact of change • Holistic requirements management • Lower risk • Faster decisions • The journey provides benefits at each step! http://www.opengroup.org/architecture/togaf8/index8.htm

  10. TBI Deliverables Map DEFINE DESIGN BUILD DEPLOY Business Process Analysis Tech Req Document Business Analyst Unit Test Integration Software QA Plan Req WT report Test Results Results Quality Manager Logical Integration Integration Design WT System Test Cases System Test Cases Report WT Report Test Result Error Integration Logical Handling Architect. TDB Design Design Guide Architect / Designer Document Code Reviews Simulation Document Unit Test Source Developer Cases Code Lessons Learned FDR Rpt FDR Rpt FDR Rpt FDR Rpt Governance Repository CTQ Signoff Repository Repository Repository

  11. TOGAF ADM Deliverables Map PD DP TP EC RFAW EFW BD RFC EC EC RFAW SOW IGS EC SD AP RFAW RFAW SOW TISA BD RFAW TD BS TTA RFAW BS SOW TISA AP RFAW SOW RFC BA2 EC AP BS BA2 BA2 I I I I I I I I I I Prel Phase Phase A Phase B Phase C Phase D Phase E Phase F Phase G Phase H Reqs Mgmt O O O O O O O O O O BD BD BD IA TP IA IA AC RFAW SRS FWD SOW SOW TISA TTA IA AP BS BA2 BA2 BA1 AP External Input BD:Business Data EFW:External Frameworks IGS:IT Govern Strategy PD:Product Definitions RFC:Req for Changes SD:Standards Devs TD:Tech Devs Internal Input AP:Arch Principles FRAW:Req for Arch Work EC:Enterprise Continuum DP:Data Principles TP:Technical Principles ABL:Application Baseline DBL:Data Baseline Output BD:Business Data FWD:Framework Definition AP:Arch Principles BS:Business Scenario BA:Business Architecture SOW:Statement Of Work TISA:Target IS Architecture TTA:Target Tech Arch IA:Impact Analysis AC:Architecture Contract SRS:Structured Req Statement

  12. Intersections at… DEFINE DESIGN BUILD DEPLOY Business Process Analysis Tech Req Document Business Analyst Unit Test Integration Software QA Plan Req WT report Test Results Results Quality Manager Logical Integration Integration Design WT System Test Cases System Test Cases Report WT Report Test Result Error Integration Logical Handling Architect. TDB Design Design Guide Architect / Designer Document Code Reviews Simulation Document Unit Test Source Developer Cases Code Lessons Learned FDR Rpt FDR Rpt FDR Rpt FDR Rpt Governance Repository CTQ Signoff Repository Repository Repository http://www.opengroup.org/architecture/togaf8/index8.htm

  13. TOGAF ADM Feeds to TBI PD DP TP EC RFAW EFW BD RFC EC EC RFAW SOW IGS EC SD AP RFAW RFAW SOW TISA BD RFAW TD BS TTA RFAW BS SOW TISA AP RFAW SOW RFC BA2 EC AP BS BA2 BA2 I I I I I I I I I I Prel Phase Phase A Phase B Phase C Phase D Phase E Phase F Phase G Phase H Reqs Mgmt O O O O O O O O O O BD BD BD IA TP IA IA AC RFAW SRS FWD SOW SOW TISA TTA IA AP BS BA2 BA2 BA1 AP External Input BD:Business Data EFW:External Frameworks IGS:IT Govern Strategy PD:Product Definitions RFC:Req for Changes SD:Standards Devs TD:Tech Devs Internal Input AP:Arch Principles FRAW:Req for Arch Work EC:Enterprise Continuum DP:Data Principles TP:Technical Principles ABL:Application Baseline DBL:Data Baseline Output BD:Business Data FWD:Framework Definition AP:Arch Principles BS:Business Scenario BA:Business Architecture SOW:Statement Of Work TISA:Target IS Architecture TTA:Target Tech Arch IA:Impact Analysis AC:Architecture Contract SRS:Structured Req Statement

  14. Prelim: Framework and Principles AArchitecture Vision H ArchitectureChange Management BBusiness Architecture Requirements CInformation System Architectures G Implementation Governance F MigrationPlanning DTechnology Architecture EOpportunitiesand Solutions Summary • TBI and TOGAF ADM are both great for GIF • Any large effort requires enterprise architecture and doing so requires an open ADM • Enterprise architecture method includes consideration of integration • An open architecture method is less likely to create new integration challenges • Any large project requires integration implementation plans • TBI is a proven method for dealing with integration details • We can harden the points of interaction between TOGAF ADM and TBI to ensure interoperability for GIF • Leverage will get us all to the top! http://www.opengroup.org/architecture/togaf8/index8.htm

  15. Contact Details 44 Montgomery Street Suite 960 San Francisco, CA 94104 USA Tel +1 415 374 8280 ext. 231 Fax 413-683-4199 www.opengroup.org Terence Blevins VP and CIO Mobile +1 650 888 6950 t.blevins@opengroup.org TOGAF 8 represents an industry consensus framework and method for Enterprise Architecture that is available for use internally by any organization around the world - members and non-members of The Open Group alike - under a free, perpetual license. http://www.opengroup.org/architecture/togaf8/index8.htm

  16. Backups

  17. Presentation Outline • Background • Why Enterprise Architecture is Important • TOGAF and TOGAF History • TOGAF and TBI • Summary

  18. Integration Is a Big Issue • Gartner Dataquest forecasts Worldwide End-User IT Spending will grow • from $2.7 US trillion in 2001 • to greater than $3.0 US trillion in 2002 and • reach $3.4 US trillion in 2003 • The worldwide integration services market is expected to see a 25% compounded annual growth rate between 2001 and 2005 to $116.5 US billion, according to IDC • CIO magazine survey says companies spend over 35% on integrating systems and processes

  19. Presentation Outline • Background • Why Enterprise Architecture is Important • TOGAF and TOGAF History • TOGAF and TBI • Summary

  20. CIOs Have Issues in Common • In general there is a trend • Demands on IT increasing • IT budgets are decreasing or flat • CIOs must do more for less, so • Look for leverage • Outsourcing • Off shore development • Open source • Collaborative development • Reusable building blocks… IT demand Ever widening gap! IT budget - run rates are declining!

  21. Presentation Outline • Background • Why Enterprise Architecture is Important • TOGAF and TOGAF History • TOGAF and TBI • Summary

  22. TOGAF 8 Scope • TOGAF covers the development of four related types of architecture: • Business architecture • Data or information architecture • Application architecture • Technology architecture TOGAF 8“Enterprise Edition” TOGAF 7 “Technical Edition” TOGAF 7 “Technical Edition”

  23. TOGAF 8 – Enterprise Edition Target Enterprise Architectures Architecture Development Method Enterprise Continuum Resource Base

  24. Prelim: Framework and Principles AArchitecture Vision H ArchitectureChange Management BBusiness Architecture Requirements CInformation System Architectures G Implementation Governance F MigrationPlanning DTechnology Architecture EOpportunitiesand Solutions Enterprise ADM • An iterative method • Each iteration = new decisions: • Enterprise coverage • Level of detail • Time period • Architecture asset re-use • Decisions based on: • Competence / resource availability • Value accruing to the enterprise.

  25. The Enterprise Continuum Technology Architecture Continuum Foundation Architectures Industry Architectures Organisation Architectures Common Systems Architectures Guides & Supports Guides & Supports Guides & Supports Guides & Supports Products &Services SystemsSolutions Industry Solutions Organisation Solutions Solutions Continuum

  26. Resource Base • Architecture Compliance Reviews • Architecture Principles • Architecture Views • Architecture Tool evaluation criteria • Business Scenarios • Architecture Governance • Case Studies • Comparisons with other Frameworks • Mapping to Zachman Framework

  27. TOGAF Origins • A customer initiative • A framework, not an architecture • A framework for developing architectures to meet different business needs • Not a “one-size-fits-all” architecture • Originally based on Technical Architectural Framework for Information Management (TAFIM) from US Department of Defense

  28. TOGAF Development Proof of need Proof of concept Proof of application Relevance to practical architectures (building blocks) Enterprise Continuum (TOGAF in context) Business Scenarios (architecture requirements) Architecture views - IEEE 1471 Architecture Principles; Compliance Reviews Extension for Enterprise Architecture • 1994: Requirement • 1995: TOGAF Version 1 • 1996: TOGAF Version 2 • 1997: TOGAF Version 3 • 1998: TOGAF Version 4 • 1999: TOGAF Version 5 • 2000: TOGAF Version 6 • 2001: TOGAF Version 7 • 2002: TOGAF Version 8

More Related