The Open Group Architecture Framework （企业架构-TOGAF介绍）

 

中文可以参见：http://www.cnblogs.com/zhoujg/archive/2010/01/23/1654721.html

 

The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides a comprehensive approach to the design, planning, implementation, and governance of an enterprise information architecture.

TOGAF is a high level and holistic approach to design, which is typically modeled at four levels: Business, Application, Data, and Technology. It tries to give a well-tested overall starting model to information architects, which can then be built upon. It relies heavily on modularization, standardization and already existing, proven technologies and products.

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

• describe a method for defining an information system in terms of a set of building blocks
• show how the building blocks fit together
• contain a set of tools
• provide a common vocabulary
• include a list of recommended standards
• include a list of compliant products that can be used to implement the building blocks

TOGAF is such an architecture framework.

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."

Enterprise architecture domains

TOGAF is based on four pillars, called architecture domains:

• Business architecture or business process architecture which defines the business strategy, governance, organization, and key business processes of the organization
• Applications architecture which provides a blueprint for the individual application systems to be deployed, the interactions between the application systems, and their relationships to the core business processes of the organization with the frameworks for services to be exposed as business functions for integration.
• Data architecture which describes the structure of an organization's logical and physical data assets and the associated data management resources
• Technical architecture or technology architecture which describes the hardware, software and network infrastructure needed to support the deployment of core, mission-critical applications

[edit] 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.^[5]

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.

[edit] Enterprise Continuum

The Enterprise Continuum may be viewed as a "virtual repository" (As of TOGAF 9 this not virtual any more) of all the architecture assets available to an organization. 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 building blocks.

[edit] TOGAF 8 Certified Tools

• alfabet planningIT
• Orbus Software (iServer)^[6]
• EVA Netmodeler^[7]
• IDS Scheer^[8]
• BiZZdesign Architect ^[9]
• Avolution ABACUS 3.x or later ^[10]
• Casewise Corporate Modeller 10.3 or later
• Flashmap Systems IT atlas v1
• Future Tech Systems, Inc.^[11]
• MEGA International ^[12]
• Metastorm ProVisionEA Version 6 or later
• IBM Rational System Architect 10 or later ^[13]
• MooD 2006, 2008, 2008se, 2010, 2010 SP1 or later ^[14] - The Salamander Organization
• Troux Metaverse 7.1 or later^[15]
• Sparx Systems ^[16]

For the latest register of TOGAF 8 Certified tools see The Open Group register ^[17].

转载于:https://www.cnblogs.com/mengheyun/archive/2011/02/14/1954330.html