TOGAF

TOGAF
(The Open Group Architecture
Framework)
Samia Azam
13003114004
12/16/2014
Software Design and Archtecture
(Business Archtecture TOGAF) 1

Business architecture
A business architecture is a part of
an enterprise architecture related to
corporate business, and the
documents and diagrams that describe the
architectural structure of that business.
12/16/2014

Business architecture
A formal definition of the first meaning is
defined by the Object Management
Group's Business Architecture Working
Group as follows:
"A blueprint of the enterprise that provides a
common understanding of the organization
and is used to align strategic objectives and
tactical demands."
12/16/2014

2-Business Architecture
2.1 Objectives
The objectives of Phase B: Business
Architecture are to:
• Describe the Baseline Business
Architecture
• Develop a Target Business Architecture
• Analyze the gaps between the Baseline
and Target Architectures
• Select architecture viewpoints to
demonstrate how stakeholder concerns
are addressed in the Business
Architecture
• Select tools and techniques for
12/16/2014

2.2 Inputs
The inputs to this phase are:
• Request for Architecture Work
• Business principles, business goals, and
business drivers
• Capability Assessment
• Communications Plan
• Organizational Model for Enterprise
Architecture
• Tailored Architecture Framework
• Approved Statement of Architecture Work
12/16/2014

2.2 Inputs (cont.)
• Architecture principles, including
business principles, when pre-existing
• Enterprise Continuum
• Architecture Repository
• Architecture Vision, including:
⎯ Refined key high-level stakeholder
requirements
⎯ Baseline Business Architecture (vision)
⎯ Baseline Data Architecture (vision)
⎯ Baseline Application Architecture (vision)
12/16/2014

2.2 Inputs (cont.)
⎯ Baseline Technology Architecture (vision)
⎯ Target Business Architecture (vision)
⎯ Target Data Architecture (vision)
⎯ Target Application Architecture (vision)
⎯ Target Technology Architecture (vision)
12/16/2014

2.2.2 Business Principles
12/16/2014

2.3 Steps
Phase B consists of the following steps:
1. Select reference models, viewpoints, and
tools
2. Develop Baseline Business Architecture
Description
3. Develop Target Business Architecture
Description
4. Perform Gap Analysis
5. Define roadmap components
6. Resolve impacts across the Architecture
Landscape
7. Conduct formal stakeholder review
8. Finalize the Business Architecture
9. Create the Architecture Definition Document
12/16/2014

2.3.1 Select Reference Models,
Viewpoints, and Tools
 Determine Overall Modeling Process
 Identify Required Service Granularity
Level, Boundaries, and Contracts
 Identify Required Catalogs, Matrices,
and Diagrams
 Identify Types of Requirement to be
Collected
12/16/2014

2.3.2.3 Phase B Catalogs,
Diagrams, and Matrices
12/16/2014

2.3.2 Develop Baseline Business
Architecture Description
 Describe existing business to extend that
support target architecture
 Where possible, identify the relevant
Business Architecture building blocks,
drawing on the Architecture Repository.
 Develop new architecture where
necessary.
 Developed to satisfy stakeholder
concerns.
 Use the models identified within Step 1
as a guideline for creating new
architecture content to describethe
Baseline Architecture.
12/16/2014

2.3.3 Develop Target Business
Architecture Description
 Describe target business to extend that
support target architecture vision
 identify the relevant Business
Architecture building blocks, drawing on
the Architecture Repository if possible
 Develop new architecture where
necessary.
 Developed to satisfy stakeholder
concerns.
 Use the models identified within Step 1
as a guideline for creating new
architecture content to describethe
12/16/2014

2.3.4 Perform Gap Analysis
 Verify the architecture models for internal
consistency and accuracy
 Perform trade-off analysis
 Check that the models support the
principles, objectives, and constraints
 Note changes to the viewpoint(s)
 Test architecture models
 Finally, identify gaps between the
baseline and target using the Gap
Analysis technique.
12/16/2014

2.3.5 Define Roadmap Components
 Business Roadmap is required to
prioritize activities over the coming
phases which is get from (Baseline
Architecture, a Target Architecture,
and Gap Analysis results)
 This roadmap will be used as raw
material to support a more detailed
definition of a consolidated, cross-
discipline roadmap within Phase
E:Opportunities & Solutions
12/16/2014

2.3.6 Resolve Impacts across the
Architecture Landscape
Once the Business Architecture is finalized, it is
necessary to understand any wider impacts or
implications.
 Does this Business Architecture impact any pre-
existing architectures?
• Have recent changes been made that impact the
Business Architecture?
• Are there any opportunities to re-use work from
this Business Architecture in other areas of the
organization?
• Does this Business Architecture impact other
projects (those planned, as well as those in
progress)?
• Will this Business Architecture be impacted by
other projects (those planned, as well as those in
progress)? 12/16/2014

2.3.7 Conduct Formal Stakeholder
Review
 Check the original motivation for the
architecture project and the Statement
of Architecture
 Work against the proposed Business
Architecture, asking if it is fit for the
purpose of supporting subsequent
work in the other architecture
domains.
 Refine the proposed Business
Architecture only if necessary.
12/16/2014

2.3.8 Finalize the Business
Architecture
 Standards for each of the building
blocks, re-using as much as possible
from the reference models selected from
the Architecture Repository
 Conduct a final cross-check of overall
architecture against business goals
 Document the final requirements
traceability report
 Document the final mapping of the
architecture within the Architecture
Repository
 Identify building block that might be re-
used
12/16/2014

2.3.9 Create the Architecture
Definition Document
 Document the rationale for building
block decisions in the Architecture
Definition Document
 Prepare the business sections of the
Architecture Definition Document
 Send the document for review by
relevant stakeholders, and incorporate
any feedback.
12/16/2014

2.4 Outputs
The outputs of this phase are:
• Statement of Architecture Work, updated if
necessary
• Validated business principles, business goals,
and business drivers
• Elaborated Business Architecture principles
• Draft Architecture Definition Document containing
content updates
• Draft Architecture Requirements ,including
content
Updates
• Business Architecture components of an
Architecture Roadmap
12/16/2014

2.4.1 Architecture Definition
Document
The following contents are typically found within an
Architecture Definition Document :
• Scope
• Goals, objectives, and constraints
• Architecture principles
• Baseline Architecture
• Architecture models
• Rationale and justification for architectural
approach
• Mapping to Architecture Repository, including
mappings to the Architecture Landscape, the
reference models, the standards, as well as a re-
use assessment
• Gap Analysis
• Impact assessment 12/16/2014

2.4.1.1 Business Architecture
Components
• Baseline Business Architecture, if
appropriate; this is a description of the
existing Business Architecture
• Target Business Architecture,
including:
⎯ Organization structure identifying business
locations and relating them to organizational
units
⎯ Business goals and objectives for the
enterprise and each organizational unit
⎯ Business functions identified using a detailed,
recursive step involving successive
decomposition of major functional areas into
12/16/2014

Components
⎯ Business services that the enterprise and each
enterprise unit provides to its customers, both
internally and externally
⎯ Business processes, including measures and
deliverables
⎯ Business roles, including development and
modification of skills requirements
⎯ Business data model
⎯ A correlation of organization and functions which
relate business functions to organizational units in
the form of a matrix report
 Views corresponding to the selected
viewpoints addressing key stakeholder
concerns
12/16/2014

2.4.2 Architecture Requirements
Specification
The following contents are typical within an
Architecture Requirements Specification:
• Success measures
• Architecture requirements
• Business service contracts
• Application service contracts
• Implementation guidelines
• Implementation specifications
• Implementation standards
• Interoperability requirements
• Constraints
• Assumptions
12/16/2014

Requirements
Business Architecture requirements populating the
Architecture Requirements Specification in
Phase B include
• Gap Analysis results
• Technical requirements: An initial set of technical
requirements should be generated as the output
of Phase B: Business Architecture. for example,
by a dependency/priority matrix (e.g., guiding
trade-offs between speed of transaction
processing and security); a list of the specific
models that are expected to be produced (e.g.,
expressed as primitives of the Zachman
Framework).
• Updated business requirements, identified by use
of the Business Scenarios technique
12/16/2014

2.4.3 Architecture Roadmap
The following contents are typically found within an
Architecture Roadmap:
• Project list:
⎯ Name, description, and objectives of each project
⎯ Prioritized list of projects to implement the proposed
architecture
• Time-oriented Migration Plan:
⎯ Benefits of migration determined (including mapping
to business requirements)
⎯ Estimated costs of migration options
• Implementation recommendations:
⎯ Criteria/measures of effectiveness of projects
⎯ Risks and issues
⎯ Solution Building Blocks (SBBs) – description and
model
12/16/2014

Zachman Framework
 The Zachman Framework is
an enterprise architecture
framework which provides a formal and
structured way of viewing and defining
an enterprise.
 It consists of a two dimensional
classification matrix based on the
intersection of six communication
questions (What, Where, When, Why,
Who and How) with five levels
of reification, successively transforming
the most abstract ideas (on the Scope
level) into more concrete ideas (at the
Operations level).12/16/2014

2.5 Summary
 The objective of Phase B: Business
Architecture is to document the
fundamental organization of a
business, embodied in its business
processes and people, their
relationships to each other and the
environment, and the principles
governing its design and evolution. It
should show how the
organization meets its business goals.
12/16/2014

12/16/2014
Question ?

TOGAF

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie TOGAF

Ähnlich wie TOGAF (20)

TOGAF

Hinweis der Redaktion