unhelkar mis week08 entarch togaf

8/9/2019 Unhelkar MIS Week08 EntArch TOGAF

1/40

Designed & Presented by

Bhuvan Unhelkar, PhD, [email protected]: 0413-821-454;

www.unhelkar.com

MethodScience 2001-2014

Management Information Systems v1.0Week 8: Enterprise Architectures

(EA)(Part ofPost Graduate Program in Management (PGPM)The Great Lakes Institute of Management, Chennai, India)


2/40

Lecture Agenda

Relating the Enterprise through Architecture:

Importance for positioning and use of MIS

Important for a Semantic Enterprise

Importance in developing MISZachman, TOGAF and System Architectures

The What-Why-When-Where-How-Who of

Zachman Enterprise ArchitectureCreating a Service Oriented Architecture

Case study discussion

Course: Management Information Systems

Great Lakes Institute, Chennai, India; MethodScience


3/40

Sub-Module

Architectures and MIS

Where and How Architectures help

MethodScience; Material Designed and Presented by Dr. B. Unhelkar


4/40

Architectural Considerations:

Higher abstractions than designs

Architect

Design

Develop


Great Lakes Institute, Chennai, India; MethodScience4

Think through the

Solution in the Context

of Needs, Capabilities

and Existing

environment

Produce the solution

Think through the

Solution (Model)


5/40

Architectural Frameworks:

Most Helpful for Business-IS synergy

Provide Basisfor

Understanding

EnableSensible

Comparison

EnhanceReuse and

Quality

JumpstartNew

Systems/Enterprises

Facilitate

Measures andControls

SupportTransitions

(BusinessTransformations)




6/40

Technology

Enterprise Architectures facilitate Meaningful Exchange

of Data and Information leading to Collaborative

Processes and Knowledge (based on Murugesan, S. & Unhelkar, B.)

Information

Silo

Information

SiloDirect

Information Exchange

Internet-based


Meaningful Internet-based


Semantic Enterprise

People / Knowledge

(Enhanceduser experiences)

Collaborative / GlobalProcesses

S e m a n t i cW e b

Legacy

Silo


7/40

ARCHITECTURAL

Frameworks Zachman Enterprise

Architecture (EA v 3.0)

The Open GroupArchitecture Framework

(TOGAF v9.0)

Software Architecture(4+1) & SOA

other frameworks




8/40

Sub-Module

Zachman EA Framework

An Enterprise Ontology:

Identify; Define; Represent, Specify,Develop/Configure, Instantiate



9/40



Identify

Define

Represent

Specify

Develop

I nstantiate


10/40

Zachman Framework (Detailed)Excellence in Positioning MIS in the Context of an

Organization/Business




11/40

Short Exercise Circle the Best Option

Q 1: In the Zachman EA

framework, building a

Business Process Model ispart of :

(a) DATA (What)

(b) FUNCTION (How)

(c) NETWORK (Where)

(d) PEOPLE (Who)

11MethodScience.com, 1998-2014

Q 2: In the Zachman EA

framework, developing a

Security Architecture is part of:

(a) DATA (What)

(b) NETWORK (Where)

(c) PEOPLE (Who)(d) TIME (When)

Sh E i


12/40

Short Exercise

Circle the Best Option

Q 3: The Physical Data/Class

model belongs to:

(a) Enterprise Model

(b) System Model

(c) Technology Model

(d) Detailed Representation


Q 4: The Distributed Systems

Architecture belongs to:

(a) Enterprise Model

(b) System Model

(c) Technology Model

(d) Detailed Representation


13/40

Sub-Module

The Open Group Architecture

Framework TOGAF)

As a Reference Architecture for use

of MIS



14/40

TOGAF EA domains

BusinessArchitecture

ApplicationsArchitecture

DataArchitecture

TechnicalArchitecture



+ Architecture Development Method (ADM) + Enterprise Continuum

Individual Apps

and theirIntegration

(Enterprise;

Consumer)

Meta Data;

Logical, Physical;Unified,

Harmonized

Hardware;

Optimizing

Systems andNetworks

Business strategy,

governance,

organization and

key Business

Processes

K El t f TOGAF 9 1


15/40

Key Elements of TOGAF 9.1http://pubs.opengroup.org/architecture/togaf9-

doc/arch/




16/40

Key Elements of TOGAF-1

Architecture Development Method (ADM)

is applied to develop an enterprise architecture

which will meet the business and information

technology needs of an organization

ADM Guidelines and Techniques

tailored to the organization's needs and is then

employed to manage the execution of

architecture planning activities

Architecture Content Frameworkstructured meta-model for architectural artifacts,

the use of re-usable architecture building blocks,

and an overview of typical architecture

deliverablesCourse: Management Information Systems



17/40

Key Elements of TOGAF-2

Reference Models

provides a selection of architectural reference models,which includes the TOGAF Foundation Architecture,

and the Integrated Information Infrastructure

Reference Model

Enterprise Continuum

The Enterprise Continuum is a way of classifying

solutions and architectures

Ranges from generic foundation architectures through

to tailored organization-specific

Include architectural models, patterns, descriptions

and other artefacts.

Architecture Capability Framework

discusses the organization, processes, skills, roles,

and responsibilities required to establish and operate

an architecture function within an enterprise.Course: Management Information SystemsGreat Lakes Institute, Chennai, India; MethodScience

17


18/40

Business Architecture

Information Architecture

Application Architecture

Technology Architecture

Vision

Mission

























Business Functions Reference Model

Business Process Reference Model

Applications Reference Model

Technology Reference Model

Subsequent EAprojects at

business

segment/function

level

End to End

Enterprise Level

initial EA

EnterpriseReference ModelsConceptual Data Model

Security

Architecture

Architectur

e

Principles

Reference Architecture Model

(ack. A. Unhelkar, 2009)

Without such a

Reference

Architecture, MIS

in most modern

organizations will

lead to massive

conflicts and

friction.

Architectures

ensure MIS are

positioned correctly

in the context of the

organization

Sh t E i


19/40

Short Exercise

Circle the Best Option

Q 1:The Four Enterprise

Architecture Domains in

TOGAF are :

(a) BusinessFunctional

Technical - Applications

(b) BusinessDataTechnical- Applications

(c) BusinessDataNetwork-

Applications

(d) UserDataTechnical -

Applications


Q 2: ADM in TOGAF stands for

:

(a) Application Development

Method

(b) Analysis & Development

Method

(c) Architecture DevelopmentMethod

(d) Algorithm Development

Method


20/40

Sub-Module

Software Architecture

Relating to EA - SOA



21/40

Enterprise Architecture Imposes Constraints on Modeling the

Problem and Creating the Solution

Information

Architecture

Solution

Architecture

Enterprise

Architecture

[IT Specific]

User

InformationArchitect

SolutionArchitect

CEO/CIO

EnterpriseArchitect

QualityPersonnel

What the Business Need? Where?

How the Solution Provides for It?

Why Does a Business

Need to Change?

What are the

Constraints?

Technical,

Environmental,

BusinessSolutionDesigner Developer

Business Space

Technology Space

BusinessAnalyst

Business

Architecture


22/40

4+1 Software Architecture(Philippe Kruchten, IEEE, 1995 Notes from Wiki)




23/40

A Service-Oriented-Architecture

(SOA)




24/40



Sh t E i


25/40

Short Exercise-

The Five tiers discussed in an SOA are:



26/40

Key Points Summary)

Architectures were discussed as basis for

most modern-day MIS

Specific Architectures provide robustness,

reuse and quality to Information Systems

Enterprise Architectures provide necessarycontext to map MIS to business

Zachman was considered in the context of the

overall enterprise and not just one information

systemTOGAF and SOA were also discussed


27/40

References

As discussed during lecture




28/40


Great Lakes Institute, Chennai, India; MethodScience

A. You, as Enterprise Architect of your

organization, has to decide betweenZachman and TOGAF. Consider some of the

factors that will be involved in this decision

making. Discuss them with reasons.

B. Would you consider developing a MISwithout a reference architecture? Why?

Why not?

28


29/40

Project Work(Group-based Case Analysis,

Report & Presentation)

a) Documented: Businessobjectives, DATA needs,

Project lifecycle (with

Iteration & Increment) for

your MIS, Business

processes, SMACmapping to MIS, and

outline of how your

organization will become

and remain AGILE

b) Continue to review whatyou are writing; Note the

minutes of your meetings

Course: Management Information System (MIS)


a) Consider ALL the cells inZachman framework;

Attempt to document All of

them (except last row) for

your enterprise (this can be

a single large table in yourreport)

b) Separately discuss the cells

that are directly satisfied by

your MIS; and those that are

outside the Systemc) Note: Your business

objectives documented

earlier will be modified by

this exercise

By now you will have In this week you will be


30/40

Sub-Module

Additional Material

Later use



31/40

Course: Management Information SystemsGreat Lakes Institute, Chennai, India; MethodScience

31

Alt ti El t f TOGAF


32/40

Alternative Elements of TOGAF

(More Explanation Follows)


32

A TOGAF MindMap:


33/40

A TOGAF MindMap:http://www.biggerplate.com


33

Zachman Framework:


34/40

Zachman Framework:Column DATA (WHAT)


34

Scope & Context

(Planner)

Business ModelConcept (Owner)

System Model

(Designer)

Technology Model

(Builder)

DetailedImplementation(Programmer)

Functioning

Enterprise (User)

Zachman Framework:


35/40

Zachman Framework:Column FUNCTION (HOW)


35

Scope & Context

(Planner)


System Model

(Designer)

Technology Model

(Builder)


Functioning

Enterprise (User)

Zachman Framework:


36/40

Zachman Framework:Column NETWORK (WHERE)


36

Scope & Context

(Planner)


System Model

(Designer)

Technology Model

(Builder)


Functioning

Enterprise (User)

Zachman Framework:


37/40

Zachman Framework:Column PEOPLE (WHO)


37

Scope & Context

(Planner)


System Model

(Designer)

Technology Model

(Builder)


Functioning

Enterprise (User)

Zachman Framework:


38/40

Zachman Framework:Column TIME (WHEN)


38

Scope & Context

(Planner)


System Model

(Designer)

Technology Model

(Builder)


Functioning

Enterprise (User)

Zachman Framework:


39/40

Zachman Framework:Column MOTIVATION (WHY)


39

Scope & Context

(Planner)


System Model

(Designer)

Technology Model

(Builder)


Functioning

Enterprise (User)

Short Exercise: Take any ONE of the Zachman xx


40/40

y

for your Case study and complete the following

C M t I f ti S t 40

Scope & Context

(Planner)


System Model

(Designer)

Technology Model

(Builder)


Functioning

Enterprise (User)

unhelkar mis week08 entarch togaf

Documents