TOGAFStudyGuideFullversion.doc

《TOGAFStudyGuideFullversion.doc》由会员分享，可在线阅读，更多相关《TOGAFStudyGuideFullversion.doc（9页珍藏版）》请在三一办公上搜索。

1、TOGAF_Study_Guide_FullversionTOGAF 9 Foundation Study Guide1. Basic Concepts1) What is TOGAF?TOGAF The Open Group Architecture, developed and maintained by The Open Group Architecture Forum is a tool for assisting in the acceptance, production, use, and maintenance of enterprise architectures. It is

2、 based on an iterative process model supported by best practices and a re-usable set of existing architectural assets.2) What is an enterprise?A collection of organizations that share a common set of goals, such as a government agency, part of a corporation, or a corporation in its entirety.Large co

3、rporations may comprise multiple enterprises.An “extended enterprise” can include partners, suppliers, and customers.3) What is enterprise architecture?EA is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firms ope

4、rating model; Source: MIT Center for Information Systems researchEA is a conceptual blueprint that defines the structure and operation of an organization. The intent of enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives; Source:

5、 SearchCIO.com4) Why do I need enterprise architecture? What are the business benefits?The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes into integrated environment that is responsive the constantly changing business needs and suppor

6、tive of the delivery of the business strategy. And also the effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage.Benefits of the EA: a) Lower costs of software development, support and maint

7、enanceb) Increased portability of applicationsc) Improved interoperability and easier system and network managementd) Improved ability to address critical enterprise-wide issues, such as securitye) Easier upgrade and exchange of system components a) Reduced complexity in IT infrastructureb) Maximum

8、return on investment in existing IT infrastructurec) The flexibility to make, buy or out-source IT solutionsd) Reduced risk overall in new investment and the costs of IT ownership a) Buying decisions are simpler, because the information governing procurement is readilyavailable in a coherent planb)

9、The procurement process is faster, maximizing procurement speed and flexibility withoutsacrificing architectural coherencec) The ability to procure heterogeneous, multi-vendor open systemsUltimately, the benefits of enterprise architecture derive from the , and that result when it is introduced.5) W

10、hat is “architecture” in the context of TOGAF?A formal description of a system, or a detailed plan of the system component level to guide its implementationThe structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over timeArchitec

11、ture is defined as “the fundamental organization of something, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution”.6) What is an architecture framework?An architecture framework is a that can be used for , it shoul

12、d: Describe a method for designing an information system in terms of a set of building blocks, and forshowing how the building blocks fit together Contain a set of tools and provide a common vocabulary Include a list of recommended standards and compliant products that can be used to implementthe bu

13、ilding blocks7) Why do I need a framework for enterprise architecture?Using an architecture framework will speed up and simplify architecture development, ensure more complete coverage of the designed solution and make certain that the architecture selected allows for future growth in response to th

14、e needs of the business.8) Why is TOGAF suitable as a framework for enterprise architecture?TOGAF has been developed through the collaborative efforts of more than 300 Architecture Forum member companies from some of the worlds leading IT customers and vendors and represents best practice in archite

15、cture development. Using TOGAF as the architecture framework will allow architectures to be developed that are consistent, reflect the needs of stakeholders, employ best practice, and give due consideration both to current requirements and to the likely future needs of the business.Enterprise archit

16、ecture development is a technically complex process, and the design of heterogeneous, multi-vendor architectures is particularly complex. TOGAF plays an important role in helping to “de-mystify” and de-risk the architecture development process. It also provides a platform for adding value, and enabl

17、es users to build genuinely open systems-based solutions to address their business issues and needs.9) What does TOGAF contain?TOGAF reflects the structure and content of an architecture capability within an enterprise.Central to TOGAF is the (ADM). The architecture capability operates the method. T

18、he method is supported by a number of guidelines and techniques. This produces content to be stored in the repository, which is classified according to the Enterprise Continuum. The repository is initially populated with the TOGAF Reference Models.ADMADM describes how deriving an organization-specif

19、ic enterprise architecture to address the business requirements. The ADM is the major component of TOGAF and provides guidance for architects on anumber of levels: It provides a number of (Business Architecture, InformationSystems Architectures, Technology Architecture) in a cycle, as an overall pro

20、cess template for architecture development activity. It provides a , describing the phase in terms of objectives,approach, inputs, steps, and outputs. The inputs and outputs sections provide a definition of the architecture content structure and deliverables (a detailed description of the phase inpu

21、ts and phase outputs is given in the Architecture Content Framework). It provides ADM Guidelines and TechniquesADM Guidelines and Techniques provide a number of guidelines and techniques to support the application of the ADM. The guidelines address adapting the ADM to deal with a number of usage sce

22、narios, including different process styles (e.g., the use of iteration) and also specific specialty architectures (such as security). The techniques support specific tasks within the ADM (such as defining principles, business scenarios, gap analysis, migration planning, risk management, etc.).Archit

23、ecture Content FrameworkThe Architecture Content Framework provides a detailed model of architectural work products, includingdeliverables, artifacts within deliverables, and the Architecture Building Blocks (ABBs) that deliverables represent.Enterprise ContinuumThe Enterprise Continuum provides a m

24、odel for structuring a virtual repository and provides methods for classifying architecture and solution artifacts, showing how the different types of artifacts evolve, and how they can be leveraged and re-used. This is based on architectures and solutions (models, patterns, architecture description

25、s, etc.) that exist within the enterprise and in the industry at large, and which the enterprise has collected for use in the development of its architectures.TOGAF Reference ModelsTOGAF provides two reference models for possible inclusion in an enterprises own Enterprise Continuum. TOGAF Foundation

26、 Architecture Technical reference Model: The TOGAF Technical reference Model is architecture of generic services and functions that provides a foundation on which specific architectures and Architecture Building Blocks (ABBs) can be built.Integrated Information Infrastructure reference Model (III-rM

27、): The Integrated Information Infrastructure reference Model (III-rM) is based on the TOGAF Foundation Architecture, and is specifically aimed at helping the design of architectures that enable and support the vision of Boundaryless Information Flow. Architecture Capability FrameworkThe Architecture

28、 Capability Framework is a set of resources, guidelines, templates, background information, etc. provided to help the architect establish an architecture practice within an organization.10) What are the different types of architecture that TOGAF deals with?TOGAF 9 covers the development of four arch

29、itecture domains. These are commonly accepted as subsets of an overall enterprise architecture, all of which TOGAF is designed to support. They are as follows: : The business strategy, governance, organization, and key businessprocesses The structure of an organizations logical and physical data ass

30、ets and datamanagement resources (Unknown) : A blueprint for the individual application systems to be deployed, theirinteractions, and their relationships to the core business processes of the organization deployment of business, data, and application services. This includes IT infrastructure, middl

31、eware, networks, communications, processing, and standards2. Core Concepts1) What are the Phases of the ADM?The Architecture Development Method (ADM) forms the core of TOGAF and is a method for deriving organization-specific enterprise architecture. The ADM includes establishing an architecture fram

32、ework, developing architecture content, transitioning, and governing the realization of architectures. All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled mann

33、er in response to business goals andopportunities. The Preliminary Phase: the preparation and initiation activities Phase A- Architecture Vision: creating the Architecture Vision and obtaining approvals Phase B- Business Architecture: describing the development of business architecture to support an

34、agreed Architecture Vision Phase C- Information Systems Architectures: describing the development of Data and ApplicationArchitectures Phase D- Technology Architecture: supporting the development of data and applicationarchitectures Phase E- Opportunities and Solutions: conducting initial implementa

35、tion planning and theidentification of delivery vehicles for the architecture defined in the previous phases Phase F- Migration Planning: addressing the formulation of a set of detailed sequence of TransitionArchitectures with a supporting Implementation and Migration Plan Phase G- Implementation Go

36、vernance: providing an architectural oversight of the implementation Phase H- Architecture Change Management: establishing procedures for managing change to thenew architecture Requirements Management: examining the process of managing architecture requirementsthroughout the ADM2) Deliverables, Arti

37、facts, and Building BlocksDuring application of the ADM process, a number of outputs are produced. In order to collate and present these major work products in a consistent and structured manner, TOGAF defines a structural model the TOGAF Architecture Content Framework in which to place them.There 3

38、 categories to describe the type of architectural work product: A deliverable: A work product that is contractually specified and in turn formally reviewed, agreed,and signed off by the stakeholders An artifact: A more granular architectural work product that describes architecture from a specificvi

39、ewpoint A building block: a (potentially re-usable) component of business, IT, or architectural capabilitythat can be combined with other building blocks to deliver architectures and solutions3) The Enterprise ContinuumTOGAF includes the concept of the Enterprise Continuum, which sets the broader co

40、ntext for an architect and explains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organization. The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts a

41、s they evolve from Generic Foundation Architectures to Organization-Specific Architectures.The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum.4) The Architecture RepositorySupporting the Enterprise Continuum is the concept of an Arch

42、itecture Repository which can be used to store different classes of architectural output at different levels of abstraction, created by the ADM. In this way, TOGAF facilitates understanding and co-operation between stakeholders and practitioners at different levels.The major components within an Arc

43、hitecture Repository are as follows: The Architecture Metamodel describes the organizationally tailored application of an architectureframework, including a meta-model for architecture content. The Architecture Capability defines the parameters, structures, and processes that supportgovernance of th

44、e Architecture Repository. The Architecture Landscape shows an architectural view of the building blocks that are in usewithin the organization today (e.g., a list of the live applications). The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives.

45、 The Standards Information Base (SIB) captures the standards with which new architectures mustcomply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization. The Reference Library provides guidelines, templates

46、, patterns, and other forms of referencematerial that can be leveraged in order to accelerate the creation of new architectures for the enterprise. The Governance Logprovides a record of governance activity across the enterprise. 5) Architecture Capability FrameworkArchitecture Capability Framework

47、that is a set of reference materials and guidelines for establishing anarchitecture function or capability within an organization. Establishing an Architecture Capability: Guidelines for establishing an Architecture Capabilitywithin an organization Architecture Board: Guidelines for establishing and

48、 operating an enterprise Architecture Board Architecture Compliance: Guidelines for ensuring project compliance to architecture Architecture Contracts: Guidelines for defining and using Architecture Contracts Architecture Governance: Framework and guidelines for Architecture Governance Architecture Maturity Models: Techniques for evaluating and quantifying an organizationsmaturity in enterprise architecture Architecture Skills Framework: A set of role, skill, and experience norms for