Jordan University of Science and Technology

CIS 221 Database Systems Fall 2017

In this project you are to create a simple database system for the Royal Jordanian reservation system. For
such system, you are to work in groups of 3-4 people. If you cannot find a partner and you still want to
work in groups, let us know and we will find you a group.

Getting started
For this project, I recommend that you visit RJ online travel reservation system that can help you get an
idea of what requirements you will have to have in mind before you start.
A competition!
Please try to do your best in this project. Your grades will be determined based on your rank in
accomplishing all the required tasks, discussion, and any extra executed tasks that can support your system,
within the scope of our requirements!
Project description
Below is the description and it is been segmented for your convenience while reading:

- Your design for this reservation system will be a simple base for a more complicated one that might
use interfaces at later stages (at a later course). Your project will be used as a base for airline
mentioned above, but is a simplified one here for the sake of this course.
- We keep track of the ID, type and number of seats (N[seats]) for each aeroplane. The type of the
aeroplane is determined by its name, ID of company that produces it, and the total number of seats.
- Certain aeroplane types can land at certain airports. We should keep track of the airport name, code,
city, county, and country.
- Arranged flights will have to have a description of the RJ airline, its code (consisting of airline
letters + number of flight), and the days of the week during which it operates.
- Each flight will also have a class (economy or business).
- Each flight will have a price (fare) that is distinguished by a code#, total price and any constraints.
Moreover, the flight consists of several segments, from and to the airport. For example, if you are
traveling from Amman to New York/United States, then a flight segment is Amman-Amsterdam,
and Amsterdam-New York.
- The flight will have a scheduled departure and arrival times as well.
- The length of the flight is the combination of the length of its segments (in miles).
 - Each flight will also have its crew members. For each crew member we store their name, ID
(composed of ID of airline and then their ID), and the airline they work for.
- A certain aeroplane is assigned to a segment instance, which is a specific occurrence of a flight
segment on a specific date, while a segment is a non-stop segment of a flight.
- Each segment departs from and arrives at airports at specific departure and arrival times.
- For each flight segment instance we can make reservations of seats based on the customer SSN and
their phone#.
- Each passenger can also be registered to the RJ reward program (earn miles). This reward program
calculates their rewards based on the total number of collected points from previous flights. For the
economic class, for every 5000 miles you get 20 points. You will need 100 points to get a free
ticket that is good for a flight that is 1000 miles long. The business class is 0.25 faster in earning
points for the flight.

Deliverables
- You will be asked to deliver the different components of the system, depending on the phase (as
convenient). Only one member of your group need to submit these deliverables. At the final
deadline, you will have to submit the following:
- Requirements and design documents: You need to make a title page, summary describing how your
design was carried out. Also you need to list the data requirements for such a project. You will also
need to provide what kind of functionality your project is providing and what limitations the current
system has in terms of functionality compared to similar systems
- Conceptual design: ER diagram. Use the (min, max) notation for specifying the cardinality for the
whole diagram
- Logical design: Map your ER diagram to a relational schema.
- Physical database design A description of all tables and attributes in your database. Your physical
database design may closely match your logical design (i.e., your relational schema), or you may
have made fairly significant design changes based on what youve learned since then. Your
relations should be normalized to a degree that makes sense based on your database and intended
applications. For this deliverable, specify all functional dependencies, constraints, keys (primary
and foreign) and normalization issues for your database. More details are given below.
- SQL file (containing sections of command that are needed to do all requirements)
- Insert data into the database (all tables)
- Your queries should be showing all DDL/DML operations that you will learn in this course.
- Team Member Contribution Describe the contributions of each team member to the project.
Include how many hours each team member put into the project! Remember, marks and status
depend on your contribution and accomplishment in the competition.
- Failure to show at the discussion times will get you a ZERO no matter what your solution is!
- Any plagiarism case will be reported to the department to be treated according to the
university code.

Good luck!
 Rubric
Conceptual Design
Entities and their attributes 30
Relationships 30
Cardinality 30
Logical design
Covers all the rules 70
Captures all the logic -5 for every missing component
Physical design
Normalization 30
Constraints -5 for evey missing constraint
Main components of tables -5 for every missing component
SQL
DDL 30
DML 30
Total 250