sia enterprise architecture
TRANSCRIPT
-
8/11/2019 SIA Enterprise Architecture
1/57
-
8/11/2019 SIA Enterprise Architecture
2/57
-
8/11/2019 SIA Enterprise Architecture
3/57
What is enterprise architecture?
A method for managing your business orenterprise:
A decision making tool
A change management tool The knowledgebase of your business or
enterprise
It is about the laws of nature that determine thesuccess of an enterprise particularly, continuingsuccess in the turbulent times of the Information Age.
John Zachman
-
8/11/2019 SIA Enterprise Architecture
4/57
Scope of Enterprise Architecture?
The scope of enterprise architecture includes theenterprises
People,
Processes,
Information,Technology,
their relationships to each other,
And the external environment
-
8/11/2019 SIA Enterprise Architecture
5/57
Who is Enterprise Architect?
Enterprise architects are the peoplewho:
create the solutions to address the business
challengesand support the enterprise in implementing
those solutions.
-
8/11/2019 SIA Enterprise Architecture
6/57
Enterprise architecture is not
focused on Information
Technology
(IT is only a part or subset of enterprisearchitecture)
-
8/11/2019 SIA Enterprise Architecture
7/57
In the Information Age
How do you manage the increasing complexityof your enterprise?
How do you manage the increasing rate ofchange?
How do you meet the demands of your
customers quicker and more efficiently?
-
8/11/2019 SIA Enterprise Architecture
8/57
In the Information Age
When someone leaves your enterprise, do youretain their knowledge?
For Example:As of 1/4 the state of Montana has 35% of its
workforce eligible for retirement
551 employees with 30+ years
An additional 3,444 employees with 2530 years
-
8/11/2019 SIA Enterprise Architecture
9/57
Thousands of years of history wouldsuggest the only known strategy foraddressing complexity and change is
architecture.
-
8/11/2019 SIA Enterprise Architecture
10/57
Architecture
If it gets so complexyou cant rememberhow it works, you haveto write it down
If you want to changehow it works, you start
with what you havewritten down
-
8/11/2019 SIA Enterprise Architecture
11/57
Why is Enterprise Architecture Needed?
System Complexity : Information systems and business processes are
complex and will become increasingly complex in the
future.
As system complexity increases, the costs to buildand maintain those systems increase and take more
of an organizations resources in time, money, and
personnel.
-
8/11/2019 SIA Enterprise Architecture
12/57
Why is Enterprise Architecture Needed?
Poor business alignment: It is becoming harder for organizations to make sure
that IT systems and spending are aligned with
business needs
IT costs are increasing while the value they bring toan organization is decreasing if the IT and business
goals are not aligned.
-
8/11/2019 SIA Enterprise Architecture
13/57
Why is Enterprise Architecture Needed?
A method for writing things down develop blueprints
The impact of moving a wall complexity and change
Plan on how to move the wall change management
Retain employee knowledge becomes knowledgebase of enterprise
If you dont have architecture, you change bytrial and error (which is high risk)
-
8/11/2019 SIA Enterprise Architecture
14/57
Why Enterprise Architecture...?
-
8/11/2019 SIA Enterprise Architecture
15/57
The Concept Of Enterprise Architecture
-
8/11/2019 SIA Enterprise Architecture
16/57
Enterprise architecture
EA gets you there with Confidence
-
8/11/2019 SIA Enterprise Architecture
17/57
Repository-Based EA
-
8/11/2019 SIA Enterprise Architecture
18/57
Standalone Documents
-
8/11/2019 SIA Enterprise Architecture
19/57
Framework of EA
-
8/11/2019 SIA Enterprise Architecture
20/57
Common Repository & Framework
-
8/11/2019 SIA Enterprise Architecture
21/57
What Happens if:
-
8/11/2019 SIA Enterprise Architecture
22/57
Architecture Framework
-
8/11/2019 SIA Enterprise Architecture
23/57
System Architect: Approach for success
-
8/11/2019 SIA Enterprise Architecture
24/57
History of Enterprise Architecture
The field now known as enterprise architecturefirst came about 20 years ago.
In 1987, J.A. Zachman wrote an article entitled
A Framework for Information Systems Architecture
Zachman originally described as informationsystems architectural framework, but it was
soon renamed enterprise-architectureframework.
-
8/11/2019 SIA Enterprise Architecture
25/57
Zachman Framework Developed in 1982 at IBM by John Zachman, first
published in 1987.
Applies physics and basic engineering principalsto the enterprise as a whole
Tool for engineering and manufacturingenterprises
Has a defined set of rules to follow for successfulimplementations
-
8/11/2019 SIA Enterprise Architecture
26/57
Zachman Framework
-
8/11/2019 SIA Enterprise Architecture
27/57
Different Perspectives (Rows)
Owner
Designer
Builder
-
8/11/2019 SIA Enterprise Architecture
28/57
Other Rows Defined
Scope (Planner) RowStakeholders Perspective Detailed Representations (Technology Used)
Bottom Row Functioning Enterprise or theSystems
Electronic Manual
-
8/11/2019 SIA Enterprise Architecture
29/57
How it works?
Rows- illustrate different descriptions of anenterprise from a certain perspective.
Source:http://www.zachmaninternational.com/2/ZachmanFramework.asp
-
8/11/2019 SIA Enterprise Architecture
30/57
Different Abstractions (Columns)
What (Data) How (Function)
Where (Network)
Who (People) When (Time)
Why (Motivation)
-
8/11/2019 SIA Enterprise Architecture
31/57
How it works?
Columns- One aspect of theenterprise from top to the
bottom from different
perspectives.
Source:http://www.zachmaninternational.com/2/ZachmanFramework.asp
-
8/11/2019 SIA Enterprise Architecture
32/57
September 13, 201432
Zachman Framework Row Scope
External Requirements and Drivers
Business Function Modeling
Row 2 Enterprise Model
Business Process Models
Row 3 System ModelLogical Models
Requirements Definition
Row 4 Technology ModelPhysical Models
Solution Definition and Development
Row 5 As BuiltAs Built
Deployment
Row 6 Functioning EnterpriseFunctioning Enterprise
Evaluation
1
2
3
4
5
6
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
-
8/11/2019 SIA Enterprise Architecture
33/57
September 13, 2014
A Tutorial on the Zachman Enterprise
Architecture Framework33
Framework Rules Rule 1:
Columns have no order
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Rule 2:
Each column has a simple, basic model
Rule 3:
Basic model of each column is unique
Rule 4:
Each row represents a distinct view
Rule 5:
Each cell is unique
Rule 6:Combining the cells in one row forms a
complete description from that view
Basic Model = Entities and Relationships
EntityRelationshipEntity
-
8/11/2019 SIA Enterprise Architecture
34/57
-
8/11/2019 SIA Enterprise Architecture
35/57
Row Descriptions
Here is a helpful hint for row Descriptions: Scope=Contextual = Planner
Business Model= Conceptual = Owner
System Model = Logical = Designer Technology Model = Physical = Builder
Detailed Representations = Detailed = Sub
Contractor
-
8/11/2019 SIA Enterprise Architecture
36/57
Functioning Enterprise Row
System down = no
work
Out of pencils = no
work
The systems are the enterprise!
-
8/11/2019 SIA Enterprise Architecture
37/57
Strengths and Weaknesses
Strength- End result (table)
WeaknessesNo process
http://www.powershow.com/view/3bf72-
ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_pr
esentation
http://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentationhttp://www.powershow.com/view/3bf72-ODI1Z/A_Tutorial_on_the_Zachman_Framework_for_Enterprise_Architecture_powerpoint_ppt_presentation -
8/11/2019 SIA Enterprise Architecture
38/57
Enterprise Architecture Terms
-
8/11/2019 SIA Enterprise Architecture
39/57
Key enterprise architecture terms
Explicit vs. Implicit Primitives vs. Composites
Integration vs. Interfacing
Alignment vs. Discontinuity Nature of Complexity
-
8/11/2019 SIA Enterprise Architecture
40/57
Explicit vs. Implicit
A cell that hasnt been modeled (made explicit,i.e. not discussed) is implicit by definition.
Assumptions have to be made when involving
implicit cells.
Assumptions generally have large margins for
error.
-
8/11/2019 SIA Enterprise Architecture
41/57
Primitives vs. Composites
Data elements primitives versuscomposites
Primitive models are architecturemodules
Composite models are implementationsintegrated
-
8/11/2019 SIA Enterprise Architecture
42/57
Integration vs. Interfacing
Integration: If you start with
primitive models,integration is easy
Single source data (orintegration) is optimal
Means sharing (notduplicating)
Interfacing: Data interfacing is
better than nothing,
but not optimal
Increases complexity
Has maintenance
issues
-
8/11/2019 SIA Enterprise Architecture
43/57
Integration vs. Interfacing
Integration: Reuse, not re-create
If you really want
integration and not
just interfacing, the
products (systems)
have to be
engineered that way
Interfacing: Inhibits change
Increases costs
Interfacing is a shortterm strategy, not a
long term solution
-
8/11/2019 SIA Enterprise Architecture
44/57
Alignment
Key element in enterprise architecture Means you want your functioning systems row
(row 6) to fully satisfy your enterprise intent
(row 1 and 2 models)
Manufacturing equivalent concept: Quality
If something (a process, work product, or
system feature, etc.) is not aligned with the
row above it, ask why are you doing it?
-
8/11/2019 SIA Enterprise Architecture
45/57
How do you achieve perfect alignment?
First, build row 1 models
Next, build row 2 models
Next, build row 3 modelsNext, build row 4 models
Next, build row 5 models
Ensuring that the intent of each row is
successfully represented (transformed) in thesucceeding row
-
8/11/2019 SIA Enterprise Architecture
46/57
Perfect alignment in face of change?
When change happens or is needed, go backto your blueprints (models) and change themfirst
Transform the change through the rest of the
framework Net impact of the change will be your gap
analysis
Nothing will be left out of the impact if your
models are accurate
-
8/11/2019 SIA Enterprise Architecture
47/57
Discontinuity
Means lack of alignment somewhere in theframework (not following standards)
Translates to unhappy users and dissatisfied
management
Any time you have duplication, you havediscontinuity
Reduce discontinuity by reducing redundant
systems and redundant data
-
8/11/2019 SIA Enterprise Architecture
48/57
Discontinuity
Interfacing causes discontinuityCompensate in the short term to mix pieces
Integrating provides alignmentReengineerto take out the discontinuity long term
-
8/11/2019 SIA Enterprise Architecture
49/57
Nature of Complexity
There is a certain amount of complexity builtinto any enterprise, product or service
Three change models for complexity without
architecture
Trial and errorJust do it
Reverse engineerTakes time and costs a lot of
money
Scrap and start over
Or you can engineer the change with yourarchitectural blueprints
-
8/11/2019 SIA Enterprise Architecture
50/57
Nature of Complexity
If you dont deal with the complexity within theenterprise, it gets pushed to the customer
-
8/11/2019 SIA Enterprise Architecture
51/57
Lessons Learned Through EA
Goal is to isolate the change, estimate theimpact, and provide a tool for managing thechange for optimal success
It is a model to come up with rational/balanceproblem solving
Discontinuity in the framework causesdissatisfaction among management andcustomers
-
8/11/2019 SIA Enterprise Architecture
52/57
Lessons Learned Through EA
You cant integrate systems (optimally) if youdont build them for integration (hold data once)
Technology change should not interrupt theenterprise
-
8/11/2019 SIA Enterprise Architecture
53/57
Lessons Learned Through EA
If you implement a COTS system , you mustchange your business processes
Every person (and their job function) in theorganization will be on the framework
somewhere
Projects must be architected
-
8/11/2019 SIA Enterprise Architecture
54/57
Integrated Enterprise Information Systems?
Enterprise
A business, an industrious effort, especially one
directed toward making money
Information System
A set of interconnected channels for communicatingknowledge of specific events or situations
Integrated
Joined together, united,
made into a wholeby having brought
all parts together
-
8/11/2019 SIA Enterprise Architecture
55/57
Enterprise EngineeringAn Enterprise is a complex system of cultural,
process, and technological components that interactto accomplish strategic goals.
People
Processes
Technology
Accomplish
Organizational
Goals
-
8/11/2019 SIA Enterprise Architecture
56/57
What is Enterprise Integration?
Definition:the task of improving the performance of
large complex processes by managing the
interactions among theparticipants
-
8/11/2019 SIA Enterprise Architecture
57/57
What is Enterprise Integration?
Assys Supplier
Part Supplier
Customer Part Order
Product Design
Product Order Work Order Product
Part
Assys Spec.
Purchase Order
Production Planning
Supply ChainEngineering Process
Distribution
Enterprise Integration
Part
Part Design
Sub -Assys