“The Open Group Architecture Framework”的意思、由来-开放百科全书

The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture.^[2] TOGAF is a high level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.

TOGAF was developed starting 1995 by The Open Group, based on DoD's TAFIM. As of 2016, The Open Group claims that TOGAF is employed by 80% of Global 50 companies and 60% of Fortune 500 companies.^[3]

Overview

An architecture framework is a set of tools which can be used for developing a broad range of different architectures.^[4] It should:

The ANSI/IEEE Standard 1471-2000 specification of architecture (of software-intensive systems) may be stated as: "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."

However TOGAF has its own view, which may be specified as either a "formal description of a system, or a detailed plan of the system at component level to guide its implementation", or as "the structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time."

The Architecture Development Method (ADM) is the core of TOGAF which describes a method for developing and managing the lifecycle of enterprise architecture.

History

TOGAF was initiated in the early 1990s as methodology for the development of technical architecture, and has been developed by The Open Group into an extensive enterprise architecture framework.^[6] In 1995, the first version of TOGAF (TOGAF 1.0) was presented. This version was mainly based on the Technical Architecture Framework for Information Management (TAFIM), developed started in the late 1980s by the US Department of Defense.

In December 2001 TOGAF 7, the "Technical Edition", was published.^[7] TOGAF 8 ("Enterprise Edition") was first published in December 2002 and republished in updated form as TOGAF 8.1 in December 2003. Around 2005 TOGAF became a registered trademark of The Open Group.^[8] In November 2006 the Open Group released TOGAF 8.1.1. According to The Open Group, as of February 2011, over 15,000 individuals are [https://togaf9-cert.opengroup.org/home-public TOGAF Certified].^[9] As of April 2018 the official register has over 77,500 certifications[https://togaf9-cert.opengroup.org/certified-individuals].^[10]

An evolutionary development from TOGAF 8, TOGAF 9 includes many new features such as:^[11]^[12]

Additional guidelines and techniques include:{{Citation needed|date=January 2012}}

TOGAF pillars

Enterprise architecture domains

TOGAF is based on four interrelated areas of specialization called architecture domains:

Architecture Development Method

The Architecture Development Method (ADM) is applied to develop an enterprise architecture which will meet the business and information technology needs of an organization. It may be tailored to the organization's needs and is then employed to manage the execution of architecture planning activities.^[16]

The process is iterative and cyclic. Each step checks with Requirements. Phase C involves some combination of both Data Architecture and Applications Architecture. Additional clarity can be added between steps B and C in order to provide a complete information architecture.

Performance engineering working practices are applied to the Requirements phase, and to the Business Architecture, Information System Architecture, and Technology architecture phases. Within Information System Architecture, it is applied to both the Data Architecture and Application Architecture.

Enterprise Continuum

The Enterprise Continuum is a way of classifying solutions and architectures on a continuum that range from generic foundation architectures through to tailored organization-specific both within and outside the Architecture Repository.^[17] These include architectural models, architectural patterns, architecture descriptions, and other artifacts. These artifacts may exist within the enterprise and also in the IT industry at large.

The Enterprise Continuum consists of both the Architecture Continuum and the Solutions Continuum. The Architecture Continuum specifies the structuring of reusable architecture assets and includes rules, representations, and relationships of the information system(s) available to the enterprise. The Solutions Continuum describes the implementation of the Architecture Continuum by defining reusable solutions.

TOGAF culture

TOGAF Certified Tools

Qualifications

The Open Group oversees formal qualifications in TOGAF at two levels, which can be taken following formal training or self-study.^[19] Learners can undertake these qualifications through training companies.

Foundation

(Level I) Ensures that an individual understands Enterprise Architecture along with core concepts and terminology of TOGAF.^[19]

Certified

(Level II) Further to the Foundation qualification, this establishes that the candidate is able to analyse and apply their knowledge to business problems.^[19]

Gaining TOGAF Certified status automatically confers free membership of the Association of Enterprise Architects.^[20]

Criticism

Despite TOGAF being considered as the de facto standard in an EA practice, it is not without its critics:

References

1. ^Stephen Marley (2003). "Architectural Framework," at aiwg.gsfc.nasa.gov, NASA /SCI. Retrieved 10 Dec 2008 ([https://web.archive.org/web/20090320230522/http://aiwg.gsfc.nasa.gov/esappdocs/RPC/RPC_Workshop_Architecture_Framework.ppt webarchive.org]).
2. ^Dirk Draheim, Gerald Weber eds. (2007) Trends in Enterprise Application Architecture: 2nd International Conference, TEAA 2006, Berlin, Germany, November 29 - December 1, 2006, Revised Selected Papers. p. 260
3. ^TOGAF Worldwide
4. ^TOGAF Introduction The Open Group Architecture Framework. Accessed 22 Jan 2009.
5. ^Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996
6. ^Marc Lankhorst (2013) Enterprise Architecture at Work: Modelling, Communication and Analysis p. 23
7. ^Jaap Schekkerman (2003) How to Survive in the Jungle of Enterprise Architecture. p. 119
8. ^Tom van Sante, Hans Van Den Bent (2007) Togaf the Open Group Architectural Framework: A Management Guide. p. iv
9. ^15,000 certifications
10. ^[https://togaf9-cert.opengroup.org/certified-individuals Directory of Certified People]
11. ^{{cite web | url =http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap04.html#tag_04_01 | title =What's New in TOGAF 9? | date =2009 | website = | publisher =The Open Group | access-date = 13 January 2017 | quote = }}
12. ^{{cite web | last = Veryard | first = Richard | title = TOGAF 9 | url = https://rvsoapbox.blogspot.com/2009/02/togaf-9.html | date = 2009 | access-date = 13 January 2017}}
13. ^Gerber A; Van der Merwe, A; Kotze, P: 2010. Towards the Formalisation of the TOGAF Content Metamodel using Ontologies. To appear in: Proceedings of the 12th International Conference on Enterprise Information Systems (ICEIS 2010). INSTICC
14. ^The Open Group Launches the TOGAF® Standard, Version 9.2 http://www.opengroup.org/news/press/The-Open-Group-Launches-TOGAF-Standard-Version-9-2
15. ^The Open Group (2011). TOGAF® Version 9 - Download. Architecture Forum. Retrieved on 2011-11-17 from http://www.opengroup.org/architecture/togaf9/downloads.htm.
16. ^The process flow can be seen as an image located here: Architecture Development Cycle
17. ^{{cite web |url=http://pubs.opengroup.org/architecture/togaf91-doc/arch/chap39.html |title=Enterprise Continuum |website=The Open Group |accessdate=4 January 2014}}
18. ^The Open Group Tool Certification Register
19. ^¹²{{cite web |url=http://www.opengroup.org/togaf9/cert/docs/indiv.html |title=TOGAF 9 Certification |website=The Open Group |accessdate=11 January 2014}}
20. ^{{cite web |url=http://www.opengroup.org/togaf/cert/docs/faq.html |title=TOGAF Certification FAQ |website=The Open Group |accessdate=11 January 2014}}
21. ^"Enterprise architecture is not TOGAF", Kotusev, S., January 2016
22. ^"The critical scrutiny of TOGAF", Kotusev, S., April 2016
23. ^¹Anderson, P., Backhouse, G., Townsend, J., Hedges, M. and Hobson, P. (2009). Doing Enterprise Architecture: Enabling the Agile Institution. Bristol, United Kingdom: Joint Information Systems Committee (JISC).
24. ^Winter, K., Buckl, S., Matthes, F. and Schweda, C. M. (2010). Investigating the State-of-the-Art in Enterprise Architecture Management Methods in Literature and Practice. In: Sansonetti, A., ed. Proceedings of the 4th Mediterranean Conference on Information Systems, Tel Aviv, Israel.
25. ^[https://www.forbes.com/sites/jasonbloomberg/2014/08/07/enterprise-architecture-dont-be-a-fool-with-a-tool/#37025dfd45f1 "Enterprise Architecture: Don't Be a Fool with a Tool"], Jason Bloomberg, visited 19 May 2016
26. ^[https://www.bcs.org/content/conWebDoc/59564 "TOGAF Version 9.2: What's New?"], Kotusev, S., June 2018
27. ^Kotusev, S. (2018) TOGAF: Just the Next Fad That Turned into a New Religion, In: TOGAF Is Not an EA Framework: The Inconvenient Pragmatic Truth, K.L. Smith (ed.). Great Notley, UK: Pragmatic EA Ltd, pp. 27-40.