Академический Документы
Профессиональный Документы
Культура Документы
Draw an Entity Relationship Diagram (ER Model) for the given case study along with
proper associations and cardinalities.
Task#2:
Derive the tables from the ER model and normalize up to third normal form (3rd NF)
Task#3:
De-normalize the database (obtained after completing task#2) by using the collapsing
tables technique.
Case Study
Air-Ticket Reservation System
Section 1: Introduction
1.1
Vision Statement:
1.1.1
Software Purpose
The main purpose of this software is to reduce the manual errors involved in the airline
reservation process and make it convenient for the airline staff to perform their daily
reservation related tasks e.g. tickets reservation, flight scheduling, announcements etc. in
automated way.
1.1.2
Software Scope
This software provides options for passengers to view and search different flights along
with their timings and reservation details for a particular date.
For administrators (staff members), it will facilitate them to manage the route schedules
(adding, editing, canceling and viewing routes), reservations (booking, modifying,
canceling and viewing) and staff.
1.1.3
Software Perspective
Passenger
interface
Air Ticket
Reservation
System
Admin
Passenger
Database
Administrator
Interface
User characteristics
2.2
Operating environment
ARS will be a client/server based system, running on LAN. Both clients and servers will
be Linux based systems.
Entire application along with database will be installed on the central server.
Administrators and passengers will be able to perform the intended functionality through
GUI interfaces provided on individual machines.
Separate Terminal computers (3 to 4) will be provided to passengers, where they will be
able to see and search flight schedules, available seats and announcements etc. A printer
will also be installed with theses terminals so that passengers could print details of flight
(and seats) they selected.
2.3
External Interfaces
The application will also need to connect to local airport services database system to get
the current status of the runway and other notifications etc. The super admins will use this
information to reserve the runway for them and to schedule their flights. Application will
connect with this database system through provided interface.
The system also needs to connect to an international weather forecasting service to get
weather forecasting details. This information will also be used for flight scheduling.
2.4
It is assumed that passengers will first see the flight schedules and fare details from the
passenger terminal computers (dedicated only for the passengers). After selecting a
particular flight and seat, they will get print of it and will go to reservation booth, where
sub admin staff member will reserve ticket for them by seeing the printed specification.
Also, any breaking news e.g. modification of flight timing etc. will be immediately added
to the system by admins, and will immediately be visible through passenger interface.
Task#1:
Draw an Entity Relationship Diagram (ER Model) for the given case study along with
proper associations and cardinalities.
Task#2:
Derive the tables from the ER model and normalize up to third normal form (3rd NF)
Task#3:
De-normalize the database (obtained after completing task#2) by using the collapsing
tables technique.
Task#1:
Draw an Entity Relationship Diagram (ER Model) for the given case study along with
proper associations and cardinalities.
Task#2:
Derive the tables from the ER model and normalize up to third normal form (3rd NF)
Tables
Jets
JetID
JetName
JetType
Number
Text
Text
Primary Key
Flights
FlightID
FlightDate
FlightJetID
FlightSource
FlighDestination
FlightTime
RunWayID
ReservedBy
Number
Date
Number
Text
Text
Text
Number
Number
Primary Key
Foreign Key (Refers JetID in Table Jets)
Passengers
PassengerID
Number
PassengerName Text
PassengerCell
Text
Primary Key
Staff
StaffMemberID
StaffMemberName
StaffMemberDesignation
StaffMemberContact
Number
Text
Text
Text
Primary Key
Tickets
TicketID
TicketType
PassengerID
FlightType
Number
Text
Number
Number
Primary Key
Foreign Key (Refers FlightID in Table Flights)
Announcements
AnnouncementID
AnnouncementText
AnnouncementStartDate
AnnouncementExpDate
Number
Text
Date
Date
Primary Key
StaffMemberID
Number
Runway
RunwayID
Number
RunwayTrack
Text
TowerAssigned Number
Primary Key
Task#3:
De-normalize the database (obtained after completing task#2) by using the collapsing
tables technique.
De-normalize
Table collapsing: table collapsing de-normalization technique is used on one-to-one and
many-to-many relations. In ER model given in task-1 we do not have man-to-many
relations, however, one-to-one relations were identified between Tickets, Passengers
entities and Runway, Flights and Jets entities.
First we collapse the Passengers and Tickets tables. We suppose that PassengerCell
attribute is unnecessary so finally the resultant Tickets table after collapsing becomes:
Tickets
TicketID
TicketType
PassengerID
PassengerName
FlightID
Number
Text
Number
String
Number
Primary Key
Flights
FlightID
FlightDate
FlightJetID
FlightSource
FlighDestination
FlightTime
RunWayID
RunwayTrack
ReservedBy
Number
Date
Number
Text
Text
Text
Number
String
Number
Primary Key
Foreign Key (Refers JetID in Table Jets)
Then we merge Jets Table with Flights. The final structure of Flights table
becomes:
Flights
FlightID
FlightDate
Number
Date
Primary Key
FlightJetID
JetName
JetType
FlightSource
FlighDestination
FlightTime
RunWayID
RunwayTrack
ReservedBy
Number
String
String
Text
Text
Text
Number
String
Number
Note:
i need to show the database resulted from the previous first task (after denormalization)
and the resultant database after performing pre-join denormalization in this task.