Suggest to practice EA in a three tier approach rather than a big bang. Point out EA is a planning effort rather than an engineering effort. EA is not the enterprise wide solution architecture. Clarify the confusion of business capability and business process. EA is not business process centric it is the mean to support the end of business capability. Introduce the concept of business floor plan and EA landscape. The business floor plan is similar to the floor plan of a house. EA landscape to present the situation of usage such as the landscape of application, data and technology. Practical EA use the popular EA method such as FEAF, TOGAF, DODAF to design the segment architecture .

1. Practice EA in three tiers
by
John Chi-Zong Wu
peaitce@yahoo.com
www.liteea.com
Date 1/30/2015

2. Presentation goals
 This presentation suggest to practice EA in a three tier approach with a road
map.
 Identify the principles of Notional EA.
 Introduce the concept of landscape and business floor plan.
 Practical EA in segment architecture to close the business performance gaps
due to constant change.
 Enterprise Architect to deliver the EA value proactively.

3. Three Tier EA overview
 The Notional EA is for all stakeholders, it covers the entire organization with low
detail and have impact on strategic outcome .
 The practical EA in segment architecture in the scope of line of business. It have
medium detail and have impact on business outcome. It is for the business
 Daily EA is the EA service delivery. It is where the rubber meet the road in high
detail with impact of operational outcome .

4. The EA road map
Notional Business Architecture
Notional Application Architecture
Notional Data Architecture
Notional Technology Architecture
Business
Performance
Gap Analysis
Strategic
Planning
Capital
Investment
Conceptual
Solution Architecture
Risk
Management
Notional EA Practical EA in segment
architecture
Daily EA
EA Service Delivery
Application Security
Managers
Project
Managers
Strategic
Planners
Decision
Makers
Scope of Segment
Architecture
Modernization
Plan
Notional Activity Model
SOA &
Cloud
Governance
Compliance Network
Collaborative
Culture
Procurement
Managers

5. Prepare Enterprise Map and Notional EA in parallel
Notional EA is a planning effort rather than an engineering effort.
Enterprise architect prepare the Notional EA as the high level
enterprise overview.
Enterprise Map is a one page concept to extract information from the
Notional EA on a poster size paper.
The collaborative effort in Enterprise Map serve the function to collect
the hidden institutional knowledge.
The architect update the notional EA accordingly.

6. Tier 1 :Notional EA
The initial EA should be simple and comprehensive.
It is a high level and notional instead of a big bang
enterprise wide architecture blueprint.
The purpose of Notional Architecture:
Notional architecture provide an overall Enterprise Architecture
concept to see the whole.
Notional Architecture prepare in architecture drawing form for
every one to comprehend.
Notional Architecture serve as the long term enterprise
architecture guide line similar to a city plan

7. The principle of Notional EA
Notional EA emphasize the “Enterprise” to look at the
whole picture. It is about the enterprise landscape of
application, data and technology to illustrate how business
take advantage of technology.
EA is a planning effort rather than engineering effort. It is
the planning effort to align enterprise resources to with
business need,
EA is not business process centric, it is based on business
capability from the perception of stakeholder rather base
on business processes from the perception of developers.
Business processes the “means” to reach the end of
business capability.
There are many means to reach the same end, business
process modeling frequently become “paralysis by
analysis”. The tail is waging the dog.

8. the iceberg
Notional is defined as abstract,
theoretical, or speculative, as
reflective thought in the
dictional.com
Notional EA serve as the visible part
of the enterprise iceberg to enable
communicate with all level of
stakeholders.

9. The Notional Architecture in architecture drawings
The Notional Architecture is
prepared in architecture drawings
for general comprehension.
Enterprise Architects prepare the
notional architecture as the other
architects do.
Notional Architecture consist of :
The Business Architecture.
The Process Architecture.
The Application Architecture.
The Information Architecture.
The Technology Architecture.

10. The Service Catalog
Service Catalog is analogy to the
restaurant menu.
A service catalog is a means of
centralizing all services that are
important to the stakeholders of the
enterprises which implement and use
it.
For example: An IT service catalog is a
subset of an enterprise service catalog
and is defined by the
Information Technology Infrastructure Library
Service Design to be an exhaustive list
of IT-only services that an organization
provides or offers to its employees or
customers.

11. The Composition of Service Catalog
 Form Wikipidia : The Service Catalog composition
 Service catalogs are implemented in a manner that facilitate the registration, discovery, request, execution, and tracking of desired services for
catalog users. Each service within the catalog typically includes traits and elements such as:
 Clear ownership of and accountability for the service (a person and often an organization)
 A name or identification label for the service
 A description of the service
 A service categorization or type that allows it to be grouped with other similar services
 Related service request types
 Any supporting or underpinning services
 Service level agreement (SLA) data and information that helps service providers set expectations for their service requestors
 Who is entitled to request/view the service
 Associated costs (if any)
 How to request the service and how its delivery is fulfilled
 Escalation points and key contacts

12. Align business segments to service catalog
 Notional EA support
stakeholder need by
aligning business
segments to services
catalog.
 The service/segment
matrix aligns
business segment to
service catalog.
Service 1 Service 2 Service 3 Service 4
Segment 1 x x x x
Segment 2 x x
Segment 3 x x x
Segment 4 x x
Segment 5
Segment 6 x x
Segment 7 x x

13. Support service catalog with business segments
 EA community have defined Business
segments based on the line of Business
(LOB) in the US segment architecture
method.
 Line of business (LOB) is a general
term which often refers to a set of one or
more highly related products which
service a particular customer transaction
or business need
 The figure on the right model the
business segment in the US government.

14. The Business Segment in Office of CIO
 The OCIO office consist of the following business segments.
 Performance.
 Enterprise Architecture
 Capital Investment
 Engineering
 Service management
 IT management.
 Security Management
 Governance & Compliance
 Strategic Planning
 Project Management
 Risk Management
 Collaboration
 Customer management
 Procurement
 Portfolio management

15. The Business Floor Plan
Performance
Strategic
Planning
Risk
Management Customer
Management
Governance
Compliance
Capital
Investment
Project ManagementProcurement
Enterprise
Architecture
Service Management
Portfolio
Management
Security
Management
Collaboration
IT Management
Engineering
Analogy to a
house floor
plan, the
Enterprise
floor plan is
used in
general to
describe any
drawing
showing the
physical
layout of
business
segments in a
organization.
Floor plan
arrangement
varies for
different
OCIO.

16. Analogy to a house floor plan
The floor plan is one of the most
important features of a house, and is
easily one of the most significant
decisions you will make regarding your
home.
A good floor plan can enhance your life,
maximize space, light, and airflow, and
create a natural flow between rooms.
Business floor plan is one of the most
important feature of an organization.
The business floor plan can enhance an
organization and create a natural flow
between business segments.
Business floor varies from one OCIO to
the other with same business segment
but different arrangement .

17. Compose Business Capability Map on floor plan
Enterprise
Architecture
Performance Risk Management Collaboration Customer
Management
Strategic Planning Portfolio CPIC
Procurement Project Management
Governance
Service ManagementEngineeringSecurity Management
IT Management
System
Administration
IT Asset
Management
Facility
Management
Service
Catalog
Service
delivery
Service
Level
Agreement
Performance
Monitoring
Vendor
Management
Business
Architecture
Application
Architecture
Data
Architecture
Technology
Architecture
Solution
Engineering
Network
Engineering
Capital
Monitoring
 Describe
the business
via business
capability
instead of
business
processes.
 Design the
business
capability
map on the
business
floor plan.
 Design the
business
capabilities
from the
aspect of
customers
not the
engineers.
ContractingAcquisition
Mitigation
ROI
Business
Cases
Performance
Measure
Performance
Gap Analysis
Vision
Continuous
Operation
Cloud
Computing
Network
Administration
Governance
Compliance
Commination
Social Networking
Marketing
Customer
Services
Decision
Support
Resource
Management
Risk
Impact
Analysis
Risk
Mitigation
Project
Execution
Investment
Control

18. Notional Architecture in the concept of landscape
The Notional Architecture adapt the word of
“landscape” to describe the situation of usage.
It is a indication of over usage, under usage and proper
usage.
Application landscape is defined as the situation of
application usage by business.
Information landscape is defined as the situation of
information usage by business.
Technology landscape is defined as the situation of
technology usage by business.

19. Business Processes support business capability
Business processes are not part of business
architecture.
Business processes are the means to support the
business capability.
It is the solution layers to support to support the
business similar to application, data and technology.

20. Notional Business Process Architecture
Notional Business process
architecture align business
process to support the business
capability.
Enterprise Architect design
the enterprise wide notional
business process architecture
in the layers of
Concept of operation.
Business Activity modeling.
Business process modeling

21. The Enterprise Application Landscape
 The enterprise
application
landscape
describe the
status of usage
application
usage by
business.
 The bubble
represent the
application
systems
 The
application
landscape is
indication of
redundant
usage or
under use of
automation
Enterprise
Architecture
Performance Risk Management Collaboration Customer
Management
Strategic Planning Portfolio CPIC
Procurement Project Management
Governance
Service ManagementEngineeringSecurity Management
IT Management
System
Administration
IT Asset
Management
Facility
Management
Service
Catalog
Service
delivery
Service
Level
Agreement
Performance
Monitoring
Vendor
Management
Business
Architecture
Application
Architecture
Data
Architecture
Technology
Architecture
Solution
Engineering
Network
Engineering
Capital
Monitoring
ContractingAcquisition
Mitigation
ROI
Business
Cases
Performance
Measure
Performance
Gap Analysis
Vision
Continuous
Operation
Cloud
Computing
Network
Administration
Governance
Compliance
Commination
Social Networking
Marketing
Customer
Services
Decision
Support
Resource
Management
Risk
Impact
Analysis
Risk
Mitigation
Project
Execution
Investment
Control
EA
System
Performance
System
ITIL
System
Engineering
System
Security
Management
System
Project
Management
System
Procurement
Management
System
Risk
Management
System
Decision
Support
System
Administration
System
IT Management
System

22. The Enterprise Information Landscape
Notional information
landscape describe
the situation of
information usage by
business.
The information
landscape align to
business via note
index .
Assign index number
to the database.
Associate business
capability with the
index number in the
capability box as
shown on the right.
2
4
1
5
7
8
6
3
Budget
1,3, 5
Information LandscapeAlign information to business
capability with information
index. The following box
shows budget capability is
associate d to data base 1,3,5

23. The Enterprise Technology Landscape
 The enterprise
technology
landscape
describe the
status of
technology
usage by
business
capability.
 The color code
represent the
technology
patterns in the
next slide.
 The technology
landscape is a
indication of
technology
modernization.
Enterprise
Architecture
Performance Risk Management Collaboration Customer
Management
Strategic Planning Portfolio CPIC
Procurement Project Management
Governance
Service ManagementEngineeringSecurity Management
IT Management
System
Administration
IT Asset
Management
Facility
Management
Service
Catalog
Service
delivery
Service
Level
Agreement
Performance
Monitoring
Vendor
Management
Business
Architecture
Application
Architecture
Data
Architecture
Technology
Architecture
Solution
Engineering
Network
Engineering
Capital
Monitoring
ContractingAcquisition
Mitigation
ROI
Business
Cases
Performance
Measure
Performance
Gap Analysis
Vision
Continuous
Operation
Cloud
Computing
Network
Administration
Governance
Compliance
Commination
Social Networking
Marketing
Customer
Services
Decision
Support
Resource
Management
Risk
Impact
Analysis
Risk
Mitigation
Project
Execution
Investment
Control
EA
System
Performance
System
ITIL
System
Engineering
System
Security
Management
System
Project
Management
System
Procurement
Management
System
Risk
Management
System
Decision
Support
System
Administration
System
IT Management
System

24. The Technology patterns
Two Tier
Main Frame
N Tier
Three Tier

25. Tier two: Practical EA in segment architecture
 The EA community have initiated the segment
architecture as the practical EA after realizing that it is
not practical to EA in a big bang approach.
 Segment Architecture is an effort to elaborate the
notional architecture for the purpose of closing the
business performance gaps due to change.
 It is an on demand EA approach only for the area of need.

26. Segment Architecture to adapt change
 Segment Architecture is the practical EA.
 It is futile to EA in a big bang approach which become
obsolete before ink dry.
 It is the holistic architecture design in adapting to change.
 It is EA on demand.

27. Business Floor Plan Enables Segment Architecture
The risk of segment architecture is to create silo
segment architecture design.
The business floor plan have orderly arrange the
business segments in the OCIO and enable an
integrated segment architecture approach to evaluate
the impacts between different segments.

28. The enterprise segment heat map
 Segment Plan is part of
Notional Architecture
 Analyze segment
Performance gaps due
to change.
 Prepare the segment
Heat map use color
code to identify the
underperform
segments
Good
Fair
Warning
Hot Spot

29. The Segment Architecture approach
 Enterprise architect
conduct segment
architecture under the
guideline of notional
architecture.
 The figure on the right
(by US FEAPMO)
illustrate the segment
architecture process.

30. Apply popular EA approaches on segment
Enterprise Architects design Segment
Architecture via popular EA method such as
EAP, FEAF, TOGAF, PEAF, DoDAF.
As a matter of fact, these methods are more
practical in the scope of segment
architecture rather than in a big bang EA
approach.
A big bang approach to identify As-is, plan
the target architecture, conducting gap
analysis and planning for transition has
been an overwhelming experience for most
of EA practitioners.

31. Tier 3 : Daily EA
EA is a daily business. After deliver the enterprise blueprint, Enterprise
Architects does not go back to their ivory tower.
The purpose of daily EA is to deliver EA value every day rather than
design architecture every.
After the hard work to design the enterprise blueprint in a big bang
approach, the architect realize that the real challenge is buy-in from the
stakeholders not the design effort.
Command and control via authority and budget is not the solution.
Under this approach EA has become a burden rather than a value.
The Enterprise Architect must proactively taking the responsibility to
deliver EA value and earn buy-in from stake holders Instead of live in an
ivory tower and expect someone else to enforce the enterprise
architecture blueprint.

32. Stakeholders are too busy to comprehend EA
 EA become shelfware because EA is not only a hard work
to design but also a hard work to comprehend.
 Enterprise Architects works hard to design the enterprise
architecture and expecting stakeholder works hard to
appreciate their hard work.
 However, the stakeholders get their job to do and
comprehend the overwhelming EA is not their priority.

33. Daily EA deliver EA value evert day
 In a ITIL service management concept, Service Delivery is
as critical as architecture design.
 The problem of EA is the EA community have indulged in
architecture design and overlook the EA service delivery.
 Daily EA does not mean to architect the enterprise every
day. It is the EA service delivery.

34. EA and the organization
 EA let every one to see the
whole and enable agility in
adapting to change in the
following area.
 Strategic planning
 Capital investment.
 Solution Architecture design.
 Procurement.
 Project management.
 Application development.
 IV & V.
 Security management.
 And more.

35. EA are the “Glue” not the “Guru”
 EA community have realize the EA is a daily business
however they also like to portray Enterprise Architect as
the architecture “Guru” to provide advice and guidance
or every acting like a architecture police to enforce the
standards.
 In this approach, EA become a burden rather than a
value.
 The true value of daily EA is to deliver EA value and
earn buy-in from the stakeholders.
 The Enterprise Architects are “the Glue” not the “Guru”

36. The take away
 EA is a three tier approach rather than a big bang.
 Begin EA with Enterprise Map and Notional EA
simultaneously.
 The principle of Notional EA principle, it is very
different from a enterprise wide solution architecture.
 Use the concept of business floor plan to architect the
notional architect.
 Business floor plan enables segment architecture.
 Business processes are the mean not the end.
 The popular EA method such as FEAF, TOGAF, DODAF
is more practical in the scope of segment architecture.