Perancangan Sistem

Informasi Logistik dan

Basis Data
ILI-3F3

Program Studi Teknik Logistik

Fakultas Rekayasa Industri
Telkom University
 SDLC-PHASE
Planning

Analysis

Maintenance

Design
Database
• Form and Reports dialogues and interfaces finalizing design
specifications Distributed and Internet System

Implementation

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 DATABASE DESIGN
File and database design occurs in two steps.

1. Develop a logical database model, which describes data using notation that
corresponds to a data organization used by a database management system.
• Relational database model

2. Prescribe the technical specifications for computer files and databases in which to store
the data.
• Physical database design provides specifications
Logical and physical database design in parallel with other system design steps

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Database Design Process
• Enterprise-wide data model(E-R with only
entities)
• Conceptual data mode(E-R with only entities
for specific project) Planning • Logical Conceptual data
models (E-R with
attributes)

Analysis

Maintenance

• Data model evolution

Design • Logical data model (relational) and
physical file and database design (file
organization)

Implementation
• Database and file definitions (DBMS
specific code)

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Database Design Process
Four key steps in logical database modeling and design:

1. Develop a logical data model for each known user interface for the application using
normalization principles.

2. Combine normalized data requirements from all user interfaces into one consolidated logical
database model (view integration).

3. Translate the conceptual E-R data model for the application into normalized data
requirements.

4. Compare the consolidated logical database design with the translated E-R model and produce one
final logical database model for the application.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Physical Database Design

Key Physical database design decision include

• Choosing a storage format for each attribute from the logical database model.
• Grouping attributes from the logical database model into physical records.

• Arranging related records in secondary memory (hard disks and magnetic tapes) so that
records can be stored, retrieved and updated rapidly.

• Selecting media and structures for storing data to make access more efficient.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Deliverables and Outcomes
Logical database design
• Must account for every data element on a system input or output
• Normalized relations are the primary deliverable.

Physical database design

• Converts relations into database tables
• Programmers and database analysts code the definitions of the database.
• Written in Structured Query Language (SQL)

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 ● Relational database model: data represented as a set of
related tables or relations

● Relation: a named, two-dimensional table of data; each

relation consists of a set of named columns and an
arbitrary number of unnamed rows

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Relations

Relations have several properties that distinguish them from nonrelational tables:
• Entries in cells are simple.
• Entries in columns are from the same set of values.
• Each row is unique.

• The sequence of columns can be interchanged without changing the meaning or use of the relation.
• The rows may be interchanged or stored in any sequence.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Well-Structured Relation and
Primary Keys
• Well-Structured Relation (or table)
• A relation that contains a minimum amount of redundancy
• Allows users to insert, modify, and delete the rows without errors or inconsistencies

• Primary Key
• An attribute whose value is unique across all occurrences of a relation

• All relations have a primary key.

• This is how rows are ensured to be unique.
• A primary key may involve a single attribute or be composed of multiple attributes.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Relations

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Relations Notations

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Binary 1:N and 1:1Relationships

The procedure for representing relationships depends on both

the degree of the relationship—unary, binary, ternary—and the
cardinalities of the relationship.

Binary 1:N Relationship is represented by adding the primary

key attribute (or attributes) of the entity on the one side of the
relationship as a foreign key in the relation that is on the many
side of the relationship

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Binary and Higher-Degree M:N Relationships

Create another relation and include primary keys of all

relations as primary key of new relation

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Unary Relationships
• Unary 1:N Relationship
• Is modeled as a relation

• Primary key of that relation is the same as for the

entity type

• Foreign key is added to the relation that references the

primary key values

• Recursive foreign key: a foreign key in a relation that references the

primary key values of that same relation

• Unary M:N Relationship

• Model as one relation, then Create a separate relation to represent the
M:N relationship.

• The primary key of the new relation is a composite key of two attributes
that both take their values from the same primary key Any attribute
associated with the relationship is included as a nonkey attribute in this
new relation.
ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data
Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Physical File and Database Design
• The following information is required:
• Normalized relations, including volume estimates
• Definitions of each attribute

• Descriptions of where and when data are used, entered, retrieved, deleted, and updated
(including frequencies)
• Expectations or requirements for response time and data integrity
• Descriptions of the technologies used for implementing the files and database

• Field: the smallest unit of named application data recognized by system software
• Attributes from relations will be represented as fields

• Data Type: a coding scheme recognized by system software for representing

organizational data

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Choosing Data Types
• Selecting a data type balances four objectives:

• Minimize storage space.

• Represent all possible values of the field.

• Improve data integrity of the field.

• Support all data manipulations desired on the

field.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Example: ERD for Sales

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 The ERD

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 CLASS DIAGRAM-UML

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Learning Objectives
Concisely define each of the following key data
modeling terms: object, state, behavior, object class,
Draw a class diagram to represent common business

01 class diagram, operation, encapsulation, association

role, abstract class, polymorphism, aggregation, and
02 situations.

composition.

Explain the unique capabilities of class diagrams

03 compared with E-R diagrams for modeling data.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Objects and Classes
• Object: an entity with a well-defined role in an application domain; has state, behavior, and identity
characteristics

• State: encompasses an object’s properties (attributes and relationships) and the values of those
properties

• Behavior: represents how an object acts and reacts

• Identity: uniqueness—no two objects are the same

• Object class (class): a logical grouping of objects that have the same (or similar) attributes,
relationships, and behaviors (methods)

• Class diagram: a diagram that shows the static structure of object classes, their internal structure, and the
relationships in which they participate

• UML classes are analogous to E-R entities.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Objects and Classes

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Objects and Classes

Operation Encapsulation
a function or a service that is provided by all the
the technique of hiding the internal implementation
instances of a class to invoke behavior in an object by
details of an object from its external view
passing a message

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Type of Operations

Constructor Query
01 an operation that creates a new instance 03 an operation that accesses the state of an
of a class object but does not alter the state

Update Operation Class Scope Operation

02 an operation that alters the state of an 04 an operation that applies to a class rather
object than an object instance

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Associations
• Association: a relationship among instances of object
classes

• Association role: the name given to the end of an association where it

connects to a class

• Multiplicity: indicates how many objects participate in a given

relationship:

• 0..10 means minimum of 0 and maximum

of 10
• 1, 2 means can be either 1 or 2
* means any number

• UML associations are analogous to E-R relationships and UML

multiplicities are analogous to E-R cardinalities.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Associative Classes

• Associative class: an
association that has attributes
or operations of its own or
that participates in

relationships with other classes

• UML association classes are

analogous to E-R associative entities.

• Generalization and
inheritance are implemented
via superclass/subclasses in

UML and via supertypes/subtypes in E-R.

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Stereotypes for Attributes

UML keywords:
Overlapping: a descendant may be descended from more than one of the subclasses
Disjoint: a descendant may not be descended from more than one of the subclasses
Complete: all subclasses have been specified
Incomplete: some subclasses have been specified, but the list is known to be incomplete

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Representing Generalization

• Abstract class: a class that has no

direct instances but whose descendants
may have direct instances

• Concrete class: a class that can have

direct instances

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 An Example of
Conceptual Data
Modeling at
Hoosier Burger

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Example: Class Diagram for Sales
Operations

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 Example: Class Diagram for Sales
Operations

ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data

Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University
 TERIMA
KASIH
ILI-3F3 | Perancangan Sistem Informasi Logistik dan Basis Data
Program Studi Teknik Logistik | Fakultas Rekayasa Industri | Telkom University