+380.000 andere samenvattingen
Een unieke studietool
Een oefentool voor deze samenvatting
Studiecoaching met filmpjes
Onthoud sneller, leer beter. Wetenschappelijk bewezen.
PREMIUM samenvattingen zijn gecontroleerd op kwaliteit en speciaal geselecteerd om je leerdoelen nog sneller te kunnen bereiken!
Samenvatting - TOGAF Version 9.1
1.1 Structure of the TOGAF Document
What are the seven parts of the TOGAF document?
- PART I Introduction
- PART II Architecture Development Method (ADM)
- PART III ADM Guidelines and Techniques
- PART IV Architecture Content Framework
- PART V Enterprise Continuum & Tools
- PART VI TOGAF Reference Models
- PART VII Architecture Capability Framework
What is the intention of dividing the TOGAF specification?
- To allow for different areas of specialization to be considered in detail and potentially addressed in isolation
- To make it possible to select particular parts for adoption
1.2 Executive Overview
What is an enterprise?Any collection of organizations that has a common set of goals.
Why do I need an enterprise archictecture?The purpose of an entrprise architecture is to optimize across the enterprise the often fragmented legacy of processes into an integrated environment that is responsive to change and supportive of the delivery of business strategy.
What are the business benefits that result from a good enterprise architecture?
- A more efficient business operation
- A more efficient IT operation
- Better return on existing investment, reduced risk in future investment
- Faster, simpler and cheaper procurement
How can an architect adress the concerns of the "stakeholders" in the change?
- Identifying an refining the requirements that the stakeholders have.
- Developing views of the architecture that show how the concerns and requirements are going to be addressed
- Showing the trade-offs that are going to be made in reconcilling the pontentially conflicting concerns of different stakeholders.
What can be said about the stakeholders concerns and requirements without an enterprise architecture?That it is unlikely that all the concerns and requirements will be considered and met.
2.1 What is TOGAF?
What is TOGAF?TOGAF is an architecture framework. It provides the methods and tools for assisting in the acceptance, production, use and maintenance of an enterprise architecture.
2.2 What is Architecture in the Context of TOGAF?
What is Architecture in the Context of TOGAF?It has two meainings depending upon the context:
- A formal description of a system, or a detailed plan of the system at component level to guide its implementation
- The structure of components, inter-relationships, and the principles and guideliness governing their design and evolution over time.
2.3 What Kind of Architecture Does TOGAF Deal With?
What does the business architecture define?The business strategy, governance, organization, and key business processes.
What does the technology architecture describe?The technology architecture describes the logical software and hardware capabilitities that are required to support the deployment of business, data and application services.
What kind of architectures does TOGAF deal with?
- Business Architecture
- Data Architecture
- Application Architecture
- Technology Architecture
What does an application architecture provide?The application architecture provides a blueprint for the individual applications to be deployed, their interactions an their relationships to the core business processes of the organization.
What does the data architecture describe?The structure of an organization's logical and physical data assets and data management resources.
2.6 Enterprise continuum
What is the enterprise continuum?The enterprise continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Arhitectures.
Which two complementary concepts are comprised in the enterprise continuum?
- Architecture continuum
- Solutions continuum
Laatst toegevoegde flashcards
- Application Component
- Business Service
- Data entity
- Information System Service
- Organizational Unit
- Platform Service
- Technology Component
- To develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and the stakeholder concerns
- To identify candidate Architecture Roadmap components.
- To develop the Target Application Architecture
- To identify candidate Architecture Roadmap components
- To develop the Target Data architecture
- To identify candidate Architecture Roadmap components
- To develop the Target Information Systems (Data and Application) Architectures
- To identify candidate Archtitecture Roadmap Components
- To develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, aned respond to strategic drivers set out in the Architecture Vision, in a way that adresses the Request for Architecture Work and stakeholder concerns
- To identify candidate Architecture Roadmap components based upon gaps between Baseline and Target Business Architectures
- Finalize the Architecture Roadmap and the supporting implementation and Migration Plan
- Ensure that the Implementation and Migration Plan is coordinated with the enterprise's approach to managing and implementing change in the enterprise's overall change portfolio
- Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders
- Generate an initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture road map components from Phases B,C and D
- Determine wether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value