TOGAF - The - The Continuing Story Story

Transcription

1 TOGAF - The - The Continuing Story Story The Open Group Framework (TOGAF) Presented by Chris Greenslade Chris@Architecting-the-Enterprise.com 1 of 53 TA P14 1

2 The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What are our future directions? 2 of 53 TA P14 2

3 Forum The mission of the Forum s members is to: Advance the cause of IT - in order to Improve the quality of information systems To move IT from a cottage industry to a profession Original (and continuing) focus: (TOGAF) Industry consensus framework and method for IT architecture Tool- and technology-neutral Extended focus Tools IT Architect Certification 3 of 53 TA P14 3

4 Who s Who Director John Spencer The Open Group Chair Chris Greenslade Frietuna Computer Consultants (UK) Vice Chairs Ian McCall IBM Global Services (UK) Vish Viswanathan CC & C Solutions (Australia) 4 of 53 David Jackson IBM (USA) TA P14 4

5 The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What are our future directions? 5 of 53 TA P14 5

6 Defining an IT ANSI/IEEE Standard Conceptually an IT is The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution. Practically it is represented in Architectural Descriptions from the viewpoints of the Stakeholders 6 of 53 ANSI/IEEE Standard IEEE Recommended Practice for Architectural Description of Software-Intensive Systems TA P14 6

7 Some more ANSI/IEEE definitions Architect: the person, team, or organisation responsible for systems architecture Architecting: the activities of defining, documenting, maintaining, improving and certifying proper implementation of an architecture. Architectural description a collection of products to document an architecture. 7 of 53 TA P14 7

8 views - definitions System Stakeholder: an individual, team, or organization (or classes thereof) with interests in, or concerns relative to, a system View: a representation of a whole system from the perspective of a related set of concerns Viewpoint: (a schema of the information in a view) acts as a pattern or template from which to develop individual views by establishing the purposes and audience for a view and the techniques for its creation and analysis 8 of 53 TA P14 8

9 view Description of the architecture from the viewpoint of a specific stakeholder The main mechanism of communication between the architect and the stakeholder Used to ensure accuracy of understanding of the current system Used to ensure the architecture meets the need of each stakeholder The collection of views comprises the description of the architecture 9 of 53 TA P14 9

10 We are NOT talking about rocket science We ARE talking about: Using common sense Being systematic Avoiding misunderstandings Knowing what we are doing before we start Knowing why we are doing it Learning from the best practice of others Treating the user as a partner Talking to business users in business terms Recording what, where, when, how, who and WHY Using common sense 10 of 53 TA P14 10

11 The TOGAF Enterprise? TOGAF s Enterprise consists of four types of architecture: Business architecture Information system architectures Data or information architecture Applications architecture TOGAF 8 Enterprise Edition Technology architecture TOGAF 7 Technical Edition 11 of 53 TA P14 11

12 What is the desired benefit of TOGAF? Architected business information systems will have: A greater ability to respond to new demands A greater business value to the organization A greater ability to use new technology A faster, simpler and cheaper procurement process The ability to support a faster time-to-market Can a business succeed without a documented business plan? 12 of 53 Can IT IT succeed without a documented architecture? TA P14 12

13 What is an Architectural Framework? design is a complex process An architectural framework is a tool for: Designing a broad range of a architectures Assisting the evaluation of different architectures Selecting and building the right architecture for an organization It embodies best practice and acknowledged wisdom It presents a set of services, standards, design concepts, components and configurations It guides the development of specific architectures 13 of 53 TA P14 13

14 What is an Architectural Framework? Use of a framework leads to: The use of common principles, assumptions and terminology The development of information systems with better integration and interoperability, especially with respect to issues that affect the whole enterprise WARNING! A framework does not make architectural design an automatic process It is a valuable aid to experienced and knowledgeable IT Architects 14 of 53 TA P14 14

15 The position of IT Architects We know solutions to every problem? What s your problem? How do I know what I want, when I don t know what you can do for me 15 of 53 TA P14 15

16 The position of IT Architects Technical Business IT IT Architects 16 of 53 System Designers & Developers TA P14 16

17 The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What are our future directions? 17 of 53 TA P14 17

18 The story so far The direction of TOGAF s evolution has been driven by The Open Group s membership over a period of 9 years An annual publication cycle 1994: Requirement statement developed Proof of need 1995: X/Open Architectural Framework - version 1 Proof of concept 1996: TOGAF - version 2 Proof of application 1997: TOGAF - version 3 Relevance to practical architectures 18 of 53 TA P14 18

19 The story so far 1998: TOGAF - version 4 TOGAF in context - the Enterprise Continuum Web structured documentation - ease of use 1999: TOGAF - version 5 Re-organized around extended ADM Business scenarios to help define requirements Addition of ADML 2000: TOGAF - version 6 Integration of Building Block work Integration of other initiatives, US DoD, IEEE 1471, IEEE of 53 TA P14 19

20 Current situation Technical Edition 2001: TOGAF - version 7 New sections on Patterns, Principles, Compliance Reviews Significant additional material on Business Scenarios Comparisons of TOGAF with other frameworks Further integration of IEEE Std into TOGAF METIS model of the TOGAF ADM Positioning of TOGAF relative to enterprise architecture 20 of 53 TA P14 20

21 Current situation Enterprise Edition 2002: TOGAF - Version 8 New Enterprise Framework New Business Scenarios section Contracts Extensive Resource facilities including initial Requirements 2003: TOGAF Version 8.1 New requirements management process Expanded Governance New TOGAF Skills Framework 21 of 53 TA P14 21

22 TOGAF consists of An Development Method (ADM) Foundation A Technical Reference Model (TRM) A Standards Information Base (SIB) Building Blocks Information Base (BBIB) Resource Base contains advice on: views Business scenarios IT Governance patterns ADL Case studies TABB principles contracts Requirements Maturity Architect Skills 22 of 53 TA P14 22

23 More about TOGAF Foundation Target s Development Method Technical Reference Model (services) Standards Information Base (standards) Building Block Information Base (future) 23 of 53 Business Requirements TA P14 23

24 development Starting with a foundation architecture, then following the phases of the ADM, results in: an organization-specific architecture; more reusable building block assets in the Enterprise Continuum. The first execution will be the hardest. Each iteration becomes easier and has more reusable building blocks to use. 24 of 53 Architecting-the-Enterprise TA P14 24

25 The ADM Is a comprehensive generalized method. Where necessary it should be tailored to meet the specific needs of an organization: some phases may be unnecessary; some procedures may need modification; some new procedures may need adding; the whole may need to be adapted to interact with other procedures and methodologies. Changes on a positive omission basis: you should have a good reason with a clear justification for making a change; otherwise use the approach recommended by TOGAF. 25 of 53 TA P14 25

26 TOGAF 7 and TOGAF 8 ADM TOGAF 7 G Maintenance F Implementation A Initiation & Framework Requirements B Baseline Description C Target TOGAF 8 A G Vision Change Preliminary Framework & Principles B Business E Migration Planning D Opportunities & Solutions G Implementation Governance Requirements C C Information Information System System s s 26 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 26

27 TOGAF 8 ADM The recommended The information approach generated for Enterprise and consumed by each development Phase consists passed of a between preliminary the phase Phases followed as named by sets a cycle of nine of information. phases. These phases are iterative, both within each phase and between the phases. H Change G Implementation Governance A Vision Requirements Preliminary Framework & Statement of of Principles Work However, this information will Sometimes mainly be in these form of B information models generated sets are by in some the Business form form of of text IT documents that tool. need The to models pass through will be held some in a formal repository acceptance, and displayed or approval, as necessary procedure. by some C form of viewing tool. C Information Information System System s s 27 of 53 F Migration Planning E Opportunities & Solutions D Technology Target Technology Version 1 TA P14 27

28 Prelminary Phase Preliminary Framework & Principles H Change G Implementation Governance A Vision Requirements B Business C C Information Information System System s s This preliminary phase is about defining how IT will be done in the enterprise concerned. There are two main aspects: defining the framework to be used; and defining the architecture principles that will inform any architecture work. 28 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 28

29 Phase A Preliminary Framework & Principles The objective of Phase A is to define the scope; create the vision; identify the stakeholders and obtain approvals. H Change A Vision B Business G Implementation Governance Requirements C C Information Information System System s s 29 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 29

30 Phase B Preliminary Framework & Principles H Change A Vision B Business The objective of Phase B is to describe the current baseline Business and to develop a Target Business G Implementation Governance Requirements C C Information Information System System s s 30 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 30

31 Phase C H Change A Vision Preliminary Framework & Principles B Business The objective of this phase is to develop target architectures For covering the Application either or both (depending on the project objective scope) he goal of the is to Data define and what Application kinds of Systems application domains. systems are The relevant scope to of the the enterprise, business and what processes those supported applications in need this phase to do in order is limited to manage to those data that and are to present supported information by information to the human technology, and computer and the actors interfaces the of those IT-related enterprise. processes to non- IT-related processes. 31 of 53 G Implementation Governance F Migration Planning Requirements E Opportunities & Solutions C C Information Information System System s s D Technology For the Data, the objective is to define the major types and sources of data necessary to support the business, in a way that is understandable by stakeholders and which is complete, consistent and stable. TA P14 31

32 Phase D Preliminary Framework & Principles H Change A Vision B Business 32 of 53 G Implementation Governance F Migration Planning Requirements E Opportunities & Solutions C C Information Information System System s s D Technology The objective of this Phase is to develop a Technology that supports the Business, Data and Application architectures and that will form the basis of the following implementation work. TA P14 32

33 Phase E Preliminary Framework & Principles 33 of 53 H NOTE Change The process of identifying the implementation opportunities sometimes allows a business to identify new applications, and in that case it may be necessary to iterate between Phases D and C. Iteration must be limited G by time or money to avoid Implementation wasting effort for the search Governance of a perfect architecture. F Migration Planning A Vision Requirements E Opportunities & Solutions B Business C C Information Information System System s s D Technology Phase E identifies the parameters of change, the major phases along the way and the top-level projects to be undertaken in moving from the current environment to the target. It will form the basis of the implementation plan required to move to the target architecture. TA P14 33

34 Phase F Preliminary Framework & Principles The objective of Phase F is to sort the various implementation projects into priority order. Activities include assessing the dependencies, costs and benefits of the various migration projects. The prioritized list of projects will go on to form the basis of the implementation plan. H Change G Implementation Governance A Vision Requirements B Business C C Information Information System System s s 34 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 34

35 Phase G The objective of Phase G is to formulate recommendations for each implementation project, and construct an architecture contract to govern the system implementation and deployment. The system is then implemented and deployed during this phase. H Change A Vision Preliminary Framework & Principles B Business G Implementation Governance Requirements C C Information Information System System s s 35 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 35

36 Phase H Preliminary Framework & Principles The objective of Phase H is to establish an Change process for the new Enterprise baseline that is achieved with completion of the Implementation Governance phase. This process will typically provide for the continual monitoring of such things as new developments in technology and changes in the business environment, and for determining whether to formally initiate a new architecture evolution cycle. H Change G Implementation Governance A Vision Requirements B Business C C Information Information System System s s 36 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 36

37 TOGAF 8 ADM Preliminary Framework & Principles H Change A Vision B Business During each Phase, the work is validated against the current business requirements that motivate the development. G Implementation Governance Requirements C C Information Information System System s s 37 of 53 F Migration Planning E Opportunities & Solutions D Technology TA P14 37

38 TOGAF 8 ADM: Phase B Steps B Business 38 of 53 Inputs Request for Work Approved Statement of Work / Project Definition, including in particular: Scope and constraints Refined statements of Business Principles, Business Goals and Strategic Drivers Principles Vision Business Scenarios, including: Business Baseline Version 1 Technical Baseline Version 1 Business Version 1 Technical Version 1 Enterprise Continuum Develop Business Baseline Description Develop Reference Models, Viewpoints and Tools Create Models Select Business Building Blocks Checkpoint Review With Stakeholder Complete Business Produce Gap Analysis & Report B Business Outputs Statement of Work Validated Business Principles, business goals, and strategic drivers Target Business - Version 2 Business Baseline - Version 2 Views corresponding to the selected viewpoints addressing key stakeholder concerns Gap analysis results Technical requirements - drivers for the Technical work: Business Report Updated business requirements TA P14 38

39 The Zachman Framework What? How? Where? Who? When? Why? Planner s Viewpoint Contextual Owner s Viewpoint Conceptual Designer s Viewpoint Logical Builder s Viewpoint Physical Sub-contractor s Viewpoint Out-of-context Data Function Network People Time Motivation Validated Validated Approved statement Validated principles of architecture principles work principles principles Refined Business Business Business Business Correlation of Organization organization Business goals principles principles functions and function structureroles and goals Data model Business baseline version 1 goals & Business Data objectives model drivers managem t drivers processes Gap analysis results managem t Business view Business architecture version 1 Business processes view services Common application Data dissemination services Technical view baseline 1 Application Data Constraints Technology Technical Application architecture user version 0.2 on Target data Target architecture application architecture information lifecycle interop. require- Data Applications lifecycle interoperability Technology location view view information Technical Data architecture technology view security architecture view version version view ments architecture Technology architecture version 0.1 Technology architecture version 0.4 Gap analysis results Scope Enterprise Models Systems Models Technology Models Detailed Representations 39 of 53 Functioning Enterprise Actual Systems TA P14 39

40 A graphical representation of the TRM.. Infrastructure Applications Business Application Application Program Interface Application Platform Communications Infrastructure Interface 40 of 53 Communication Infrastructure TA P14 40

41 Services and Qualities API Application Platform Services Infrastructure Applications Location & Directory Transaction Processing Sys & Net Security Software Engineering Business Application Data Data Interchange International Operations User Interface Graphics & Image Service Qualities 41 of 53 CII Operating System Services Network Services Communication Infrastructure TA P14 41

42 Detailed IIIRM Security Policy Qualities Application Platform Mobility Policy Web Portal Languages Libraries Registries Development Tools Business Modeling Tools Design Tools Construction Tools Languages and Libraries Information Consumer Applications Directory Referencing/Dereferencing Naming, Registration Publish, Subscribe Discovery Brokering Applications Information Brokers Application Integrators Application Message Format Application Messaging Application to Application Communications Services Enterprise Application Integration Desktop Video Conference Streaming Audio/Video Information Access Mail Phone/Fax Utilities Information Brokers Application Integrators Presentation Transformation Browser Services Portal & Personalization Meta Indices 42 of 53 Digital Signature Intrusion Detection Key Firewall Encryption AAAC SSO Web Portal Information Provider Applications Desktop Video Conference Streaming Audio/Video Information Access Mail Phone/Fax Messaging/Event Brokering Info Format eform Services Instant Messaging Services Process/Workflow Control Information Access Transformation Mapping Query Distribution Aggregation Search File Services Web Services Performance SLAs Manageability Policy TA P14 42

43 Standards Information Base (SIB) A complete and up to date database of open industry standards with links to conformant products Standards Information Base publicly available At With user guide Search or full listing Can be used to: Define particular services Define properties of components Be the basis of procurement procedures Keeps the architecture up to date with the latest IT industry consensus 43 of 53 TA P14 43

44 Benefits of TOGAF to the architect Avoids regular reinvention of the wheel Provides a corporate memory of previous successes and failures Ensures completeness of the design process Provides access to accumulated best practice wisdom Avoids communication difficulties within the team The professional approach Best endeavor legal defense - just in case 44 of 53 TA P14 44

45 TOGAF - its key benefits (1) Vendor-Neutral Comprehensive process - from business requirements to applications to infrastructure The result of 9 years of global development Cuts up-front costs - avoids re-inventing the wheel Refined and honed checklists at all levels - from business requirements to physical components The Standards Information Base Maintained, current and comprehensive Standard documented approach insures against the departure of key staff 45 of 53 TA P14 45

46 TOGAF - its key benefits (2) TOGAF is available today under an evaluation license TOGAF is available under a free perpetual license for use within your own organization Third-party users can buy a commercial license or can join the Forum Any member of the Forum can participate in shaping TOGAF s evolution 46 of 53 TA P14 46

47 TOGAF - its key benefits (3) TOGAF is the vendor-neutral, global basis of Certification to impose standards within our profession 47 of 53 TA P14 47

48 The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What are our future directions? 48 of 53 TA P14 48

49 What is our current motivation? The work goes on - new knowledge, new experience, new ideas, new challenges Changes that will influence the future take-up of IT More extended enterprises More co-operative IT operations Tighter IT budgets Global competition More frantic skills chase Increase in litigation Failure can be terminal 49 of 53 TA P14 49

50 What is our current motivation? Pace set by public agencies and large vendors More enforcement of acquisition regulations Clinger-Cohen Act (US Information Technology Reform Act 1996) EU Directives on the Award of Public Contracts Contracting Authority needs procedures for ensuring: Completeness of given business requirements Vendor independent expression of needs Same information to all 50 of 53 TA P14 50

51 The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What are our future directions? 51 of 53 TA P14 51

52 The Forum 52 of 53 Our target is to enable IT Architects to deliver successful and complete practical architectural solutions TOGAF Enterprise Edition Certification of TOGAF Practitioners Professional Services IT Architects TOGAF Technical Edition A quality Technical Framework Knowledgeable Professional Practitioners & Services A World Class Enterprise Framework State of the Art Support Tools & Training Training & Tools Certification TA P14 52

53 The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What are our future directions? 53 of 53 TA P14 53