The Open Group Architecture Framework TOGAF The Continuing

Скачать презентацию The Open Group Architecture Framework TOGAF The Continuing

d276df8ef0407a501a0b67a5c57cebee.ppt

Количество слайдов: 49

The Open Group Architecture Framework (TOGAF) The Continuing Story Presented by Chris Greenslade cjtg@frietuna. com Architecting the Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 1 of 49

The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What is the TOGAF Enterprise Edition? What are our future directions? Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 2 of 49

Architecture Forum The mission of the Forum’s members is to: Advance the cause of IT Architecture - in order to Improve the quality of information systems To move IT Architecture 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 Architecture Tools IT Architect Certification Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 4 of 49

Who’s Who Director John Spencer The Open Group Chair Chris Greenslade Frietuna Computer Consultants (UK) Vice Chairs Barry Smith The MITRE Corporation (USA) Ian Mc. Call IBM Global Services (UK) Vish Viswanathan CC & C Solutions (Australia) Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 5 of 49

Forum Membership Architecting the Enterprise (UK) Frietuna Consultants (UK) BMC Software Inc. (US) Hewlett-Packard (US) Boeing Corporation (US) Hitachi (Japan) Booz Allen & Hamilton (US) IBM (US) Brandeis University (US) Innenministerium Nord. Rhein-Westfalen (Ger) CC and C Solutions ((Aus) Jet Propulsion Labs (US) Centre For Open Systems (Aus) Lockheed Martin (US) Chi. Surf (Hong Kong) MEGA International (Fr) Computacenter (UK) Ministry of Defence (UK) Computas (Nor) Mitre Corporation (US) Computer Associates (US) Monash University (Australia) Conclusive Logic (US) Motorola (US) Department of Defense / DISA (US) NASA Goddard Space Flight Center (US) Department of Works and Pensions (UK) National Computerization Agency (Korea) Desktop Management Task Force (US) NATO C 3 Agency (Bel) Fujitsu (Japan) NEC (Japan) Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 6 of 49

Forum Membership NEMMCO (Australia) Toyota Info. Technology Center (Japan) Ne. Traverse, Inc. (US) TRON Association (Japan) Nexor, Inc. (US) University of Plymouth (UK) Open GIS Consortium, Inc. (US) University of Reading (UK) PASS Network Consulting (Ger) Popkin Software and Systems, Inc. (UK) US Army Weapon Systems Technical Working Group (WSTAWG) (US) POSC (US) Veriserve Corporation (US) Predictive Systems AG (Ger) Visa International (US) Primeur (Italy) Weblayers, Inc (US) Re. GIS (Japan) Westpac Banking Corporation (Australia) QA Consulting (UK) SCO (US) Sun Microsystems (US) Teamcall (Bel) The Terasoft Group (US) 57 Tivoli (US) Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 7 of 49

Defining an IT Architecture ANSI/IEEE Standard 1471 -2000 Conceptually an IT Architecture 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 9 of 49

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. Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 10 of 49

Architecture 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 11 of 49

Architecture 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 12 of 49

Architecture 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 13 of 49

The Zachman Framework What? How? Where? Who? When? Why? Data Function Network People Time Motivation Planner’s Viewpoint Validated Approved statement principles Validated of architecture work Architecture principles Business Contextual Business Correlation of organization Organization Business goals and function structureroles Data model Owner’s Viewpoint Data model Business baseline version 1 objectives Gap managem’t processes analysis results managem’t Business Conceptual Business architecture version 1 view processes Business services Designer’s Common application services view Data disseminationarchitecture version 0. 2 Technical baseline version 1 Data Application Technology view Application user Viewpoint Target data architecture Target application architectureinterop. information lifecycle location view Applications interoperability view Data lifecycle. Technology architecture version 0. 3 1 view Applications information view. Technicalsecurity view version Data architecture Logical Builder’s Viewpoint Physical Technology architecture version 0. 1 Sub-contractor’s Viewpoint Out-of-context Functioning Enterprise Architecting-the-Enterprise Limited Copyright © 2003 Refined Business principles goals & drivers Constraints Technical on requiretechnology ments architecture Technology architecture version 0. 4 Gap analysis results Scope Enterprise Models Systems Models Technology Models Detailed Representations Actual Systems TOGAF - The Continuing Story 14 of 49

What is an Enterprise Architecture? An Enterprise Architecture is the technical foundation of an effective IT strategy It consists of four types of architecture: Business architecture Information system architectures TOGAF 8 Data or information architecture Enterprise Edition Application architecture TOGAF 7 Technical Edition Technology architecture All these are related Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 15 of 49

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? Can IT succeed without a documented architecture? Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 16 of 49

What is an Architectural Framework? Architecture 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 17 of 49

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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 18 of 49

The position of IT Architects We know solutions to every problem? What’s your problem? Architecting-the-Enterprise Limited Copyright © 2003 How do I know what I want, when I don’t know what you can do for me TOGAF - The Continuing Story 19 of 49

The position of IT Architects Technical Management Business Management IT Architects System Designers & Developers Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 20 of 49

The story so far The direction of TOGAF’s evolution has been driven by The Open Group’s membership over a period of 8 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 22 of 49

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 Do. D, IEEE 1471, IEEE 1003. 23 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 23 of 49

Current situation Tech nica l Ed ition 2001: TOGAF - version 7 New sections on Architecture Patterns, Architecture Principles, Architecture Compliance Reviews Significant additional material on Business Scenarios Comparisons of TOGAF with other frameworks Further integration of IEEE Std 1471 -2000 into TOGAF Metis model of the TOGAF ADM Positioning of TOGAF relative to enterprise architecture 2002: TOGAF - Version 8 Architecting-the-Enterprise Limited Copyright © 2003 Ente rpris e Ed ition TOGAF - The Continuing Story 24 of 49

TOGAF consists of An Architecture Development Method (ADM) Foundation Architecture A Technical Reference Model (TRM) A Standards Information Base (SIB) Building Blocks Information Base (BBIB) Resource Base contains advice on: Architecture views Business scenarios IT Governance Architecture patterns ADL Case studies TABB Architecture principles Architecture contracts . . . Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 25 of 49

More about TOGAF Foundation Architecture Target Architectures Architecture Development Method Technical Reference Model (services) Standards Information Base (standards) Building Block Information Base (future) Business Requirements Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 26 of 49

Architecture Development Method ni stluse. R cificeps-noitazinagro na erutcetihcra kcolb gnidliub elbasuer erom esirpretn. E eht ni stessa muunitno. C dna reisae semoceb noitareti hca. E ot skcolb gnidliub elbasuer erom sah esu Start with a foundation architecture A Initiation & framework Follow the phases of the ADM stnemeriuqe. R G Architecture maintenance F Implementation E Migration options Architecting-the-Enterprise Limited Copyright © 2003 B Baseline description C Target architecture D Opportunities & solutions

Technical Reference Model Infrastructure Applications Business Application Program Interface Application Platform Communications Infrastructure Interface Communication Infrastructure Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 28 of 49

Services and Qualities Infrastructure Applications Business Application API Service Qualities Graphics & Image Data Management Data Interchange International Operations User Interface Location & Directory Transaction Processing Sys & Net Management Security Software Engineering Application Platform Services Operating System Services Network Services CII Communication Infrastructure Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 29 of 49

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 http: //www. opengroup. org/sib 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 30 of 49

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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 31 of 49

TOGAF - its key benefits (1) Vendor-Neutral Comprehensive process - from business requirements to applications to infrastructure The result of 8 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 32 of 49

TOGAF - its key benefits (2) TOGAF is available today under an evaluation license http: //www. opengroup. org/architecture/togaf 7/index 7. htm http: //www. opengroup. org/architecture/togaf 8/index 8. htm 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 Architecture Forum Any member of the Architecture Forum can participate in shaping TOGAF’s evolution Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 33 of 49

TOGAF - its key benefits (3) TOGAF 7 is the vendor-neutral, global basis of Certification to impose standards within our profession Architecture tools which support TOGAF 7 Training courses which instruct in TOGAF 7 Architects trained in the use of TOGAF 7 Professional services offered to support TOGAF 7 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 34 of 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 Architecture More extended enterprises More co-operative IT operations Tighter IT budgets Global competition More frantic skills chase Increase in litigation Failure can be terminal Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 36 of 49

What is our current motivation? Pace set by public agencies and large vendors More enforcement of acquisition regulations Clinger-Cohen Act (US Information Technology Management 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 Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 37 of 49

What is the Enterprise Edition? An Enterprise Architecture is the technical foundation of an effective IT strategy It consists of four types of architecture: Business architecture Information system architectures TOGAF 8 Data or information architecture Enterprise Edition Application architecture TOGAF 7 Technical Edition Technology architecture All these are related Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 39 of 49

Preliminary steps (1) Getting the buy-in The most difficult stage The most important stage Establishing the Architectural Framework Customizing, configuring and selecting options suitable for the organization Providing a foundation for the framework by establishing: Architecture principles – to guide all future work on all future architectures IT Governance Architecture compliance procedures Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 41 of 49

Preliminary steps (2) Integrating the framework with existing procedures Preserving tried, trusted, or mandated procedures Choosing the tools Training the staff - architects and others Creating a repository for Building Blocks (BBIB? ) Monitored pilot project Built-in leeway to allow for familiarization and fine-tuning Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 42 of 49

The Enhanced ADM G Architecture Change Management G Implementation Governance F Migration Planning Architecting-the-Enterprise Limited Copyright © 2003 A Architecture Vision Requirements Management E Opportunites & Solutions Preliminary Framework & Principles B Business Architecture C C Information System Architectures D Technology Architecture TOGAF - The Continuing Story 43 of 49

Integrated Information Infrastructure Reference Model Security Policy Qualities Application Platform Mobility Policy Information Consumer Applications Development Tools Brokering Applications Management Utilities Information Provider Applications Performance SLAs Architecting-the-Enterprise Limited Copyright © 2003 Manageability Policy TOGAF - The Continuing Story 44 of 49

Transition policy TOGAF 7 - frozen and retained as the version for Technology Architectures TOGAF 8 - the first release of the Enterprise Edition Feedback needed on the ADM as applied to the Business, Data and Application Architectures Future releases will strengthen and work harden the Enterprise Edition until it can become a basis for Certification Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 45 of 49

The Architecture Forum Striving to achieve a total, practical, architectural solution Certification of Training courses TOGAF practitioners Professional Services A good IT Architects architecture framework Knowledgeable and professional practitioners Architecting-the-Enterprise Limited Copyright © 2003 TOGAF X Enterprise Edition Tools Certification Support tools at all levels TOGAF - The Continuing Story 47 of 49

What are our future directions? Evolution of TOGAF – Enterprise Edition Bring to maturity Establish TOGAF X Certification And possibly: Enhance to align with OMG’s MDA Enhance to include mobility features Enhance to support Quality of Service Align with Zachman Framework Enhance to include industry TRMs Establishment of IT Architect Certification Develop the distributed BBIB Promote, support, advise and get it all into use. Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 48 of 49

The questions to answer Who are we? What principles have we adopted? What have we achieved so far? What is our current motivation? What is the TOGAF Enterprise Edition? What are our future directions? Any questions? Architecting-the-Enterprise Limited Copyright © 2003 TOGAF - The Continuing Story 49 of 49