INSTITUT

TEKNOLOGI
DEL

TOPIK KHUSUS BIDANG MINAT

SISTEM ENTERPRISE
INFORMATION DESIGN

“Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge
we have lost in information?” – T.S. Eliot (1888-1965) poet.
 INSTITUT
TEKNOLOGI
DEL

Garis Besar
Method To Build Entity-Relationship Model

Relational Database

Normalization

Data Dictionary

Deliverables

2
 INSTITUT
TEKNOLOGI
DEL

INFORMATION DESIGN
METHOD TO BUILD ENTITY-RELATIONSHIP MODEL

3
 INSTITUT
TEKNOLOGI
DEL

Method To Build Entity-Relationship Model

• The entity-relationship model can be developed in two
stages with three steps in each stage.

Build the Business Model

• Information modeling project initiation

• Entity definition
• Relationship definition

Build the Database Design Model

• Primary key definition

• Resolve many-to-many relationships
• Non-key attribute definition

4
 INSTITUT
TEKNOLOGI
DEL

1.1. Information Modeling Project Initiation

• Model conventions should be discussed and agreed upon.
• i.e. naming conventions (is it StudentID, StudentNum, or
StudentNumber), spelling agreements (is it Dept or Department),
or notation agreements (Employee ID or EmployeeID).
• Devise a strategy for source data collection.
• Source materials include all existing forms, reports, manuals,
instructions, Web pages, and other documentation that exists in
the enterprise.
• Additionally, interviews should be conducted to determine what
are the entities, relationships, and attributes that are needed in
the model.
• The source data materials should be collected, and then they
should be logged into a Source Materials Log.

5
 INSTITUT
TEKNOLOGI
DEL

1.1. Information Modeling Project Initiation

Table 1. Source Material Log
Number Name and Description Source Comments
Purchase order – form sent to purchasing
1 Paper form
department
Paper book (25
2 Telephone book
pages)
May be out-of-
3 Organization chart Paper document
date

Table 2. Source Data List

Source Material
Number Name Data Properties Comments
Data
14-digit alphanumeric
111 Purchase order 1 Document name
character
Purchase order
112 1, 22, 35 5-digit number Tracks PO, is unique
number
Vendor 10-digit alphanumeric Unique identity of
113 1, 22, 15
number character vendor
6
 INSTITUT
TEKNOLOGI
DEL

1.2. Entity Definition

Table 3. Entity Identification
Entity
Description
Type
An entity can describe a person in the system such as student, employee,
Person
customer, guest, patient, doctor, spouse, child, or pet.
An entity can describe any geographical location in the system such as a
Place
classroom, building, state, sales zone, store, or country.
An entity can describe any event in the system such as arrival, trip,
Event
departure, award, or meeting.
An entity can describe a physical real object in the system such as part,
Object
inventory, movie, product, tool, or machine.
An entity can describe a transaction the system processes such as a
Transaction
reservation, sale, contract, purchase order, deposit, or withdrawal.
An entity can describe a concept in the system that does not have a
physical manifestation such as a class, semester, procedure, account,
Concept
block of
time, or work assignment.
An entity can describe a group of people such as a department, team,
Group
division, supplier, or company.
7
 INSTITUT
TEKNOLOGI
DEL

1.2. Entity Definition

Table 3. Example of Entity Pool
Entity # Entity Name Entity Definition Source Comments
A document authorizing the purchase of
E1 Purchase Order 2
goods
E2 Carrier A vendor who provides delivery service 2, 3
The organization unit that employees are
E4 Department 2, 3, 5
assigned to
A document that requests payment for
E5 Invoice 3
services from a client

• The entity pool is used to document the candidate entities that were
identified.
• When analyzing the entity pool, the following rules need to apply:
• Each entity must have a unique name.
• An entity must have a primary key (entity integrity rule).

8
 INSTITUT
TEKNOLOGI
DEL

1.3. Relationship Definition

• Goal : to have only parent-child relationships in the model.
• Steps:
• Determine whether two entities are related (i.e., create Entity-
Relationship Matrix)
• Specify the relationship with the cardinality and a relationship phrase
• The completion of this phase results in the business model

FIGURE 1
Business model. 9
 INSTITUT
TEKNOLOGI
DEL

2.1. Primary Key Definition

• The primary key is defined for each entity.
• Sometimes it is possible to identify naturally
occurring attributes that have the properties of a
primary key.
• One practice is for the system to generate an
internally, unique primary key for each instance.

10
 INSTITUT
TEKNOLOGI
DEL

2.2. Resolve Many-to-Many Relationships

• It is possible that some many-to-many relationships were
defined in the business model.
• The final information model does not allow these non-specific
relationships.
• To resolve a many-to-many relationship, we usually add an
associative entity such that the associate entity replaces the
many-to-many relationship between the entities.

FIGURE 2
Resolving a many-to-many relationship.
11
 INSTITUT
TEKNOLOGI
DEL

Review: Database Rules

• Two database rules help maintain a good database
design.
• The entity integrity rule says that all primary key entries
are unique, and no part of the primary key can be null.
• The referential integrity rule says that the foreign key’s
values are required to match those of the primary key or
be completely null.
• These two rules are important to the implementation
and operation of a database.

12
 INSTITUT
TEKNOLOGI
DEL

2.3. Non-Key Attribute Definition

• The focus of the information design is identifying the
entities, their relationships, and the primary keys.
• Once this crucial aspect is completed, then you add all the
non-key attributes.
• The data attributes are assigned to the entity that they
most belong to.
• The information model should not have redundant non-
key attributes, each piece of data should appear in only
one entity in the entire model.
• For each attribute, you need to define the data type and
domain.

13
 INSTITUT
TEKNOLOGI
DEL

INFORMATION DESIGN
RELATIONAL DATABASE

14
 INSTITUT
TEKNOLOGI
DEL

Relational Database
• The entity-relationship model can be implemented in
a relational database management system (DBMS).
• The DBMS is a large record storage system that
maintains all the data in a system.
• The DBMS allows a user to store, read, update, and
delete data in the system without having to know
how the data are physically stored or organized
Information Model Term Database Term
Entity Table
Attribute Field
Entity instance Record
15
 INSTITUT
TEKNOLOGI
DEL

Relational Database: SQL

• CRUD describes the four main operations that are done
on a database.
• CRUD is implemented in SQL using the SQL Insert, Select,
Update, and Delete commands.
• SQL Insert
• SQL uses the Insert command to enter new data into a table.
• SQL Select
• To read data from the database SQL uses the Select command.
• SQL Update
• If a data record already exists in the table, then to change any of the
attributes the SQL Update command is used.
• SQL Delete
• To delete an existing record or records from the database, the SQL
Delete command is used.

16
 INSTITUT
TEKNOLOGI
DEL

INFORMATION DESIGN
NORMALIZATION

17
 INSTITUT
TEKNOLOGI
DEL

Normalization
• Normalization is the process of recognizing undesirable properties
in the information model and converting them into a more desirable
form.
• Normalization does two things:
• Removes data redundancy by having any piece of data appear in only one
entity.
• Ensures data dependencies make sense. By doing this, normalization leads
to a data structure that will avoid insertion, update, and deletion
anomalies

18
 INSTITUT
TEKNOLOGI
DEL

Normalization
• Normalization occurs through a series of stages,
called normal forms, such that each successive stage
builds on the previous stage.
• To be in second normal form, a data model must first
be in first normal form.
• Normalization is applied to the entities in the data
model; all entities must adhere to the normal form to
be declared in that normal form.

19
 INSTITUT
TEKNOLOGI
DEL

INFORMATION DESIGN
DATA DICTIONARY

20
 INSTITUT
TEKNOLOGI
DEL

Data Dictionary
• A data dictionary is a centralized repository of
information about data such as data type, meaning,
relationships to other data, origin, usage, and format
of each attribute.

FIGURE 3
Partial Data Dictionary.

21
 INSTITUT
TEKNOLOGI
DEL

INFORMATION DESIGN
DELIVERABLES

22
 INSTITUT
TEKNOLOGI
DEL

Deliverables
• The final output of information modeling is a
database definition model. It includes the:
• Final entity-relationship model, called a Database
Definition Model.
• The Source Material Log.
• The Source Material List.
• The entity pool.
• The attribute pool.
• The Data Dictionary.

FIGURE 4
23
Database Design Model.
 INSTITUT
TEKNOLOGI
DEL

Referensi
• R. E. Giachetti, “Design of Enterprise Systems: Theory,
Architecture, and Methods,” CRC Press, 2011.

24