Enterprise Architecture

Enterprise Architecture = a framework or ‘blueprint’ for how the organization achieves the business objectives at hand and in futureComprehensive description of all of the key elements and relationships that make up an organizationLook at key business, information, application and technology strategy & impact on business functions

Enterprise Architecture

Organization’s business and info needsLeverage of the synergistic relationship between ROI and Total Cost of OwnershipAble to support migration from the current stateAble to support easy migration to the organization’s desired futureSupport business objectives of reducing costs, improve service, increase revenue

Concern on

Why Enterprise Architecture

Improve business benefit derived from ITReduce costs associated with ITReduce risk in adopting and exploiting ITEnable desirable business changes, pursuit of opportunitiesShorten lead times to realizing benefitsExploit emerging technologies which can provide strategic advantageProvide framework for decision making and practice within development, technology purchase and operations

SYSTEM ARCHITECTURE

Enterprise Architecture (c’td)

Enterprise Architecture

Business Architecture

Information Architecture Application Architecture

Technical Architecture

Product Architecture

Functionality that delivers value to the business

Enabling infrastructure that supports the other architecture

Enterprise Architecture (c’td)

Each of the strategies is a separate architectural discipline

EA used to keep them together in a cohesive framework

The strategies are: business, information, application, technical & product architecture

System architecture is to support the higher layers of the EA

Enterprise Architecture (c’td)Business Architecture = define business

strategies, processes & functional requirements. Provides the tools the business needs to ensure the quality & consistency of business design.

Enterprise Architecture (c’td) Information Architecture = modeling the

information needed to support business process and functions of the enterprise. It spans the organizational boundaries and ties the business processes identified in Business Architecture. Can be expressed in the form of data models, information flows & analysis of input/output.

Enterprise Architecture (c’td)Application Architecture = focused on

developing and/or implementing applications to fulfill the business requirements & meet business needs. Also considering on the relationship between applications and optimizing and managing the integration of multiple applications. Expressed in terms of the entire life cycle of an application i.e. from the initial development through sustaining evolution and maintenance to replacement or retirement.

Enterprise Architecture (c’td) Technical Architecture = provides foundation

that supports the applications, data and business processes identified in the other three architectural layers. Identifies and plans the computing services (including applications / hardware / tools) that form the technical infrastructure for the enterprise.

Product Architecture = identify standards and configurations for the enabling technologies & products within the Technical Architecture

Developing Enterprise ArchitectureProcess proposed by Paul Harmon,

Developing an Enterprise Architecture, 2003

1. Agree on the need

2. Establish an organizational Structure

3. Select a framework

4. Select a tool and repository

5. Organize the existing material

6. Begin using the Enterprise Architecture

7. Extend and maintain the architecture

Applications of Information Technology

Interorganizational systems Intraorganizational systemESSMISDSSKWSOASTPS

Enterprise System

Organization can integrate and coordinate their major internal business process

Solve problems of isolated islands of information, business process and technology

Discrete business processes from sales, production, finance and logistics can be solved

Benefits of Enterprise SystemCreate more disciplined organizational

culture Improve management reporting and

decision makingProvide firm with single, unified

information on all key business processData are common, standard and have

same format Improve customer service Improve supply change management

Challenges of Enterprise System

Difficult and costly to buildBPR TimelyMay not suitable for some organization

Enterprise Information ArchitectureDeveloped by John Zachman for designing an enterprise information architectureAllows integration & coordination across the enterprise (vertical - horizontal approach)Zachman framework caters the paradigm shift for IS development

Vertical Approach

Department-dependentSpan of information departmentally Involve certain groups Can satisfy small groups or individual as it

is it is aligned more closely with a set of users

Own proprietary data, software & technology components

Horizontal Approach

Cut across organizationSpan of information across departments Involves inter-department (intra-

organization)Satisfy many groups as it is it is aligned

with other departments Share data, software & technology

components

Advantages of Zachman’s Approach

Balance the needs between the end user & executives (management)

Defines which components need to integrate with each other and how

Defines the boundaries between components required by end user & executives (management)

Defines the boundaries between the IS (to prevent redundancy)

The Zachman Framework Developed in 1997 in IBM systems

Journal, known as “A Framework for Information Systems Architecture”

Simply referred to as “The Zachman Framework”

Two key things:1. A set of architectural presentation produced

for each participants2. Same product can be described for different

purpose, in different ways

The Zachman Framework (c’td)

Outlines six detailed views/levels for architecture description:

1. The Planner or Ballpark View2. The Owner’s or Enterprise Model View3. The Designer’s or System Model View4. The Builder’s or Technology Model View5. The Subcontractor’s or Detailed

Representation View6. The Functioning Enterprise or Actual System

View

The Zachman Framework (c’td)

Outlines six architecture descriptions for each level:

1. The Data Description – What2. The Function Description – How3. The Network Description –Where4. The People Description – Who5. The Time Description – When6. The Motivation Description - Why