This document provides instructions for an ER modeling assignment. Students are asked to model the ER diagrams for 4 different databases using the Dia free software tool: 1) a CONFERENCE_REVIEW database, 2) a MAIL_ORDER database, 3) a MOVIE database, and 4) extract the requirements and constraints from an example ER diagram for a TRANSPORT_SHIP database. For each database, they are provided data dictionaries describing the relevant entities and attributes.

1. Tugas Group Project 2
ER Modeling
Disusun oleh :
Arief Sandi Destianto 6026221003
Dosen Pengampu :
Prof. Ir. Arif Djunaidy, M.Sc., Ph.D
NIP 19581005 198603 1 003
DEPARTEMEN SISTEM INFORMASI
FAKULTAS TEKNOLOGI ELEKTRO DAN INFORMATIKA CERDAS
INSTITUT TEKNOLOGI SEPULUH NOPEMBER
SURABAYA
2022

2. Anda diminta untuk membuat ERD menggunakan pemodelan ER yang dibahas dalam
kuliah. Anda diharuskan menggunakan tool Dia free software (dapat diunduh di http://dia-
installer.de/download/index.html.en) untuk menggambarkan ERD. Dalam Dia free sfotware,
pilih menu “Other sheets > ER” dalam Dia free software. Anda HARUS menggunakan
software tersebut, dan penggunaan software lainnya TIDAK akan dinilai.
Gunakan notasi basic ER Modeling dan gunakan sepenuhnya notasi yang tersedia dalam Dia
free sfoware. Untuk menggambarkan relationship participation constraint, gunakan general
cardinality (1:N, N:1, atau M:N) dan penggunaan garis penghubung garis tunggal (partial
particiaption) dan garis ganda (total participation).
1. Consider a CONFERENCE_REVIEW database in which researchers submittheir
research papers for consideration. Reviews by reviewers are recorded for use in the
paper selection process. The database system caters primarily to reviewers who record
answers to evaluation questions for each paper they review and make
recommendations regarding whether to accept or reject the paper. Using the data
requirements summarized below, design an ERD for the CONFERENCE_REVIEW.
a. Authors of papers are uniquely identified by e-mail id. Authors of papers are
uniquely identified by e-mail id. First and last names are also recorded.
b. Each paper is assigned a unique identifier by the system and is described by a
title, abstract, and the name of the electronic file containing thepaper.
c. A paper may have multiple authors, but one of the authors is designated as the
contact author.
d. Reviewers of papers are uniquely identified by e-mail address. Each
reviewer’s first name, last name, phone number, affiliation, and topics of
interest are also recorded.
e. Each paper is assigned between two and four reviewers. A reviewer rates each
paper assigned to him or her on a scale of 1 to 10 in four categories: technical
merit, readability, originality, and relevance to the conference. Finally, each
reviewer provides an overall recommendation regarding each paper.
f. Each review contains two types of written comments: one to be seen by the
review committee only and the other as feedback to the author(s).
2. Consider a MAIL_ORDER database in which employees take orders for parts from
customers. The data requirements are summarized as follows:
a. The mail order company has employees, each identified by a uniqueemployee
number, first and last name, and Zip Code.
b. Each customer of the company is identified by a unique customer number,
first and last name, and Zip Code.

3. c. Each part sold by the company is identified by a unique part number, a part
name, price, and quantity in stock.
d. Each order placed by a customer is taken by an employee and is given a
unique order number. Each order contains specified quantities of one or more
parts. Each order has a date of receipt as well as an expected ship date. The
actual ship date is also recorded.
Design an Entity-Relationship diagram for the mail order database
3. Consider a MOVIE database in which data is recorded about the movie industry. The
data requirements are summarized as follows:
a. Each movie is identified by title and year of release. Each movie has a length
in minutes. Each has a production company, and each is classified under one
or more genres (such as horror, action, drama, and so forth). Each movie has
one or more directors and one or more actors appear in it. Each movie also has
a plot outline. Finally, each movie has zero or more quotable quotes, each of
which is spoken by a particular actor appearing in the movie.
b. Actors are identified by name and date of birth and appear in one or more
movies. Each actor has a role in the movie.
c. Directors are also identified by name and date of birth and direct one or more
movies. It is possible for a director to act in a movie (including one that he or
she may also direct).
d. Production companies are identified by name and each has an address. A
production company produces one or more movies.
Design an Entity-Relationship diagram for the movie database
4. Consider the ER diagram below, which shows an ER schema for a database that can
be used to keep track of transport ships and their locations for maritime authorities.
Extract from the ER diagram the requirements and constraints that produced this
schema. Try to be as precise as possible in your requirements and constraints
specification; i.e. if the requirements and cosntraints are modeled, the same ER
diagram will be generated as shown in this problem.

4. 1. CONFERENCE_REVIEW
a. DATA DICTIONARY
NO ENTITY ATRIBUT
1 AUTHOR EMAIL_ID [PK]
AUTHOR_NAME
(FIRST_NAME,LAST_NAME)
2 PAPER PAPER_ID [PK]
PAPER_TITLE
ABSTRACT
E_FILE
3 REVIEWER EMAIL_REVIEWER [PK]
REVIEWER_NAME
(FIRST_NAME,LAST_NAME)
TOPIC
AFFILIATION
PHONE
4 REVIEW (Weak Entity) EMAIL_REVIEWER [FK]
PAPER_ID [FK]
SCALE_CATEGORIES
(TECHNICAL_MERIT,
READABILITY, ORIGINALITY,
RELEVANCE)
RECOMMENDATION
COMMENT
b. ER MODELING

5. 2. MAIL_ORDER
a. DATA DICTIONARY
NO ENTITY ATRIBUT
1 EMPLOYEES EMPLOYEE_ID [PK]
EMPLOYEE_NAME
(FIRST_NAME, LAST_NAME)
ZIP_CODE
2 CUSTOMER CUSTOMER_ID [PK]
CUSTOMER_NAME
(FIRST_NAME, LAST_NAME)
ZIP_CODE
3 PART PART_ID [PK]
PART_NAME
PRICE
STOCK
4 ORDER ORDER_ID [PK]
EMPLOYEE_ID [FK]
CUSTOMER_ID [FK]
QUANTITY
DATE_RECEIPT
EXPECTED_SHIP
ACTUAL_SHIP
b. ER MODELING

6. 3. MOVIE
a. DATA DICTIONARY
NO ENTITY ATRIBUT
1 MOVIE MOVIE_ID [PK]
MOVIE_NAME
RELEASE
DURATION
PLOT
2 ACTOR ACTOR_ID [PK]
ACTOR_NAME
BIRTH_DATE
3 DIRECTOR DIRECTOR_ID [PK]
DIRECTOR_NAME
BIRTH_DATE
4. PRODUCT_COMPANIES COMPANIES_ID [PK]
COMPANIES_NAME
ADDRESS
b. ER MODELING

7. 4. TRANSPORT_SHIP
Skema ER database yang digunakan untuk melacak kapal pengangkut dan
lokasinya untuk otoritas maritim. Persyaratan data dan constraint diringkas sebagai
berikut:
a. Setiap kapal dapat diidentifikasi berasarkan nama kapal (Sname), dan pemilik
kapal (owner). Setiap kapal hanya memiliki 1 tipe, dan 1 tipe dapat dimiliki
oleh kapal berbeda. Setiap kapal dapat di klasifikasikan berdasarkan tipe kapal
(type) yang berisikan kode unik, kapasitas kapal (tonnage), dan besar lambung
yang dimiliki olek tipe kapal tersebut (hull). Kapal dapat melakukan
perjalanan maupun tidak. Untuk setiap kapal yang sedang melakukan
perjalanan (ship_movement) akan dilacak keberadaanya. Dari pelacakan
perjalanan kapal tersebut, hal-hal yang akan dicatat terdiri dari: informasi
waktu (time_stamp) yang berisikan tanggal (date) dan waktu (time), garis
bujur (longitude), dan garis lintang (latitude).
b. Setiap kapal bisa jadi tidak memiliki pelabuhan (port) atau hanya memiliki 1
pelabuhan (port) sebagai tempat berlabuh (home_port) dan memungkinkan
kapal memiliki tempat singgah (ship_at_port) lebih dari 1 pelabuhan (port)
maupun tidak sama sekali.
c. Di setiap kapal yang akan berlabuh, terdapat catatan ekspedisi untuk setiap
tujuan pelabuhan (port_visit) berupa tanggal dimulainya perjalanan
(start_date) dan kapan perjalanan tersebut berakhir (end_date).

8. d. Pelabuhan (port) sebagai tempat berlabuh (home port) sekaligus tempat
singgah (ship_at_port) memungkinkan untuk menampung lebih dari 1 kapal
maupun tidak sama sekali. Pelabuhan (port) memiliki preposisi lokasi dalam
lingkup atau batasan tertentu (in) yang akan dicatat dinegara mana pelabuhan
tersebut berada (state/country). Negara pelabuhan diidentifikasi dengan Nama
negara (name) dan benua (continent). Pelabuhan juga memiliki preposisi yang
lebih spesifik (on) yang akan dicatat keberadaan dilaut/samudra mana
pelabuhan tersebut berada (sea/ocean/lake) dengan identifikiasi nama
laut/samudra (name).