Goals: Preliminary
Define and scope the enterprise
You need to know which parts of an organization will be
affected in the architecture to be developed, and how
much they will be affected.
A
Define the Architecture Principles
Define the architecture principles, which are the general rules
and guidelines that govern the conduction of architecture
H B
work.
F D
2
Impact of the Stakeholders on EA
3
Scope the Enterprise
Basically there are four levels of impact.
Core - units those who are most affected and achieve most value
from the work.
Soft - Those who will see change to their
capability and work with core units but are
otherwise not directly affected.
Extended - Those units outside the
scoped enterprise who will be affected
in their own enterprise architecture.
Level of impact:
Core
Soft
Extended
Community
Stakeholders concern may be impacted by the project
A company is going to establish an enterprise architecture for anticipating requirement changes and business transformation.
We need to understand which company units are going to be impacted.
Besides, we have to indicate the level of impact.
4
Identify Participants in Architecture Development
Besides identifying the impacted units, you also need to identify the participants who will take part in architecture development.
Ideally identify the stakeholders at the initial stages
It will cost hugely if you missed out any key stakeholders during that period
Service Management
5
RACI Chart
Task 1 Task 2 Task 3
Once these units are identified, identify
the key tasks throughout the
development of architecture. R R R
Group CIO
And state the responsibilities of the units
with respect to the tasks. Usually we
describe all these by mean of a RACI chart. R
Legal Advisor
AC
There are four main responsibilities: Chief Architect
Responsible - Denoted by the letter R, responsible
means the person who will complete the task. And is
responsible for the actions and implementation. R
Architecture
Board
Accountable - Denoted by A, accountable means the
person hold the power to authorize actions or
implementation. Evidently answerable for the correct A
and detailed completion of the deliverable task. Architects
6
Enterprise Maturity Assessment
Before embarking the development of architecture, perform a We can make use of the chart to represent the level of
maturity assessment to analyze your organizations maturity in different stages.
competency in particular area in turn assist you identify Obviously the red ring indicate the current maturity
opportunities for improvement. The green ring indicate the level of maturity we want to
achieve in medium term
We can use a popular maturity assessment tool for the analysis.
The blue ring indicate the long term goal.
Say, we have defined 8 assessment factors. Each factor define a
particular area of organizations competency.
Goals
IT Strategy
Documentation Methods
8
Architecture Principles
Principles are general rules and guidelines, intended to be enduring and seldom amended, which inform and support the
way in which an organization sets about fulfilling its mission. Generally speaking, there are four categories of principles:
Business Principles
Data Principles
Application Principles
Technology Principles
10
Five Criteria for a Good Set of Principles
Improve Competitiveness
ROBUST
Definitive and precise to support
consistent decision-making in
UNDERSTANDABLE complex, potentially
Clear and unambiguous, so that controversial situations.
violations, whether intentional
or not, are minimized.
COMPLETE
Cover every situation perceived.
STABLE
Principles should be enduring,
CONSISTENT
yet able to accommodate Carefully chosen to allow
changes. consistent yet flexible
interpretation.
11
Principle Template
Enterprise policy is to abide by laws, policies, and regulations. This will not preclude
Rationale
business process improvements that lead to changes in policies and regulations.
The enterprise must be mindful to comply with laws, regulations, and external
Implications
policies regarding the collection, retention, and management of data.
Education and access to the rules. Efficiency, need, and common sense are not
the only drivers. Changes in the law and changes in regulations may drive changes
in our processes or applications.
Mandatory Mandatory
13
Context for Architecture Work
Business
Principles
Business Business
Goals Drivers
Business principles, business goals, and business drivers provide context for architecture work
Business principles, business goals, and business drivers provide context for architecture work, by describing the needs and ways of
working employed by the enterprise.
14
Context for Architecture Work
In the previous activity
youve identified the business
principles already. So now, we will
focus on identifying the business
goals and drivers. !
Primacy of Principles
!
Maximize Benefit
to the Enterprise
!
Information Management
Business Business
Goals Drivers
15
Define Business Goals
Reference ID Title Business Goal
R-01 ArchiSurance Unify the three existing platforms into a one-stop-shop service oriented
insurance platform
16
Develop Architecture Repository
17
Concept of Deliverable
Deliverables
Throughout the ADM cycle you will
keep producing some documents in
each phase. These documents are
Preliminary known as deliverables.
A
H B
18
Concept of Deliverable
Deliverables
Deliverables had developed in on
phase as output, will automatic serve
as inputs for the subsequently
Preliminary development phases
A
H B
19
Architecture Repository
Deliverables along with the artifacts have to
Architecture Metamodel be managed in a way that allows future
Architecture Method Content Metamodel
retrieval with ease. And Architecture
Repository is to serve this purpose.
21
Deliverable contains Artifacts
Each deliverable is formed by several kinds of content, known as artifacts.
Catalogs
Architecture Matrics
Principles
Diagrams
22
Start Architecture Development
Request for
Architecture Work
23
a r y P h a s e
f Prelim i n
Re s u l t o
24
Results
Production of Deliverables:
Both the sponsoring organization and
architecture development team are
Print involved and committed to
architecture development.
Organization Model Architecture
for Enterprise Architecture Principles
25