Summary TOGAF Version 9.1

ISBN-10 9087536798 ISBN-13 9789087536794
361 Flashcards & Notes
9 Students
  • This summary

  • +380.000 other summaries

  • A unique study tool

  • A rehearsal system for this summary

  • Studycoaching with videos

Remember faster, study better. Scientifically proven.

This is the summary of the book "TOGAF Version 9.1". The author(s) of the book is/are prepared The Open Group Architecture Forum, Dave Hornford (chair). The ISBN of the book is 9789087536794 or 9087536798. This summary is written by students who study efficient with the Study Tool of Study Smart With Chris.

PREMIUM summaries are quality controlled, selected summaries prepared for you to help you achieve your study goals faster!

Summary - 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:
    1. A formal description of a system, or a detailed plan of the system at component level to guide its implementation
    2. 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?
    1. Architecture continuum
    2. Solutions continuum
Read the full summary
This summary. +380.000 other summaries. A unique study tool. A rehearsal system for this summary. Studycoaching with videos.

Latest added flashcards

Why is defining of the principals of architecture important?
definition of Architecture Principles is fundamental to the development of an Enterprise.

Architecture work is informed by business principles as well as Architecture principes. The Architecture Principles themselves are also normally based in part on business principles.

Defining business principles normally lies outside the scope of the architecture function.
What are benefits of an Architecture View Creation Process ?
  • less work for the architects (because the architecture viewpoints have already been defined and therefore the views can be created faster) 
  • Better apprehensibility for stakeholders (because the architecture viewpoints are already familiar) 
  • Greater confidence in the validity of the views (because their architecture viewpoints have a known track record) 
Where does the risk mitigation refer to?
Risk mitigation refers to the identification, planning, and conduct of actions that will reduce Ihe risk to an acceptable level
What is after risk classification the next step in risk management?
The next step is to classify risks with respect to effect and frequency in accordance with scales used within the organizatioa Combine effect and frequency to come up with a preliminary risk assessment
Of which activities consists th process for risk management?
  • Risk classification 
  • Risk identification 
  • Initial risk assessment 
  • Risk mitigation and residual risk assessment 
  • Risk monitoring 
Explain the two level of risk which should be considered?
  • Initial Level of Risk: risk categorization prior to determining and implementing mitigating actions 
  • Residua] level of Risk: risk categorization after implementation of mitigating actions (if any) 
What is important about risks before starting a transformation effort?
To identify, classify/ and mitigate the risks before starting so that they can be tracked throughout the transformation effort.
The Canadian Government Business Transformation Enablement Program (BTEP) provides guidance on how to identity the business transformation-related issues. What does the BTEP recommend?
That all projects conduct a transformation readiness assessment to at least uncover the business transformation issues.

This assessment is based upon the determination and analysis/rating of a series erf readiness factors.

The outcome is a deeper understanding of the challenges and opportunities that could be presented in the course of the endeavor.

Many of the challenges translate directly into risks that have to be addressed, monitored, and, if possible, mitigated.
What are the activities in an assessment of an organization's readiness to address business transformation?
  • Determine the readiness factors that will impact the organization 
  • Present the readiness factors using maturity models 
  • Assess the readiness factors, including determination of readiness factor ratings 
  • Assess the risks for each readiness factor and identify improvement actions to mitigate the risk 
  • Work these actions into Phase E and F Implementation and Migration Plan 
What is the key for succes for a successful architecture transformation in Phases E and F?
Understanding the readiness of the organization to accept change, identifying the issues, and then dealing with them in the Implementation and Migration Plans is key to suoosssful architecture transformation in Phases E and F.

This will be a joint effort between corporate (especially human resources) staff, lines of business, and IT planners.