[ TOGAF 9 FOUNDATION SUMMERY NOTES ]TOGAF 9 Foundation summery notes by Mohammed Omar

2013

Mohammad Omar

Tech-TOGAF-------------------We are using enterprise architecture to build strong partnership between the organization technical and business group and deliver more cost effective IT systems that enable business agility

Organizations that can manage change effectively are generally more successful than those that cannot. Many organizations know that they need to improve their IT-related development processes in order to successfully manage change

Independent groups decide alone resulting in inconsistency, information islands, isolated business processes, and inefficient technologies. This mixture is a recipe for poor performance.To get consistent behavior, the enterprise must create a framework of guiding principles to define what is most important to the enterprise. Guiding principles define the enterprise‘s strategy for certain business and technical functions. They balance department and agency mandates on the one hand and enterprise -wide interests on the other. They filter decision making, eliminating solutions that don‘t meet the enterprise.‘s objectives. This clarity of executive intent takes the guesswork out of lower-level decisions. Clear, well-understood and sanctioned principles, combined with an executive commitment to enforce them, help drive change across disparate departments and programs.

SMART________

• Specific, by defining what needs to be done • Measurable, through clear metrics for success • Actionable, by clearly segmenting the problem and providing the basis for a solution • Realistic, in that the problem can be solved within the bounds of physical reality, time, and cost constraints • Time-bound, in that there is a clear statement of when the opportunity expires

TOGAF  Enterprise_________As any collection of organizations that has a common set of goalsAn extended enterprise nowadays frequently includes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units. 

Architecture__________[ISO definition]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[togaf]In TOGAF, “architecture” has two meanings depending upon the context: 1. A formal description of a system, or a detailed plan of the system at a component level to guide its implementation 2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time 

Enterprise Architecture____________________1. The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm's operating model. 2. A conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives

TOGAF Architecture domain________________________1-Business Architecture The business strategy, governance, organization, and key business processes. 2-Data Architecture The structure of an organization's logical and physical data assets and data management resources.3-Application Architecture A blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.4-Technology Architecture The software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, and standards. 

Organization  mission --------> need key enabler capabilities to fulfill mission 

Definition of “Capability” __________________An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve. For example, marketing, customer contact, or outbound telemarketing. 

Organization key enabler capabilities or components of transformation _______________________________________________________The people ,process,technology and physical infrastructure dimensions are the key enablers capabilities that organization uses to fulfill its missionThe dimension of change describe many features that work together to enable the organizational capabilities 1-people - organization structure and human capital management 2-process business activities performed by organization  3-technology data and applications and technical infrastructure 4-physical infrastructure places and envirmental factor where the enterprise workforce perform work

Each transformation program must work towards those capabilities development process 

Information asset life cycle______________________1-5 project delivery PMP

1-envision2-define3-design

4-develope5-deploy

6-10 operation management 

6-operate7-measure8-manage9-optimizeRebate 7,8,910 dispose

Framework vs. methodologyMethodology tills what to do but not how to do PMPFramework tills how to do ITIL

Capability maturity models have gained wide scale acceptance over the last decade. These models and their associated methods were originally applied to IT solutions, particularly software solutions, but a number of IT-related disciplines have developed capability maturity models to support process improvement in areas such as:

1-People - the P-CMM (People Capability Maturity Model), and the IDEAL Life Cycle Model for Improvement2-Systems Engineering - the SE-CMM (Systems Engineering Capability Maturity Model)3-Software Acquisition - the SA-CMM (Software Acquisition Capability Maturity Model)4-CMMI (Capability Maturity Model Integration)The models have been adopted by large organizations, including the US Department of Commerce, the US DoD, the UK Government, and a number of large services organizations, to assess competencies.

An enterprise architecture capability_____________________________ (or architecture capability) in the context of TOGAF, is the ability for an organization to effectively undertake the activities of an enterprise architecture practice.

The increasing interest in applying these techniques to the IT architecture and enterprise architecture fields has resulted in a series of template tools which assess:

___________________________The components of TOGAF 9 are as follows:  7 parts• introduction• Architecture Development Method (ADM) • ADM Guidelines and Techniques • The Architecture Content Framework • The Enterprise Continuum and Tools • TOGAF Reference Models • The Architecture Capability Framework

Part I: Introduction This part provides a high-level introduction to the key concepts of enterprise architecture and, in particular, to the TOGAF approach. It contains the definitions of terms used throughout TOGAF and release notes detailing the changes between this version and the previous version of TOGAF

Part II: Architecture Development Method (ADM) 

Part III: ADM Guidelines and Techniques 

Part IV: Architecture Content Framework This part describes the TOGAF content framework, including a

structured metamodel for architectural artifacts, the use of re-usable Architecture Building Blocks (ABBs), and an overview of typical architecture deliverables. 

Part V: Enterprise Continuum and Tools This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise. Part VI: TOGAF Reference Models This part provides two architectural reference models, namely the TOGAF Technical Reference Model (TRM), and the Integrated Information Infrastructure Reference Model (III-RM). 

Part VII: Architecture Capability Framework This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture practice within an enterprise.

The following summarize TOGAF components and their relation to each other1-Central to TOGAF is the Architecture Development Method  ADM (the methods)2- The architecture capability operates the method. Architecture capability framework3- The method is supported by a number of guidelines and techniques -ADM Guidelines and Techniques4-This produces content to be stored in the repository -Architecture Content Framework5-which is classified according to the Enterprise Continuum 6- The repository is initially populated with the TOGAF Reference Models 

The ADM describes a process for deriving an organization-specific enterprise architecture that addresses business requirementsIt provides a number of architecture development phasesIt provides a narrative of each architecture phaseIt provides cross-phase summaries that cover requirements management.

Enterprise continuumexplains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organizationThe 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 Architectures

Architecture Building Blocks (ABBs) typically describing the required capability in order to shape the Solution Building Blocks (SBBs) which would represent the components to be used to implement the required capability

The ADM provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, 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 manner in response to business goals and opportunities.

Pattern A pattern is “an idea that has been useful in one practical context and will probably be useful in others”.

Architecture (Syllabus Reference: Unit 3, Learning Outcome 4) Architecture has two meanings depending upon its contextual usage: 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, their inter-relationships, and the principles and guidelines governing their design and evolution over time

1- Governance Is the practice by which xyz is controlled within enterprise wide activities

Enterprise continuum is a view for Architecture repository

1-Central to TOGAF is the Architecture Development Method  ADM2- The architecture capability operates the method. Architecture capability framework3- The method is supported by a number of guidelines and techniques -ADM Guidelines and Techniques4-This produces content to be stored in the repository -Architecture Content Framework5-which is classified according to the Enterprise Continuum 6- The repository is initially populated with the TOGAF Reference Models 

Ch3______The Architecture Development Method (ADM) forms the core of TOGAF and is a method for deriving organization-specific enterprise architecture that support business requirements  The ADM provides a tested and repeatable process for developing architectures. The ADM includes 1-establishing an architecture framework,2- developing architecture content3-, 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 manner in response to business goals and opportunities. 

The ADM is described as a number of phases within a process of change illustrated by an ADM cycle graphic (see following). Phases within the ADM are as follows: each phase is described as a narrative 

Architecture Building Blocks (ABBs) typically describing the required capability in order to shape the Solution Building Blocks (SBBs) which would represent the components to be used to implement the required capability

Deliverable + artifacts + building blocks archived in architecture repository as stand red or ref model or snapshot of arch landscape in a point of time

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 Architecturesexplains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organization

Ch6

Architecture repository ___________________The Architecture Metamodel The Architecture CapabilityThe Architecture LandscapeThe Reference LibraryThe Standards Information BaseThe Reference LibraryThe governance log

describes the organizationally tailored application of an architecture framework, including a method for architecture development and a metamodel for architecture content. The Architecture Capability 

defines the parameters, structures, and processes that support governance of the Architecture Repository. The Architecture Landscape shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications). The landscape is likely to exist at multiple levels of granularity to suit different architecture objectives. The Standards Information Base captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization. The Open Group provides an example of a Standards Information Base on its web site.8 The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise.

Ch -8- ADM Guidelines and TechniquesInteroperability is a Key Enabler for eGovernment

Guidelines till how to adapt adm

Technics tills how to apply adm effectively 

TheTOGAF 9 Part III: 

• Architecture Principles • Stakeholder Management • Architecture Patterns • Business Scenarios • Gap Analysis • Migration Planning Techniques • Interoperability Requirements • Business Transformation Readiness Assessment • Risk Management • Capability-Based Planning

Architecture principles are a set of general rules and guidelines for the architecture being developed. Principles are an initial output of the Preliminary Phase and are used throughout the ADM to provide a framework for guiding decision-making within the enterprise.

They are intended to be enduring and seldom amended, and inform and support the way in which an organization sets about fulfilling its mission. Often they are one element of a structured set of ideas that collectively define and guide the organization, from values through to actions and results

Depending on the organization, principles may be established at any or all of three levels:1-Enterprise principles provide a basis for decision-making and dictate how the organization fulfills its mission. Such principles are commonly found in governmental and not-for-profit organizations,2-IT principles provide guidance on the use and deployment of all IT resources and assets across the

enterprise. They are developed to make the information environment as productive and cost-effective as possible3-Architecture principles are a subset of IT principles that relate to architecture work. They reflect consensus across the enterprise, and embody the spirit of the enterprise architecture. Architecture principles can be further divided into: 

— Principles that govern the architecture process, affecting the development, maintenance, and use of the enterprise architecture — Principles that govern the implementation of the architecture

Ch-10- views viewpoints and stakeholders --------------------------------------------------------systemA system is a collection of components organized to accomplish a specific function or set of functions. 

Stakeholders Stakeholders are people who have key roles in, or concerns about, the system; for example, users, developers, etc. Stakeholders can be individuals, teams, organizations, etc.

Concerns --------------Concerns are key interests that are crucially important to stakeholders, and determine the acceptability of the system. 

Many types of concerns one of them is cross cutting concerns which is named as quality attributes 

The terms “concern” and “requirement” are not synonymous. A concern is an area of interest. Concerns are the root of the process of decomposition into requirements. Concerns are represented in the architecture by these requirements. Requirements should be SMART

A viewpoint defines the perspective from which a view is taken. It defines how to construct and use a view, the information needed, the modeling techniques for expressing and analyzing itThe relationship between viewpoint and view is analogous to that of a template and an instance of the completed template. In constructing an enterprise architecture, an architect first selects the viewpoints (templates), then constructs a set of corresponding views (instances)

The architect uses views and viewpoints in the ADM cycle during Phases A through D for developing architectures for each domain (Business, Data, Application, and Technology).Selection of ref model and viewpoints and tools must occurs before development of base line or target arch 

ADMActual solution in phase EInteroperability logically selected and implemented in phase F Architecture realization. E,F,G 

Applying Iteration to the ADM_______________________1-architecture context iteration  pre-vision2- architecture definition iteration  B-F or B,C,D3-architecture transition iteration  E-F4-architecture governance iteration   G-H

Content framework ________________1-architecture principles ,vision, and requirement  2. 2.1-preliminary phase 2.1.1 architecture principles

2.2 architecture vision 

5 business architecture ------------------------5.1 motivation5.1.1 drivers5.1.2 goals5.1.3 objectives 5.1.4 measures   

5.2 organization5.2.1 organization5.2.2 location5.2.3 actor ,role

5.3 function5.3.1 business services ,contracts,service qualities 5.3.2 process, events,controls ,products

5.3.3