INSTITUT

TEKNOLOGI
DEL

TOPIK KHUSUS BIDANG MINAT

SISTEM ENTERPRISE
ENTERPRISE INTEGRATION

“The way a team plays as a whole determines its success. You may have the greatest bunch of individual stars in the world,
but if they don’t play together, the club won’t be worth a dime.” – Babe Ruth (1895-1948), American baseball player.
 INSTITUT
TEKNOLOGI
DEL

Garis Besar
Introduction

Correspondence between Views

Data Integration

Process Integration

Interface Analysis

Human System Interaction

Testing

2
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
INTRODUCTION

3
 INSTITUT
TEKNOLOGI
DEL

Introduction
• Integration of the enterprise is done throughout the
enterprise design process and should always be in the mind of
the design team.
• There are identifiable points in the design life-cycle where
consideration of integration is especially called for:
1. Strategy formulation
2. Enterprise architecture development
3. Requirements analysis
4. Integrate system design
5. View analysis and design
6. Testing and quality assurance
7. Information technology infrastructure

4
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
CORRESPONDENCE BETWEEN VIEWS

5
 INSTITUT
TEKNOLOGI
DEL

Correspondence Between Views

• The enterprise was decomposed into three views of process,
information, and organization.
• To reduce the complexity with dealing with all aspects of the
enterprise at once.
• It is possible that inconsistencies were introduced between
the views.
• To analyze the congruence between the three views we use
matrices that map one view into another view.

6
 INSTITUT
TEKNOLOGI
DEL

Process and Information

• Two versions of the Process-Information Matrix depending on whether the
activities are modeled using a data flow diagram or IDEF0.
• When a data flow diagram (DFD) models the activities, then the matrix is a
CRUD matrix.

FIGURE 17.2
Process-information matrix for data flow diagram.
FIGURE 17.1 7
Correspondence between data flow diagram and entity-relationship diagram.
 INSTITUT
TEKNOLOGI
DEL

Process and Information

• When the activities are modeled using IDEF0, then the Process-
Information matrix shows whether an information object is: I = an input to
the activity, C = a control to the activity, or O = an output of the activity.

FIGURE 17.3
Process-information matrix for IDEF0.

8
 INSTITUT
TEKNOLOGI
DEL

Organization to Information
• The Organization-Information Matrix shows which organization units: O =
own the information object and U = users of the information object.
• The main objective is to understand who the information owners are.

FIGURE 17.4 9
Organization-information matrix.
 INSTITUT
TEKNOLOGI
DEL

Organization to Information
• As an information owner, the organizational unit is
responsible for ensuring that:
• The information is correct and up-to-date.
• The information adheres to enterprise-wide policies on accuracy,
privacy, security, and data storage.
• Part of these responsibilities may be delegated to the IT
department, but it is the business unit that maintains
authority and control.

10
 INSTITUT
TEKNOLOGI
DEL

Process to Organization
• The Process-Organization Matrix shows which organizational units are: A =
authority responsible for an activity, R = a resource for the activity, and C =
concerned party about the execution or outcome of the activity.
• Shows how the organizational design corresponds to the process design.

FIGURE 17.6
Using IDEF0 model to understand process-
organization relationships.
FIGURE 17.5
Process-organization matrix.
11
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
DATA INTEGRATION

12
 INSTITUT
TEKNOLOGI
DEL

Data Integration
• The main challenge in data integration is semantic heterogeneity or the
need to reconcile many different data definitions for the same data entities
and attributes.
• Data integration is accomplished by taking the data structure and data
definitions from the legacy systems, redesigning the structure and data
definitions, and creating it in the new system.
• The conversion process is called extract, transform, and load (ETL).

FIGURE 17.7
Data integration process.
13
 INSTITUT
TEKNOLOGI
DEL

Data Conversion at Cruise Line

• A typical scenario invoking data integration is when one company
merges or acquires another company.
• In order to achieve the efficiencies that mergers promise, the
companies must consolidate and integrate their systems.

FIGURE 17.8 14
Integrating the information models of two cruise lines.
 INSTITUT
TEKNOLOGI
DEL

Data Conversion at Cruise Line

• The data integration issues are:
• Sunny Seas Cruise Line identifies ships by their name, which is unique. The
Ocean Reef Cruise Line has a ShipID. Negotiation among stakeholders
can easily resolve this issue. A likely resolution is to assign ShipIDs to all
the ships.
• The definitions of the primary keys for the cabins/staterooms. Sunny Seas
uses both the CabinNumber and DeckLevel, whereas Ocean Reef uses
just the RoomNumber, which has the deck level as part of the number.
Standardizing on one approach would make sense. However, if they decide
to go with just RoomNumbers, then this would entail replacing all the
room numbers on the ships currently operated by Sunny Seas.
• Sunny Seas has an entity CabinClass and assigned rates based on the
cabin. Ocean Reef has an entity Season and a different policy of charging
rates based on the season. Needs to consider the two business policies and
decide whether to standardize on one policy or create a new policy that
may contain elements of the previous two policies.

15
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
PROCESS INTEGRATION

16
 INSTITUT
TEKNOLOGI
DEL

Process Integration
• Process integration described starts with good process design and also
involves good information architecture, good information design, and good
organization design.
• Start by examining what is required to have the right materials at the right
place and the right time.
• Materials refers to the inputs, controls, and resources of the process.
• If the inputs are physical materials, then this means they are available
when needed in the correct quantity and quality.
TABLE 17.1 Interdependence and Coordination Analysis

17
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
INTERFACE ANALYSIS

18
 INSTITUT
TEKNOLOGI
DEL

Interface Analysis
• The project team needs to identify, define, and document all
interfaces.
• An interface defines the boundary between a system and
everything outside of the system.
• Interfaces can be identified by:
• Examining process inputs and outputs to see where information comes
from and where it goes.
• Examining the data flow diagrams and other models identify
interfaces.
• Examining the organizational to information matrix and where an
organizational unit uses information owned by another unit there may
be a need for an interface.

19
 INSTITUT
TEKNOLOGI
DEL

Interface Analysis
• The interfaces are documented in the Interface List
TABLE 17.2 Interface List

FIGURE 17.9
Context diagram to identify external interfaces.
20
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
HUMAN SYSTEM INTERACTION

21
 INSTITUT
TEKNOLOGI
DEL

Human System Interaction

• Human system interaction is the study of the interface
between humans and systems.
• In an enterprise much of this interaction is with computer
systems, so it is called human-computer interaction (HCI).
• The design issue in HCI is how to allocate tasks between
humans and the systems (or machines) in the enterprise.
• Understanding the relative strengths of humans versus
machines can help in the correct allocation of tasks between
the too.

22
 INSTITUT
TEKNOLOGI
DEL

Human System Interaction

• Humans exceed machine performance in the areas of:
• Value-based decisions.
• Prioritizing things.
• Resource allocations.
• Tasks requiring flexibility and creativity.
• Tasks that interact with other humans.
• Tasks that require adaptive behavior.
• Machines on the other hand exceed human performance in the
following areas:
• Processing large amounts of data.
• Repetitive tasks.
• Following complex algorithms that require no judgment.
• Maintaining system control.

23
 INSTITUT
TEKNOLOGI
DEL

Human System Interaction

• Knowledge of when machines perform better than humans
and vice versa is critical to job design and the human-
computer interface.
• The human-computer interface is part of integrating the
organization with both the process and the information. It also
supports job design directly.

24
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE INTEGRATION
TESTING

25
 INSTITUT
TEKNOLOGI
DEL

Testing
• Enterprise integration is ensured by testing all the systems in
isolation and as an integrated system prior to deployment.
• The types of tests performed are:
• Unit Test – Test each individual component to ensure it is as defect-free as
possible.
• Integration Test – Test functionally grouped subsystems to see they work
together. It occurs between unit and system testing.
• User Acceptance Test – An independent test performed by the end user
prior to accepting the delivered system; i.e., users sign off on test results.
• Interface Test – Test the interfaces in the end-to-end business process.
• System Test – Test the system as a whole.
• Security Test – Test users’ security access provides proper authority for
their roles in the business processes.
• Regression Test – Test that new changes do not adversely impact already
tested components.

26
 INSTITUT
TEKNOLOGI
DEL

Referensi
• R. E. Giachetti, “Design of Enterprise Systems: Theory, Architecture, and Methods,”
CRC Press, 2011.
• W.J. Hopp and M.L. Spearman, “Factory Physics,” Irwin McGraw-Hill, Boston, MA,
1996.
• J. Preece, Y. Rogers, H. Sharp, D. Benyon, S. Holland, and T. Carey, “Human-Computer
Interaction: Concepts and Design,” Pearson Education Ltd, Harlow, England, 1994.
• B. Shneiderman and C. Plaisant, “Designing the User Interface: Strategies for
Effective Human-Computer Interaction,” 4th ed., Addison Wesley, Reading, MA, 2004.
• J.P. Womack and D.T. Jones, “Lean Thinking,” Simon & Schuster, New York, NY, 2003.

27