0% found this document useful (0 votes)
15 views5 pages

Business Architecture Perspective - Model - Techniques

This document provides an overview of business architecture approaches, techniques, and methodologies, referencing BABOK v3 and other sources. It outlines various models relevant to different domains, such as the Business Motivation Model and ITIL, as well as techniques like Archimate and Value Mapping. The document serves as a guide for understanding enterprise architecture frameworks and their applications in various industries.

Uploaded by

basantkumar83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views5 pages

Business Architecture Perspective - Model - Techniques

This document provides an overview of business architecture approaches, techniques, and methodologies, referencing BABOK v3 and other sources. It outlines various models relevant to different domains, such as the Business Motivation Model and ITIL, as well as techniques like Archimate and Value Mapping. The document serves as a guide for understanding enterprise architecture frameworks and their applications in various industries.

Uploaded by

basantkumar83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

BUSINESS ARCHITECTURE

PERSPECTIVE

This document is created to provide a quick overview of approaches, techniques and methodologies
(as applicable).

The information is gathered from BABOK v3 and other reference websites.

Version 1.0
BUSINESS ARCHITECURE REFERENCE MODEL

MODEL DESCRIPTION
Association for Domain: Insurance and Financial industries.
Cooperative The enterprise architecture framework consists of business
Operations Research processes, product models, development frameworks, information
and models, data models, and capability models which help
Development (ACORD) organizations to run, develop, modify, and maintain various
insurance industry applications.
Business Motivation Domain: Generic
Model BMM captures business requirements across different dimensions
(BMM) to rigorously capture and justify why the business wants to do
something, what it is aiming to achieve, how it plans to get there,
and how it assesses the result.

• Ends: What (as opposed to how) the business wants to


accomplish
• Means: How the business intends to accomplish its ends
• Directives:
The rules and policies that constrain or govern the
available means
• Influencers: Can cause changes that affect the
organization in its employment of its means or achievement
of its ends. Influencers are neutral by definition.
• Assessment: A judgment of an Influencer that affects the
organization's ability to achieve its ends or use its means.

Control Objectives for IT Domain: IT governance and management. It was designed to be


(COBIT) IT governance a supportive tool for managers—and allows bridging the crucial
and management gap between technical issues, business risks, and control
requirements
eTOM and Domain: Communications sector. eTOM is a critical component
FRAMEWORX of Open Digital Framework.
Federal Enterprise Domain: Government (developed for the U.S. Federal
Architecture Government)
Service Reference
Model (FEA
SRM) It provides a common approach for the integration of strategic,
business and technology management as part of organization
design and performance improvement.
Information Technology Domain: IT services
Infrastructure Library It is a library of volumes describing a framework of best practices
(ITIL®) for delivering IT services.
Process Classification Domain: Multiple sectors
Framework Sectors including aerospace, defence, automotive, education,
(PCF) electric utilities, petroleum, pharmaceutical, and
telecommunications
Supply Chain Domain: Supply Chain Management Supply-chain operations
Operations reference model is a process reference model developed and
Reference (SCOR) endorsed by the Supply Chain Council as the cross-industry,
standard diagnostic tool for supply chain management.
Value Reference Model Domain: Value change and network management.
(VRM) The Value Reference Model is a business process classification
scheme developed by Value Chain Group. Under VRM business
processes are arranged into three Level 1 areas – Govern, Plan
and Execute.

TECHNIQUES

TECHNIQUES DESCRIPTION
Archimate An open standard modelling language.
ArchiMate is an open and independent enterprise architecture
modelling language to support the description, analysis and
visualization of architecture within and across business domains in
an unambiguous way
Business A formalization of the business motivation in terms of mission,
Motivation Model vision, strategies, tactics, goals, objectives, policies, rules, and
(BMM) influencers.
Business Process The modelling of the processes, including interface points,
Architecture as a means of providing a holistic view of the processes
that exist within an organization.
A Business Process Architecture is the overview of a set of
business processes that reveals their inter-relations, which may be
extended with guidelines to determine the various relations
between business processes.
Capability Map Capability Map is a map or hierarchical catalogue of the enterprise
that visualizes its capabilities in a particular state, for example
current capabilities and their current maturity level, or
required capabilities in a future state. Capabilities are categorized
according to strategic, core, and supporting.
Customer Journey A model that depicts the journey of a customer through various
Map (Journey Mapping) touch points and the various stakeholders within the service or
organization. Customer journey maps are frequently used to
analyze or design the user experience from multiple perspectives.
Enterprise Core Models the integration and standardizations of the organization.
Diagram The Core Diagram is the blueprint that answers the
question: “What does an enterprise architecture look like?”
Information Map A catalogue of the important business concepts (fundamental
business entities) associated with the business capabilities and
value delivery. This is typically developed in conjunction with the
capability model and represents the common business vocabulary
for the enterprise. It is not a data model but rather a taxonomy of
the business.
Organizational A model that shows the relationship of business units to each
Map other, to external partners, and to capabilities and information.
Unlike a typical organizational chart, the map is focused on the
interaction between units, not the structural hierarchy.
Project Portfolio Used to model programs, projects, and portfolios to provide a
Analysis holistic view of the initiatives of the organization.
Project Portfolio refers to a set of project proposals,
projects, programs, sub-portfolios and operations managed
together to achieve an organisation's strategic objectives.
Roadmap It is a strategic blueprint that communicates how a company’s
plans will help the organization achieve its business objectives.
The technique models the actions, dependencies, and
responsibilities required for the organization to move from current
state, through the transition states, to the future state.
Service-Oriented It is the first stage of SOA initiative. It is used to model analysis,
Analysis design, and architecture of systems and software to provide a
holistic view of the IT infrastructure of the organization. It is
commonly carried out iteratively, once for each business process.
The Open Group Provides a method for developing enterprise architecture.
Architecture Phase B of the TOGAF Architecture Development Method (ADM)
Framework is focused on the development of business architecture.
(TOGAF®) Organizations following TOGAF may choose to tailor Phase B to
adopt the business architecture blueprints, techniques, and
references described in the BABOK® Guide.
Value Mapping Value mapping provides a holistic representation of the stream of
activities required to deliver value. It is used to identify areas of
potential improvement in an end–to–end process. Although there
are several different types of value mapping, a value stream is
often used in business architecture.
Zachman Provides an ontology of enterprise primitive concepts based on a
Framework matrix of six interrogatives (what, how, where, who, when, why)
and six levels of abstraction (executive, business management,
architect, engineer, technician, enterprise). Business architects
may find that exploring the executive or business management
perspectives across the different interrogatives provides clarity and
insight.

You might also like