TUGAS 1 INDIVIDU

MANAJEMEN DATA DAN INFORMASI

DOSEN PENGAMPU
Prof. Dr. Ir. Arif Djunaidy, M.Sc

DISUSUN OLEH
Rachmad Abdullah

INSTITUT TEKNOLOGI SEPULUH NOPEMBER

FAKULTAS BISNIS DAN MANAJEMEN TEKNOLOGI
MAGISTER MANAJEMEN TEKNOLOGI
2018/2019
 TUGAS 1 Man Data & Informasi

1. Consider the following set of requirements for a UNIVERSITY database that is

used to keep track of students' transcripts.
a. The university keeps track of each student's name, student number, social
security number, current address and phone, permanent address and phone,
birth date, sex, class (freshman, sophomore, ..., graduate), major department,
minor department (if any), and degree program (B.A., B.S., ..., Ph.D.). Some
user applications need to refer to the city, state, and zip of the student's
permanent address, and to the student's last name. Both social security number
and student number have unique values for each student.
b. Each department is described by a name, department code, office number,
office phone, and college. Both name and code have unique values for each
department.
c. Each course has a course name, description, course number, number of
semester hours, level, and offering department. The value of course number is
unique for each course.
d. Each section has an instructor, semester, year, course, and section number. The
section number distinguishes different sections of the same course that are
taught during the same semester/year; its values are 1, 2, 3, ..., up to the number
of sections taught during each semester.
e. A grade report has a student, section, letter grade, and numeric grade (0, 1, 2,
3, or 4).

Design an ER schema for this application, and draw an ER diagram for that schema.
Specify key attributes of each entity type and structural constraints on each
relationship type. Note any unspecified requirements, and make appropriate
assumptions to make the specification complete.

Assumptions:
 Every department must have at least one student enrolled in it as a major
 A student must specify his major when he/she joins the university
 Not all departments are used as a minor department for a student’s degree
 Every department must offer at least one course
 Every course must belong to exactly one department
 Not all courses will have sections (a course may be new and will not be offered
until next year, or there is no instructor available to teach the course)
 A section may not have any students enrolled in it
 A student may not sign up for any classes (section) (for example, the student
dropped that semester for medical reasons

1
 TUGAS 1 Man Data & Informasi

2
 TUGAS 1 Man Data & Informasi

2. Consider the ER diagram below, which shows a simplified schema for an airline
reservations system. 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.

3
 TUGAS 1 Man Data & Informasi

Answer:
(1) The database represents each AIRPORT, keeping its unique AirportCode, the
AIRPORT Name, and the City and State in which the AIRPORT is located.
(2) Each airline FLIGHT has a unique number, the Airline for the FLIGHT, and
the Weekdays on which the FLIGHT is scheduled (for example, every day of the
week except Sunday can be coded as X7).
(3) A FLIGHT is composed of one or more FLIGHT LEGs (for example, flight
numberCO1223 from New York to Los Angeles may have two FLIGHT LEGs: leg
1 from New York to Houston and leg 2 from Houston to Los Angeles). Each
FLIGHT LEG has a DEPARTURE AIRPORT and Scheduled Departure Time, and
an ARRIVAL AIRPORT and Scheduled Arrival Time.
(4) A LEG INSTANCE is an instance of a FLIGHT LEG on a specific Date (for
example, CO1223 leg 1 on July 30, 1989). The actual Departure and Arrival
AIRPORTs andTimes are recorded for each flight leg after the flight leg has been
concluded. TheNumber of available seats and the AIRPLANE used in the LEG
INSTANCE are also kept.
(5) The customer RESERVATIONs on each LEG INSTANCE include the
Customer Name, Phone, and Seat Number(s) for each reservation.
(6) Information on AIRPLANEs and AIRPLANE TYPEs are also kept. For each
AIRPLANETYPE (for example, DC-10), the TypeName, manufacturing
Company, and Maximum Number of Seats are kept. The AIRPORTs in which
planes of this typeCAN LAND are kept in the database. For each AIRPLANE, the
AirplaneId, Total number of seats, and TYPE are kept.

4
 TUGAS 1 Man Data & Informasi

3. Design a database to keep track of information for an art museum. Assume that the
following requirements were collected:
a. The museum has a collection of ART_OBJECTS. Each ART_OBJECT has a
unique Id_no, an Artist (if known), a Year (when it was created, if known), a
Title, and a Description. The art objects are categorized in several ways, as
discussed below.
b. ART_OBJECTS are categorized based on their type. There are three main
types: PAINTING, SCULPTURE, and STATUE, plus another type called
OTHER to accommodate objects that do not fall into one of the three main
types.
c. A PAINTING has a Paint_type (oil, watercolor, etc.), material on which it is
Drawn_on (paper, canvas, wood, etc.), and Style (modern, abstract, etc.).
d. A SCULPTURE or a statue has a Material from which it was created (wood,
stone, etc.), Height,Weight, and Style.
e. An art object in the OTHER category has a Type (print, photo, etc.) and Style
f. ART_OBJECTs are categorized as either PERMANENT_COLLECTION
(objects that are owned by the museum) and BORROWED. Information
captured about objects in the PERMANENT_COLLECTION includes
Date_acquired, Status (on display, on loan, or stored), and Cost. Information
captured about BORROWED objects includes the Collection from which it was
borrowed, Date_borrowed, and Date_returned.
g. Information describing the country or culture of Origin (Italian, Egyptian,
American, Indian, and so forth) and Epoch (Renaissance, Modern, Ancient, and
so forth) is captured for each ART_OBJECT.
h. The museum keeps track of ARTIST information, if known: Name, DateBorn
(if known), Date_died (if not living), Country_of_origin, Epoch, Main_style,
and Description. The Name is assumed to be unique.
i. Different EXHIBITIONS occur, each having a Name, Start_date, and
End_date. EXHIBITIONS are related to all the art objects that were on display
during the exhibition.
j. Information is kept on other COLLECTIONS with which the museum interacts,
including Name (unique), Type (museum, personal, etc.), Description, Address,
Phone, and current Contact_person.

5
 TUGAS 1 Man Data & Informasi