© minder chen, 1997-2008 enterprise architecture - 1 source:...

© Minder Chen, 1997-2008 Enterprise Architecture - 1 Source: http://emi-web.inel.gov/roadmap/factsheet.pdf

Use EA as a roadmap to supports good IT planning,

investment decisions

Mount

surpriseContingency

Drive

Regulatory

Mountain

Data rich and information

poor

Uncertainty Gap

Successful Program and project

management

Current Resources /

Systems

Migration path

Business

Applications

Service

building blocks

Technical architecture

© Minder Chen, 1997-2008 Enterprise Architecture - 2

Evolution of EA

• BSP: Business Systems Planning

• ISF: Zachman Information Systems Framework

• ISP: Information Systems Planning

• EAP: Enterprise Architecture Planning

• EA: Enterprise Architecture


BSP: Business Systems Planning


Zackman Framework

Source: http://www.zifa.com/framework.pdf


Information Strategy Planning Tasks

Initial

Assessment

Project

Planning

Information

Architecture

Definition

Business System

Architecture

Definition

Current

Environment

Assessment

Technical

Architecture

Definition

ISP

Project

Completion

Organization Model Business

Objectives Information Needs

Activity Model (AHD & ADD) Data Model (ERD)

Entity Type/Function (CRUD) Matrix

Current Systems & Data Current Information Architecture Coverage

IS Organization Using RAEW Matrix Current Technical Environment

Cluster CRUD Matrix Business Area List

Ranked BAA Projects

BAA Distribution Analysis Technical Requirements

Technical Direction


Levels of Enterprise Architecture Planning

Planning

Initiation

Existing

Business

Model

Current

Systems &

Technology

Data

Architecture

Applications

Architecture

Technology

Architecture

Implementation and

Migration Plans

Getting started

Where we

are today

The vision of where

we want to be

How we plan

to get there

Source: Steven H. Spewak, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, John Wiley & Sons, Inc., 1992, p. 16.


References1. Texas Instruments, A Guide to IE Using IEF, 2nd edition,

Part No. 2739756-0001, 1990.

2. Martin, James, Information Engineering Book I: Introduction, Prentice-Hall Inc., 1989.

3. James Martin with Joe Leben, Strategic Information Planning Methodologies, 2nd edition, Prentice-Hall, Inc., 1989.

4. Spewak, Steven H. with Steven C. Hill, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, New York: John Wiley & Sons, Inc., 1992.

5. IBM, Business Systems Planning: Information Systems Planning Guide, Fourth edition, Order Number: GE20-0527-04, July 1984.

6. IBM Systems Journal: A Special Issue on Enterprise Analysis, Vol. 21, No. 1, 1982, Order Number: G321-0068.


Introduction to ISP

• Develop a high-level view of the enterprise-wide information requirements and furnish a plan to fulfill these requirements.

• Central task: Define an architectural framework for future applications


ISP Purposes

• Gain top level commitment to information systems• Develop IS strategy based on business strategy• Manage data as corporate resource• Coordinate IS plans:

– Business strategies and goals – Systems plans– Technical plans

» Hardware» Software» Networking

– IS organization and resource plans


Major Components in the ISP

ISP

Organization Structure

InformationTechnology

BusinessStrategy

InformationStrategy


Business-Driven Planning

BusinessObjectives

BusinessFunctions

Information Needs

Information Systems

give priorities

to

determineare

fulfilledby

support

START


Linking ISP with Business Strategies

• Understand the environments culture of existing business

• Identify information requirements in the long run

• Develop a baseline to determine systems development priority

• Link IS with organizational strategies and objectives


Categories of Information Used in ISP• Business Objects

– Mission– Objective– Strategy – Goal – Critical Successful Factor– Plan – Performance Measure

• Organizational Objects– Organizational Unit– Organizational Structure

• Activity Object– Business Function– Business Process

• Data Object– Subject Area– Entity Type– Information Need


Key Elements in ISP • Information Architecture

– Specifications of activities performed by the enterprise and the information required to perform these activities

– Basis for the Business Area Analysis stage

• Business System Architecture – Descriptions of Business Systems and Data Stores required to support the

Information Architecture

– Basis for the Business System Design stage

• Technical Architecture– Requirements of hardware and software environments needed to support the

Business System Architecture

– Basis for the Technical Design stage

• Information Management Organization– The organization of IS organization to implement proposed ISP


Deliverables: ISP• Facts about the enterprise

– A Mission Statement; an Information Needs map; a list of Objectives, CSF, and Strategies by Organization Unit, a ranked list of objectives.

• Facts about the current environment– IS organization; software/hardware/application systems

• Information Architecture– Subject Area Diagram and high level ERD; a overall Function Hierarchy Diagram; a set of Function Dependency Diagram,

supporting matrices.

• Business System Architecture– A prioritized list of BAA projects in an Implementation Plan

• Technical Architecture– A statement of technical direction

• ISP Report


Information Strategy Planning

1. Planning the ISP Project

2. Making the initial assessment

3. Defining the Information Architecture

4. Assessing the current environment

5. Defining the Business System Architecture

6. Defining the Technical Architecture

7. Planning for the BAA and Completing ISP


Information Strategy Planning Tasks

InitialAssessmen

t

ProjectPlannin

g

InformationArchitectur

eDefinition

Business SystemArchitecture

Definition

CurrentEnvironmen

tAssessment

TechnicalArchitectur

eDefinition

ISPProject

Completion

Organization Model Business

Objectives Information Needs

Activity Model (AHD & ADD) Data Model (ERD) Entity Type/Function (CRUD) Matrix

Current Systems & Data Current Information Architecture Coverage IS Organization Using RAEW Matrix Current Technical Environment

Cluster CRUD Matrix Business Area List Ranked BAA Projects

BAA Distribution Analysis Technical Requirements Technical Direction


Levels of Enterprise Architecture Planning

Planning

Initiation

Existing

Business

Model

Current

Systems &

Technology

Data

Architecture

Applications

Architecture

Technology

Architecture

Implementation and

Migration Plans

Getting started

Where we

are today

The vision of where

we want to be

How we plan

to get there

Source: Steven H. Spewak, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, John Wiley & Sons, Inc., 1992, p. 16.


Relationship of The Three Architecture

Data

Model

Activity

Model

Interaction

Model

Information Architecture

Business

Areas

Natural Business Systems

BusinessSystems

Architecture

Current Systems Analysis

Existing & Proposed IS

Hardware

Platforms

Software Development Environments

TechnicalArchitecture

Data Management

Security

Networks

Adapted from: Elaine Sill, "Information Engineering and Its Architectures," CASE Trends, Vol. 4, No. 3, May 1992, pp. 15-17


Planning the ISP Project

• Setting the scope of the project– Managing expectation – Establishing organizational and time boundaries– Determining information technologies boundaries – Formulating the statement of objectives

• Forming the project task force– The project sponsor – The project team: Project manager, ISP expert, Business expert ,

Technical Expert. – Reference team, administrative and clerical support

• Developing the project schedule– Establishing a detailed task list and project checkpoints– Estimating task duration:

» 80 person-days for interviewing (40 interviews; 1 day & two persons per interview)

» 30-80 man-days for specifying an information architecture Interviewing and constructing Information architecture take 1/2 of the project time


Making the Initial Assessment

• Specify Organization Structure– Organizational Units: Name & Person-in-charge

• Identify and rank Objectives and CSFs– Identify the following Entities by Organizational Unit: Mission, Objective,

Strategy, Critical Success Factor (CSF), Goal, Plan

– Develop Enterprise/Organizational Unit Objective Matrix

– Prioritize List of Objectives for the enterprise and each major Organizational Unit

• Determine Information Needs and Performance Measures– Construct Information Needs List: Description, Usage, Objectives supported,

Supporting systems, Important factor, Satisfaction factor, Requirements weight

– Develop Information Needs/Organization Matrix and Performance Measure/Organization Matrix


Examples of Mission, Objectives, CSF

• Missions– To provide high quality PC products to satisfy ever-changing customer needs and

achieve maximum return for stakeholders.

• Objectives– Maintain peripheral business at 25% of total sales

– 15% market share in the Unite States

– Sales growth of at least 10% per year

– ROI of 15% per year

• Critical Success Factors– Effective OEM relationships with major PC suppliers in Asia

– Effective research and development of emerging technologies

– Understand customer needs and industry trends

– Accurate prediction of customer demands

– Management of major marketing channels


Making the Initial Assessment (Continued)

• Assess potential impacts of information technology – Include Hardware Items and Software Products– Assess the role of IT:

» Become (part of) a product or service » Deliver a product or service » Gain competitive advantage

• Define a preliminary Information Architecture– Identify the following Entities by Organizational Unit:

Mission, Objective, Strategy, Critical Success Factor (CSF), Goal, Plan

– Develop Enterprise/Organizational Unit Objective Matrix– Prioritize List of Objectives for the enterprise and each major

Organizational Unit


Tasks of Assessing the Current Environment

• List all the current and planned systems and data stores.

• Determine the coverage of current information architecture (consisting of current systems and data stores) against entity types and functions.

• Define a list of information needs.

• Assess IS organization using RAEW Matrix. – R: Responsibility; A: Authority

– E: Expertise; W: Work

• Analyze current technical environment.


Purpose of Analyzing Current and Planned Systems and Data Stores

• Develop transition plan

• Determine development priority

• Confirm information architecture


On Modeling

• Modeling the system that the user wants is the primary job of a systems analyst.

• Models of the system-to-be is abstract representations of what will eventually become a combination of computer hardware and software.

• Examples of models in our daily life: – Maps

– Globes

– Flowcharts

– Architect’s drawing


On Modeling

• Models are abstract representations of real world systems.

• A model is used to emphasize important system features while other aspects of the system are de-emphasized.

• One should avoid analysis paralysis.

• Sometimes we need to use several modeling techniques to describe various aspects of a system in order to present a complete picture of the system.

• Models are used as media to facilitate the communication between systems developers and users.

• A model should be used as a strawman. Changes and corrections can be made to the model with low cost and minimal risk.


Modeling Aspects of IE

Data Activity

Interaction

• Subject Area Diagram• Entity Relationship Diagram• Data Structure Diagram• DDL: Data Definition Language• Installed Database

• Function Hierarchy Diagram• Function Dependency Diagram• Process Hierarchy Diagram• Process Dependency Diagram• Dialog Flow Diagram• Load Module Package

• Expected Effects of a Process on Entity Types • Function/Entity Type Matrix• Elementary Process/Entity Type Matrix• Process Action Diagram & Process Action Block • Procedure Action Diagram• Screen/Window Layout


Activity Models

Software on Us

Marketing

Manufacturing

Market Analysis

Advertising

Inventory Control

Production Planning


Data Models

order is part of

contains

customer

places

is placed by

is ordered by

has

ORDERS

Subject Area

Entity Type

product

orderitem


Interaction Models: Matrix

Order Employee Inventory Vendor

Marketing C R

Manufacture R C

Finance Human

Resource C

Purchasing U CAdminis-

tration R

Func. Entity

C: Create; R: Read; U: Update; D: Delete

Function/Entity Type Matrix Function/Entity Type Matrix


Systems As Planned Organizational Change

Process/Data Class Matrix

Figure 12-1


Cluster Analysis

orderitemis part of

contains

customer product

places

is placed by

is ordered by

has

order

Data Model

Marketing

Manufacturing

Market Analysis

Advertising

Inventory Control

Software on Us

Activity ModelInteraction

ModelFUNCTION

Entity Type

CRUD

Domain Experiences

PracticalIssues

Activity Clusters

DataClusters

Business Areas /

Business Systems

Cluster Analysis


Business Systems Architecture Diagram

StrategicPlanning

Planning & Analysis

ManagementControl

Operational Control

Operational Processing

Function 1Function 2Function 3Function 4

High Level Business Function

SystemsCategory

BusinessSystem 1

BusinessSystem

2

BusinessSystem 3

Information Flow

Function 5


(facilitation)

DatabaseTechnology

Database Structures

Database Schema

Data Requirements

Business Subjects

Data

Application Programs

Application Schema

Business Processes

Business Functions

Processes

Component Programs

Interface Schema

Interface Requirements

System Context

Interfaces

Software(and Hardware)

Technology

InterfaceTechnology Networking

Technology

Network Programs

Network Schema

Communication Reqts.

Operating Locations

Geography(Networks)

CREATE TABLE CUSTOMER (customer_no CHAR(10) NOT NULL

customer_name CHAR(32) NOT NULL customer _rating CHAR(1) NOT NULL

balance_due DECIMAL(5,2) CREATE INDEX cust_no_idx on CUSTOMER CREATE INDEX cust_rt_idx on CUSTOMER

CUSTOMER customer-no customer-name customer-rating

balance-due

PRODUCT product-no product-name unit-of-measure

unit-price quantity-available

ORDER order-no order-date

products-ordered quantities-ordered

Order Form

Help +

Customer Form

Product Lookup

Logon

New Customer

New Order

Order Accepted

Change of

Address

First Order

Request Order Help

Order Help Complete

Request Product Lookup

Request Product Lookup Help

Product Lookup Help Complete

On Event Help.ButtonClick Do

Change Focus HelpDialog

On Event OKButton Do

Begin

{proecdure} End

On Event CancelButton Do

Create AccountType = SalesClerk

Set OrderDir.Rights=full Set CustomerDir.Rights=full Set ProductDir.Rights=read Set OrderAppDir.Rights=copy

Customers order zero, one, or more products. Products may be ordered

by zero, one, or more customers.

Marketing

Advertising

Orders

Sales

Cancellations Services

Order Management

SystemCustomer

Accounts Receivable Database

Warehouse

Bank

OrderPicking Order

Credit

Credit Voucher

Check credit

Validate customer

Validate products

Release order

Customers

Orders

Products

order

customer number

valid order

order without valid

customer

credit

order with valid products

approved order

quantity in stock

approved order

rejected order

prices

picking ticket

Firecracker Sales

EDI Cust

St. Louis HQ

LA Office

Indy Ware- house

NY Office

West Customers

East Customers

Maintenance Records

Products Catalog

ordercatalog changes

ship order

ship order ship order

credit credit

service

CUSTOMER customer_no [Alpha (10)] INDEX

customer_name [Alpha(32)] customer_rating [Alpha(1)] INDEX

balance_due [Real(5,2)]

PRODUCT product_no [Alpha(10)] INDEX

product_name [Alpha(32)] unit_of_measure [Alpha(2)]

unit_price [Real(3,2)] quantity_available [Integer(4)]

ORDER order_no [Alpha(12)] INDEX order_date [Date(mmddyyyy)

CUSTOMER.customer_no

ORDER_PRODUCT ORDER.order_no

PRODUCT.product_no quantity_ordered [Integer(2)

Order Processing

Program

Process an Order

Initiation Routine

Shutdown Routine

Get an Order

Validate an Order

File an Order

Check Customer

Credit

Check Product

Data

Check Credit Data

Release an

Order

Customers Products Orders

St. Louis Mainframe

Indy AIX Server

NT Server LA

NT Server NY

Communications Controller

PBX

Enternet LAN AIX/Lan Manager

Ethernet LAN/NT

Ethernet LAN/NT

Client PC Client PC

Client PC Client PC

VALIDATE_AN_ORDER. REPEAT UNTIL NO_MORE_ORDERS

PERFORM CUSTOMER_VALIDATIO REPEAT UNTIL NO_MORE_ORDER

PERFORM PRODUCT_VALIDATI END REPEAT.

PERFORM CREDIT_CHECK. IF CREDIT_CHECK 'BAD' THEN

Information Systems FrameworkS

ys

tem

An

aly

sts

SystemOwners(Scope)

SystemUsers

(Requirements)

SystemDesigners(Specification)

SystemBuilders(Components)


Zachman Framework

• Row 1 – ScopeExternal Requirements and DriversBusiness Function Modeling

Row 2 – Enterprise ModelBusiness Process Models

Row 3 – System ModelLogical ModelsRequirements Definition

Row 4 – Technology ModelPhysical ModelsSolution Definition and Development

Row 5 – As BuiltAs BuiltDeployment

Row 6 – Functioning EnterpriseFunctioning EnterpriseEvaluation

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


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


Zachman Framework – Row 1 Scope/Planner’s View

• External Requirements and Drivers

• Business Function Modeling

• Motivation/WhyBusiness goals, objectives and performancemeasures related to each function

Function/HowHigh-level business functions

Data/WhatHigh-level data classes related to eachfunction

People/WhoStakeholders related to each function

Network/WhereVA locations related to each function

Time/WhenCycles and events related to eachfunction

1 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


Zachman Framework – Row 2 - Enterprise Model/Designer’s View

• Business Process Models• Business Function

Allocation• Elimination of Function

Overlap and Ambiguity

• Motivation/WhyPolicies, procedures and standards for

each process

Function/HowBusiness processes

Data/WhatBusiness data

People/WhoVA roles and responsibilities in eachprocess

Network/WhereVA locations related to each process

Time/WhenEvents for each process and sequencingof integration and process improvements

2

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


Zachman Framework – Row 3 System Model/Designer’s View

• Logical Models• Project Management• Requirements Definition

• Motivation/WhyVA policies, standards and proceduresassociated with a business rule model

Function/HowLogical representation of informationsystems and their relationships

Data/WhatLogical data models of data and datarelationships underlying VA information

People/WhoLogical representation of access privilegesconstrained by roles and responsibilities

Network/WhereLogical representation of the distributedsystem architecture for VA locations

Time/WhenLogical events and their triggered responses constrained by business events and their responses

3Contextual

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


Zachman Framework – Row 4 Technology Model/Builder’s View

• Physical Models• Technology Management• Solution Definition and

Development

• Motivation/WhyVA business rules constrained by informationsystems standards

Function/HowSpecifications of applications that operateon particular technology platforms

Data/WhatDatabase management system (DBMS) typerequirements constrained by logical data models

People/WhoSpecification of access privileges tospecific platforms and technologies

Network/WhereSpecification of network devices and theirrelationships within physical boundaries

Time/WhenSpecification of triggers to respond to systemevents on specific platforms and technologies

4

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


Zachman Framework – Row 5 As Built/Integrator’s View

• As Built• Configuration Management• Deployment

• Motivation/WhyVA business rules constrained by specific technology standards

Function/HowPrograms coded to operate on specific technology platforms

Data/WhatData definitions constrained by physical data models

People/WhoAccess privileges coded to control access to specific platforms and technologies

Network/WhereNetwork devices configured to conform to node specifications

Time/WhenTiming definitions coded to sequence activities on specific platforms and technologies

5

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


Zachman Framework – Row 6Functioning Enterprise/User’s View

• Functioning Enterprise• Operations Management• Evaluation

• Motivation/WhyOperating characteristics of specific technologies constrained by standards

Function/HowFunctioning computer instructions

Data/WhatData values stored in actual databases

People/WhoVA personnel and key stakeholders working within their roles and responsibilities

Network/WhereSending and receiving messages

Time/WhenTiming definitions operating to sequence activities

6

Contextual

Conceptual

Logical

Physical

Integrated

Functioning

Contextual

Conceptual

Logical

Physical

Integrated

Functioning

Why

Why

Who

Who

When

When

Where

Where

What

What

How

How


VA Zachman Framework Portal


IBM's Business Systems Planning Methodology

Business

Objectives

Business

Objectives

Business

OrganizationBusiness

Process

Business

ProcessApplication

Business

Data

Data

Bases

Information

Architecture

Top-down planning & analysis Bottom-up design & implementation

Source: IBM, Business Systems Planning, GE20-0527-04, 1984.


OperationDatabase

TransactionProcessing

System

ManagementInformation

Systems

Data

Data

Data &messages

Read-only dataData

snapshots

Data Data

Problem

Manager

Information

need

Management

information

Relevant User

User

Transaction Data

Transaction

information

DSS Database

DecisionSupportSystem

ExecutiveInformation

SystemRead-only data

Decision support information

Executive information

Decisionmaker or executive

ExpertSystem

Comminations betweenusers and within groups

OfficeInformation

System

Problem

SolutionKnowledgeDatabase

Personal Files & Database

PersonalInformation

System

Personal data

Personalinformation

User

Captureddata

Shareddata

Knowledge

Information Systems Types and Their Relationships


Technical Architecture

Information Technology Areas

CIMCAD/CAM

TransactionProcessing

OfficeAutomation

Messaging/Networking

Scope

Inter-organization

EnterpriseWide

DepartmentalComputing

WorkgroupComputing

PersonalComputing

• Information technology area

• Scope

• Technical facilities

• Networks among facilities

• Location


The Real and Conceptual Worlds

Information

ArchitectureBusiness Areas/

Natural Business Systems

Conceptual World

Organization

Models

Current

Technical

Environ.

Real World

Technical

Architecture

Proposed

IS

Current

Systems

Technical Directions

Adapted from: Elaine Sill, "Information Engineering and Its Architectures," CASE Trends, Vol. 4, No. 3, May 1992, pp. 15-17


Transformation through Enterprise Architecture

George Paras, "Embrace Enterprise Transformation as a Core Concept," Architecture & Governance, Summer 2005, pp. 15-17.


Overall FEA Schema

Source: http://www.actgov.org/actiac/documents/ sigs/easig/EAMaturityWP013105.pdf


Federal Enterprise Architecture

The FEA was established by OMB, with support from GSA and the Federal CIO Council


The Business Reference Model


Structure of the FEAF Components


PRM Articulates Line of Sight


Performance Reference Model


Service Component Reference Model


Conceptual/Process Model


Technical Reference Model


U.S. Customs Technical Reference Model


Technical Reference Model


IT Infrastructure as a Centrally Coordinated Set of Shared and Reliable Services


IT Infrastructure can be deployed at multiple levels


IT Infrastructure Services in 10 Clusters

Local I T Applications

Standardized Interfaces

Agreed-upon Standards

© minder chen, 1997-2008 enterprise architecture - 1 source:...

Documents