Jet Bond 007

018800006882 STANLEY-KEMUEL LLOYD SALVTION
TABLE OF CONTENT
TABLE OF CONTENT ................................................................................................................................ 1

INTRODUCTION ....................................................................................................................................... 3
CURRENT BUSINESS ACTIVITIES AND OPERATIONS ................................................................................ 4
INVENTORY MANAGEMENT: ...................................................................................................... 4
AVAILABILITY DISPLAY AND RESERVATION: ....................................................................... 4
FARE TARIFFS AND TICKETING: ................................................................................................ 5
DOCUMENT AND FARES MANAGEMENT ................................................................................. 5
RESERVATION PROCESSING ....................................................................................................... 5
CUSTOMER MANAGEMENT AND BOOKINGS .......................................................................... 5
TICKETING ....................................................................................................................................... 5
PAYMENT PROCESSING ................................................................................................................ 5
INTERNET BOOKING ENGINE ...................................................................................................... 6
DATA WAREHOUSE AND REPORT ENGINE .............................................................................. 6
BUSINESS RULES...................................................................................................................................... 7
PURPOSE OF JETBOND RESERVATION SYSTEM ...................................................................................... 8
ENTITY, ATTRIBUTES AND RELATIONSHIPS ............................................................................................. 9
IDENTIFICATION OF INITIAL ENTITIES .................................................................................... 9
ENTITIES AND ATTRIBUTES ........................................................................................................ 9
RELATIONSHIPS .............................................................................................................................. 9
NORMALIZATION .................................................................................................................................. 11
NORMAL FORM (UNF) ................................................................................................................. 11
MULTIVALUED ATTRIBUTES: ................................................................................................... 11
NORMAL FORM (INF) ................................................................................................................... 13
PASSENGER ENTITY ....................................................................................................................... 13
FUNCTIONAL DEPENDENCIES ....................................................................................................... 18
NORMAL FORM (3NF) .................................................................................................................. 18
DESIGN SPECIFICATIONS ....................................................................................................................... 23
ENTITY SPECIFICATIONS ........................................................................................................... 23
ATTRIBUTE SPECIFICATION ...................................................................................................... 23
RELATIONSHIP SPECIFICATIONS ............................................................................................. 26
DATA DICTIONARY ................................................................................................................................ 31
DATABASE IMPLEMENTATION .............................................................................................................. 38
DATABASE MANAGEMENT ASSIGNMENT Page 1

CONCLUSION......................................................................................................................................... 49
CRITICAL APPRAISAL ............................................................................................................................. 49
REFERENCES .......................................................................................................................................... 50

INTRODUCTION
JETBOND007 operations began 17th day of the month of September 1975, was founded on
August 21, 1975 by the Robert Kemuel. JETBOON007 airline is a private airline company
with a fixed-base operation in the Nigeria. With a number of 48 different categories of
Airplanes ranging from mini-chartered jets to large Boeing Jets, we provide both private and
commercial services to the public.
JETBOND007 specializes in air for extremely competent and highly competent pilots who
fly across the country of Nigeria; Port Harcourt via Lagos, Abuja, Jos, Benue and back and
lost and lots of flight part even in the continent of West Africa. Amongst Airline Company’s
in the region we can boast of the largest number of Airlines, best maintenance services, best
passenger and airline service which is handle by our integrated database reservation system,
providing user the flexibility of making bookings and reservation from the following avenue;
front desk at the airport, agent or simply at the comfort of our homes or leisure: online
booking and reservation.
JETBOON007 is set out to build its foundation of operations and service excellence to
expand in all aspects from start-up operations which includes: reservations, ticketing,
charges, fees, flight schedule, time plan, etc. to its passengers and the addition of database
system which will keep flight records of individual passenger reservation.
The Customers/ Passengers we commute include large outfitters, resort, lodges, and tourist.
We are proud to announce that JETBOND007 is exclusive supplier of the best flying services
in the country of Nigeria to many hotels, tourist centres, luxury lodges, etc.
JETBOND007 Airline is gradually controlling the market of Nigeria’s local Air flight with its
innovative passion for customer satisfaction and its automated Reservation System built for
business excellence and strategic growth.

CURRENT BUSINESS ACTIVITIES AND OPERATIONS

JETBOND007 Airline Reservation contains the following: Aircraft types, Schedules, Fare,
tariffs, ticket records, passenger list, reservation, etc.
Online Reservation systems are currently used by customers who employ the use of internet
services/ mobile application web services to make reservation. Other means are by Travel
agencies who books customers having privileged access to our database reservation system.
Due to the fact that Airline reservation system is critical to our business success and
application, its functionality is quite complex, we employ the use of an in-house design
database reservation system. The fact that this system is expensive and cumbersome and
processes, stores and produces large amount of data they perform major functions are
categorized as follows:
INVENTORY MANAGEMENT:
JETBOND007 Airline Reservation will present a list of flight with their reservation seats
available for a number of bookings. Our Airline inventory is classified according to the
following groups of services name; First Class, Economy, and Business Class, from which
customers can book from with their varying prices and conditions of application.
Furthermore, the inventory management shall also keep track of seats and other inventories,
single or dual structures, gives pre-defined space templates with posting level for booking
classes and special request control with point based virtual inventory
AVAILABILITY DISPLAY AND RESERVATION:

User or Agencies access our Airline inventory for bookings and reservation through a user
friendly design networked software application. The display contains list of flights services
for a particular destination and seats available in their different booking class. A table of
flight s ran by JETBOND007 which are operated by our Company. Depending on the type of
booking made by users, our database reservation system supports access to the seats
availability in real-time. Reservations of passengers are stored in our central database system.
The database reservation system manages the following operations: storage of customer’s
data; such as names, contact information, or special services request, etc. Also in addition or
database systems holds a list of passengers who checked in on flight schedule and those who
did not check in.

Data from customer’s reservation are also linked to the revenue accounting and reports
department which are integrated into the database for profit and updates.
FARE TARIFFS AND TICKETING:

Fare data are stored also in the database, some taxing information that gives overall prices for
commuting and conditions for minimum stay, etc. are also held in our database system.
JETBOND007 database runs a centralized system where all transactions data related to
flights are stored and can be called up from different distribution Airports around the country
of Nigeria. This database reservation system unlike many has various technological
procedural limitations. Our reservation system is purely 92% electronic with 8% manual
systems for checks and balances.
DOCUMENT AND FARES MANAGEMENT

Management of fares, surcharges, rules and restrictions for public, private and campaign
fares. Flexible display that can be set to show base fare (excluding taxes and airport charges)
or full fare (inclusive all taxes and airport charges).
RESERVATION PROCESSING
Route calculation based on minimum and maximum connecting times and greater circle
distance, real-time fare and surcharge calculation, rule and exemption based tax and airport
charge calculation.
CUSTOMER MANAGEMENT AND BOOKINGS

Passenger names records, bookings and payment histories are stored using our super capable
database.
TICKETING
Inventories are kept on reservation made by customers and upon payment of receipt tickets
are issued by the system containing flight schedule details and other information.
PAYMENT PROCESSING
Debit and credit card processing, invoice account and credit line processing, electronic
voucher, travel cards and corporate bulk document are available on request for payment by
users of the reservation system. Through our partnerships we offer central or local payment
processing and acquiring of debit/credit cards provided for most countries; processing and
collecting of invoice payments can be provided in most countries

INTERNET BOOKING ENGINE

Booking and change booking dialogues, calendar views, traveller accounts and profile access,
booking information and history, payment status, are fully integrated features and content
management system and web statistics tools. JETBOND007 internet booking is closely
integrated with a secured open source website content management system
DATA WAREHOUSE AND REPORT ENGINE

Management information system, operational and financial reporting with standard reports
and possibility to define own reports by incorporating standard and needed data to produce
required information for users of the reservation system.
JETBOND007 Airline Reservation system is designed for adaptation to local markets needs
and to be highly customizable in terms of corporate layout and branding. Our airline
company went online as it saw the need for localized market restructuring as more and more
people are now choosing to fly to their respective destination due to cost effectiveness and
connections between cities via airports. With a dedicated business services to customers
JETBOND007 will see a percentage rise in reservation and ticket booking.

BUSINESS RULES
 All passengers are required to either make booking or reservations before flight
boarding.
 Passengers are required to provide the following information upon booking for a
flight; there name, sex, phone no, e-mail, address, etc.
 A passenger who wishes not to travel at the moment but intending to do so must make
a reservation.
 A passenger who wishes to take a flight must book a ticket and make necessary
payments.
 Each passenger will be able to inquire any available seat.
 Each passenger will be able to reserve a seat for a flight if there is a vacant seat
 If a books wants to reserve a flight less than 7 days before the flight, he/she has to pay
for the air flight ticket which automatically is regarded as booking.
 Those who had bought air tickets are not allowed to cancel or change their bookings.
 For those Passengers who made reservation for flights but did not turn up to pay for
the air tickets before 7 days of the flight, their reservations will be cancelled.
 A Passenger can change his/her reservation provided that the date of his/her
reservation is at least 7 days before the flight.
 A passenger those demand cannot be met will be put in a waiting list.

PURPOSE OF JETBOND RESERVATION SYSTEM

The Airline reservation database will store, process and display information about
JETBOND007 Passenger records, reservation, flight, route, aircrafts, tariffs, etc. who make
reservations for flight plan to buy tickets. This database will also make provisions for data
entry forms for use by the facilitators by accounting department.
The data from the reservation system is for the use by JETBOND007 Airline to keep track of
new customer and old customers who shall make bookings. The system as mentioned earlier
will store, process and display information to users. It shall also be operational on a 24hr
basis to enable users make reservation anytime anywhere they want.
This reservation system is planned for integration with Agencies who seek to make
reservation for tourist, also there shall be provision to make reservation and buy of ticketing
at the front desk of JETBOND007 Airlines. The reason for vast use of distributed database
reservation system is encourage a flexible booking and ticketing system for passengers who
wishes to fly JETBOND.
To further augment the above approaches to flexible customer booking and reservation we
shall see the need for incorporating an online reservation database which shall be the focus of
our future endeavour.

ENTITY, ATTRIBUTES AND RELATIONSHIPS

IDENTIFICATION OF INITIAL ENTITIES
The listed entities below are the initial of the the supposedly to be derived entities of my
Airline Reservation System. These entities include all of the following:
 Entity: Passenger
 Entity: Flight
 Entity: Airport
ENTITIES AND ATTRIBUTES

 Entity: Passenger
Attributes: pass_id, pass_name, sex, DOB, address, phone_no, e_mail, reserve_id,
reserve_date, ticket_id, ticket_date, booking_id, booking_date, class_id, class_type,
payment_id, payment_type, aircraft_type, aircraft_desc, price
 Entity: Flight
Attributes: flight_code, flight_name, Departure_TimeDate, arr_TimeDate,
origin_airport_code, dest_airport_code, flight_schedule_no
 Entity: Airport
Attributes: airport_code, airport_name, airport_location, other_airport_details
RELATIONSHIPS
Three Relations were identified that exist between our entities and they are:
1. Reserves
2. Books
3. Schedules
Below is the representation of the initial E-R Diagram showing the relations identified,
attributes and their respective entities.

Figure 0-1: shows the initial E-R Diagram of JETBOND007

NORMALIZATION
NORMAL FORM (UNF)
PASSENGER
Primary key pass_id
pass_name
Sex
DOB
Address
Phone_no
E_mail
multivalued Reserve_id
multivalued Reserve_date
multivalued Ticket_id
multivalued Ticket_date
multivalued Booking_id
multivalued Booking_date
multivalued Class_id
multivalued Class_type
multivalued Payment_id
multivalued Payment_type
multivalued Aircraft_type
Multivalued Aircraft_desc
multivalued Price
Above is the table showing the PASSENGER Entity and its attributes, we can see that the
pass_id attribute is defined as the primary key. Reason for choosing the pass_id as the
primary key for the PASSENGER entity is because assignment of unique id for each
PASSENGER that makes reservation to the airline system can be made, this will help
guarantee non duplication of values in this Table - PASSENGER. Other values do not
qualify for this because they can have more than 1 value at a time.
MULTIVALUED ATTRIBUTES:
Reserve_id, reserve_date, ticket_id, ticket_date, booking_id, booking_date, class_id,

class_type, payment_id, payment_type, aircraft_type, aircraft_desc, price.
FLIGHT
Primary key Flight_code
Flight_name
Departure_TimeDate
Arr_TimeDate
origin_Airport_code
Dest_Airport_code
Flight_schedules
The table above showing the FLIGHT ENTITY and its attributes has flight_code as its
primary key. The reason for its choosing as primary key is because unique values can be
assigned to it and with an assurance that its values cannot be duplicated.
MULTIVALUED ATTRIBUTES: there are no multivalued attributes in the FLIGHT entity.
AIRPORT
Primary key Airport_code
Airport_name
Airport_location
Airport_details
Above is the table showing the AIRPORT ENTITY and its respective attributes.
Airport_code is been identified as the primary key of the Airport Table. The reason for its
being the primary key is because; unique values can be assigned for each Airport name
identified which will enforce non duplication of data and values.
This section of the Zero Normal Form sees the identification of primary key values for the
three tables identified and subsequent identification of the multivalued attributes that
threatens the formation of a relational database model. Primary keys noted were the
Aiport_code for the Airport Entity, Flight_code for the flight entity and the pass_id for the
Passenger entity.

NORMAL FORM (INF)

In other to make the first Normal form of my Airline reservation system I have to consider
Reservation database in un-normalized form (UNF). Removal of repeating groups identified
in the 1NF also called multivalued attributes and definition of necessary key attributes after
removal will be done in this stage.
Before normalization, lists have a look at the figure 1. Above of the initial entity relationship
diagram (ERD)
PASSENGER ENTITY
Multivalued attributes from the Passenger Entity are: Reserve_id, reserve_date, ticket_id,
ticket_date, booking_id, booking_date, class_id, class_type, payment_id, payment_type,
aircraft_type, aircraft_desc, and price.
These multivalued attributes are intended to store data about customer’s reservation and
booking activity. A customer may book a flight (booking_id) that contains the booking date
(booking_date) which specifies a certain cabin class (class_id) and type (class_type). Upon
booking he makes payment with a unique identifier (payment_id) and chooses a mode of
payment based on the id (payment_type), he can have feel of the type of Aircraft his to
board and its description (Aircraft_type and Aircraft_desc). Furthermore, reservation can
also be made be made for flights ahead of time (reservation_id and time) and its subsequent
flight cost recorded when reservation is made (price).
In other to eliminate these repeating groups an introduction of new relations booking and
reservation as new tables.
In the new “booking” entity, we shall reference the bookings made to the flight by inserting
the flight_code, and pass_id for each customer who made bookings: other attributes such as
ticket_id, ticket_date, booking_id, booking_date, class_id, class_type, payment_id,
payment_type, aircraft_type, aircraft_desc are also added in this break. The primary key
of this new entity will be booking_id.

BOOKING
Primary key Booking_id
Ticket_id
Ticket_date
Booking_date
Class_id
Class_type
Payment_id
Payment_type
Aircraft_type
Aircraft_desc
Foreign key pass_id
Foreign key Flight_code
FUNCTIONAL DEPENDENCIES
Booking_id  book_date Good
Ticket_id, pass_id, flight_code, booking_id  ticket_date, class_id, class_type
Class_id, class_type, Payment_id, payment_type, price.
Aircraft_type , Aircraft_desc Partial Dependency
Class_id  class_type Transitive Dependency
Payment_id  payment_type Transitive Dependency
Aircraft_type  Aircraft_desc Transitive Dependency
RESERVATION
Primary key Reserve_id
Reserve_date
price
Foreign key pass_id
Reserve_id, pass_id, flight_no  reserve_date, price Good

PASSENGER
Primary key pass_id
pass_name
Sex
DOB
Address
Phone_no
E_mail
In the new PASSENGER entity there are no multiple values, which means that there are no
repeating group in this entity, therefore no modification needs to be made in this table entity
to make it in the 1NF.
pass_id  pass_name, sex, DOB, address, phone_no, e_mail Good
FLIGHT
Flight_name
Departure_TimeDate
Arr_TimeDate
origin_Airport_code
Dest_Airport_code
Flight_schedules_no
Flight_code  flight_name, depature_TimeDate, arr_TimeDate,
origin_Airport_code, dest_Airport_code, flight_schedules_no Good
Flight_details  depTime, arrTime Transitive dependency
AIRPORT
Airport_name

Airport_location
Airport_details
Airport_code  airport_name, airport_location, airport_details Good
NORMAL FORM (2NF)

In this step, our relations must be in the 1NF, there shall be the removal of partial
dependencies.
PASSENGER
Primary key pass_id
pass_name
Sex
DOB
Address
Phone_no
E_mail
AIRPORT
Airport_name
Airport_location
Airport_details
FLIGHT

Flight_name
Departure_TimeDate
Arr_TimeDate
origin_Airport_code
Dest_Airport_code
Flight_schedules_no
Flight_code  flight_name, Departure_TimeDate, Arr_TimeDate,
origin_Airport_code, dest_Airport_code, flight_schedules_no Good
Flight_details  Depature_TimeDate, arr_TimeDate Transitive dependency
RESERVATION
Reserve_date
Price
Foreign key pass_id
Foreign key Flight_no
Reserve_id, pass_id, flight_code  reserve_date, price Good
BOOKING
Booking_date
TICKET
Primary key Ticket_id
Ticket_date
Class_id

Class_type
Payment_id
Payment_type
Aircraft_type
Aircraft_desc
Foreign key pass_id
Foreign key Booking_id
Ticket_id, pass_id, flight_code, booking_id  ticket_date, class_id, class_type
Class_id, class_type, Payment_id, payment_type
Aircraft_type , Aircraft_desc Good
Class_id  class_type Transitive Dependency
Payment_id  payment_type Transitive Dependency
Aircraft_type  Aircraft_desc Transitive Dependency
NORMAL FORM (3NF)

In this stage there is the removal of all partial dependencies, but all relations must be in their
2NF.
PASSENGER
Primary key pass_id
pass_name
Sex
DOB
Address
Phone_no
E_mail

AIRPORT
Airport_name
Airport_location
Airport_details
RESERVATION
Reserve_date
price
Foreign key pass_id
Reserve_id, pass_id, flight_code  reserve_date, price Good
BOOKING
Booking_date
TICKET
Primary key Ticket_id
Ticket_date
Class_id
Payment_id
Aircraft_type

Foreign key pass_id

Foreign key Booking_id
Ticket_id, pass_id, flight_code, booking_id  ticket_date, class_id,
payment_id, aircraft_type Good
CLASS
Primary key Class_id
Class_type
Class_id  class_type Good
PAYMENT
Primary key Payment_id
Payment_type
Payment_id  payment_type Good
AIRCRAFT
Primary key Aircraft_type
Aircraft_desc
Aircraft_type  Aircraft_desc Good
FLIGHT
Primary key Flight_no
origin_Airport_code
Dest_Airport_code

Foreign key Flight_schedules_no
Flight_code  flight_name, depature_TimeDate, arr_TimeDate,
origin_Airport_code, dest_Airport_code, flight_schedules_no
Good
FLIGHT_SCHEDULES
Primary key Flight_schedules_no
Departure_TimeDate
Arr_TimeDate
Flight_schedule_no  Departure_TimeDate, Arr_TimeDate Good

Figure 0-1: Final E-R diagram

DESIGN SPECIFICATIONS
ENTITY SPECIFICATIONS
ENTITIES DESCRIPTION
Airport This entity records all airports from which airline operates
Payment This entity gives description of payment types available to users
Passenger This entity records all passengers who have flown with the airline
Ticket This entity records tickets currently allocated to passengers.
Bookings This entity specifies bookings made by all users of the Airline
Flight This entity holds details of all time table flights, times of departure,
destination and service.
Aircraft This entity records each type of aircraft used by JETBOND007
Class This entity describe the different travel class provided in an airplane
Reservation This entity describes reservations made by passengers who intend to take
a flight in the future.
Flight_schedule This entity Flight_schedule gives a vivid description of the Flight no.
ATTRIBUTE SPECIFICATION
Below shows the symbols of the primary key and unique key of attributes
1. The “#” symbols is an unique key (Primary key) attribute

To know what you are talking about, you need to find, for every entity, a value, or
a combination of values, that uniquely identifies the entity instance. This value or
combination is called the unique identifier for the entity.
2. The “*” symbols is an mandatory attribute
It is realistic to assume that for every instance of the entity the attribute value is
known and available when the entity instance is recorded and that is a business
need to record the value.
3. The “°” symbols is an optional attribute

The value of the attribute for an instance of the entity may be unknown or
unavailable when that instance is recorded or the value may be known but is not
that important.
Attributes of “Passenger”
Attributes Type of Key Data type Data size
pass_id # INTEGER 4
Pass_name * VARCHAR 20
Sex * VARCHAR 20
DOB ° DATE/TIME -
Address * VARCHAR 60
Phone_no * VARCHAR 20
E_mail * VARCHAR 50
Attributes of “Airport”
Airport_code # CHAR 4
Air_name * VARCHAR 20
Air_location * VARCHAR 35
Aiport_details °
Attributes of “AirCraft”
Aircraft_type # CHAR 3
Aircraft_desc * VARCHAR 40
Attributes of “Flight”
Flight_code # VARCHAR 5
origin_Airport_code * CHAR 4
dest_Airport_code * CHAR 4
Attributes of “Reservation”

Reserv_id # CHAR 3
Reserv_date * DATE/TIME -
Price ° CURRENCY 10
Attributes of “Booking”
Booking_id # INTEGER 3
Booking_date * DATE/TIME -
Attributes of “Ticket”
Ticket_id # INTEGER 3
Ticket_date ° DATE/TIME -
Class_id ° INTEGER -
Payment_id ° VARCHAR 4
Aircraft_type ° CHAR 3
Attributes of “Payment”
payment_id # VARCHAR 4
Payment_type * CHAR 8
Attributes of “Class”
Class_id # INTEGER 8
Class_type * CHAR 12
Attributes of “Flight_schedule”
Flight_schedules_no # VARCHAR 4
Departure_TimeDate * DATETIME -
Arr_TimeDate * DATETIME -

RELATIONSHIP SPECIFICATIONS
Relationships can be defined as mandatory or optional, in the same way as attributes.
Mandatory, optional and degree of relationships are shown below with special lines. They are
represented below:
Mandatory:
Optional:
The Degree of relationships is shown by the following symbols:
1 to 1 Relationships:
1 to Many Relationships:
Many to Many Relationships:
1 TO 1 (1:1) RELATIONSHIPS
DESCRIPTION:
One ticket must have one cabin class in it.
One class must be in one ticket
DESCRIPTION

One ticket must be used to make one payment
One payment must be used for one ticket
DESCRIPTION
One ticket must specify an aircraft.
At least one aircraft must be specified in 1 ticket.
DESCRIPTION
One flight must have one flight schedule.
One flight schedule must be assigned to one flight.
1 TO MANY (1: M) RELATIONSHIP
DESCRIPTION
One passenger may make 1 or more reservations.
One or more reservations may be made by 1 passenger.

DESCRIPTION
One passenger may make 1 or more bookings.
One or more bookings may be made by 1 passenger.
DESCRIPTION
One ticket may contain one or more bookings.
One or more bookings may be contained in a ticket.
DESCRIPTION
One or more booking may contain one flight detail
One flight detail must be contained in one or bookings.

DESCRIPTION
One or more flight maybe scheduled for one airport
One airport must be schedule to handle one or more flights
MANY TO MANY (M: N) RELATIONSHIP
DESCRIPTION
One or more flight may be placed under reservation
One or more reservations may be made for one or more flight.
DESCRIPTION

One passenger may make one or more reservations
One or more reservations may be made by one passenger
One or more reservations may be placed for one or more flights
One or more flights may be placed under reservation.
DESCRIPTION
One passenger may make one or more bookings.
One or more bookings may be made by one passenger
One more bookings may be for one flight
One flight must have one or more bookings

DATA DICTIONARY
The Data Dictionary defines all attributes used in the database and give realistic meaning to
other programmers
DATA NAME Aircraft_type

DATA DESCRIPTION Defines the types of Aircraft used by the Airline JETBOND007
ALIASES Aircraft Types
DATA TYPE Text
FIELD SIZE 3
DATA VALUES -
USED IN Aircraft Tables, Flight Table
DATA NAME Aircraft_desc

DATA DESCRIPTION Aircraft gives description of the different Aircraft types
ALIASES Aircraft Description
DATA TYPE Text
FIELD SIZE 255
DATA VALUES -
USED IN Aircraft Tables
DATA NAME Aircraft_desc

DATA DESCRIPTION Aircraft gives description of the different Aircraft types
ALIASES Aircraft Description
DATA TYPE Text
FIELD SIZE 255
DATA VALUES -
USED IN Aircraft Tables
DATA NAME Airport_code

DATA DESCRIPTION Airport Code is used as a unique identifier for attributes in the
Airport Relation
ALIASES Airport Unique Code
DATA TYPE Text
FIELD SIZE 4
DATA VALUES -
USED IN Airport Tables,
DATA NAME Airport_name

DATA DESCRIPTION Each code in an Airport has a variable name description to
them. Airport name gives understanding to the code of an

airport
ALIASES Airport Name
DATA TYPE Text
FIELD SIZE 20
DATA VALUES -
USED IN Airport Tables
DATA NAME Airport_location

DATA DESCRIPTION Tells of the various Airport locations for which JETBOND007
operates
ALIASES Airport location
DATA TYPE Text
FIELD SIZE 4
DATA VALUES -
DATA NAME Airport_details

DATA DESCRIPTION Gives details of the airport location and names of the airports
associated with the airline.
ALIASES Airport location
DATA TYPE Memo
FIELD SIZE -
DATA VALUES Alphanumeric
DATA NAME Booking_id

DATA DESCRIPTION A key that uniquely defines attributes of the booking relation
ALIASES Booking identification
DATA TYPE Integer
FIELD SIZE -
DATA VALUES Numbers
USED IN Booking Table
DATA NAME Booking_date

DATA DESCRIPTION Tells of the date a particular booking was made
ALIASES Booking date
DATA TYPE Date/time
FIELD SIZE -
DATA VALUES -
USED IN Booking Table

DATA NAME Class_id

DATA DESCRIPTION This is the primary key attribute of the class relation that
uniquely identifies this entity
ALIASES Class identification number
DATA TYPE Integer
FIELD SIZE -
DATA VALUES Numbers
USED IN Class Table
DATA NAME Class_type

DATA DESCRIPTION This attributes describes the different classes of the Airline
ALIASES Class types
DATA TYPE Integer
FIELD SIZE -
DATA VALUES Numbers
USED IN Class Table
DATA NAME Flight_code

DATA DESCRIPTION This attributes is the primary key of the Flight Table
ALIASES Flight codes
DATA TYPE Text
FIELD SIZE 5
USED IN Flight Table
DATA NAME Origin_airport_code

DATA DESCRIPTION This defines the Airport unique origin identification numbers
used for the different airports.
ALIASES Origin airport code
DATA TYPE Text
FIELD SIZE 4
DATA NAME Dest_airport_code

DATA DESCRIPTION This defines the Airport unique destination identification
numbers used for the different airports.
ALIASES Destination Airport Code
DATA TYPE Text
FIELD SIZE 4

DATA NAME Flight_Schedule_no

DATA DESCRIPTION Foreign key reference and primary keys of the Flight Schedule
Table
ALIASES Flight Schedule Number
DATA TYPE Text
FIELD SIZE 5
USED IN Flight Table, Flight Schedule
DATA NAME Departure_TimeDate

DATA DESCRIPTION Gives the departure time and date for flights
ALIASES Departure Time and Date
DATA TYPE Date/Time
FIELD SIZE -
DATA VALUES -
USED IN Flight Schedule
DATA NAME Arr_TimeDate

DATA DESCRIPTION Gives the time and date for arrival of flights
ALIASES Arrival Time and Date
DATA TYPE Date/Time
FIELD SIZE -
USED IN Flight Schedule
DATA NAME Pass_id

DATA DESCRIPTION Primary key of the Passenger table that uniquely identifies
this entity
ALIASES Passenger identification number
DATA TYPE Integer
FIELD SIZE -
DATA VALUES Number
USED IN Passenger Table, Ticket Table,
DATA NAME Pass_name

DATA DESCRIPTION Gives the description of the
ALIASES Passenger identification number
DATA TYPE Integer

FIELD SIZE -
DATA VALUES Number
USED IN Passenger Table, Ticket Table and Reservation Table
DATA NAME Sex

DATA DESCRIPTION Defines the gender of a particular passenger
ALIASES Gender
DATA TYPE Text
FIELD SIZE 20
USED IN Passenger Table
DATA NAME DOB

DATA DESCRIPTION Records the Date of birth for a particular passenger
ALIASES Date of Birth
DATA TYPE Date/Time
FIELD SIZE -
DATA VALUES -
DATA NAME Address

DATA DESCRIPTION Gives detail description of the passengers address
ALIASES Address
DATA TYPE Text
FIELD SIZE 20
DATA NAME Phone_no

DATA DESCRIPTION Explains explicitly the phone numbers of the individuals
ALIASES Phone number
DATA TYPE Text
FIELD SIZE 20
DATA NAME e_mail

DATA DESCRIPTION Gives the e_mail of the all passengers
ALIASES Electronic Mail
DATA TYPE Text

FIELD SIZE 20
DATA NAME Payment_id

DATA DESCRIPTION Primary key and unique identifier of the payment table
ALIASES Payment identification number
DATA TYPE Text
FIELD SIZE 4
USED IN Payment Table
DATA NAME Payment_type

DATA DESCRIPTION Describes the different payment types
ALIASES Payment Type
DATA TYPE Text
FIELD SIZE 8
USED IN Payment Table
DATA NAME Reserve_id

DATA DESCRIPTION Primary key and unique identification of the Reservation
Table
ALIASES Reservation Identification number
DATA TYPE Text
FIELD SIZE 3
USED IN Reservation Table
DATA NAME Reserve_date

DATA DESCRIPTION Gives the date for reservation made by passengers
ALIASES Reservation Date
DATA TYPE Date/Time
FIELD SIZE -
DATA VALUES -
DATA NAME Price

DATA DESCRIPTION Gives the currency for reservation of flights in future dates
ALIASES Price

DATA TYPE Currency

FIELD SIZE 3
DATA VALUES Numbers
DATA NAME Ticket_id

DATA DESCRIPTION Primary identifier of the Ticket Table
ALIASES Ticket Identification Number
DATA TYPE Text
FIELD SIZE 255
USED IN Ticket Table
DATA NAME Ticket_date

DATA DESCRIPTION Gives the date for ticket paid for by passengers
ALIASES Ticket Date
DATA TYPE Date/Time
FIELD SIZE -
DATA VALUES -
USED IN Ticket Table

DATABASE IMPLEMENTATION
This section provides screen capture of JETBOND007 database using Microsoft Access. The
following tables shall be screen captured showing primary keys and foreign keys.
Aircraft
This Table Shows the different types of Aircraft owned by JETBOND007
Figure 0-1: AIRCRAFT RELATION
Figure 0-2: DESIGN VIEW OF AIRCRAFT TABLE

AIRPORT RELATION
This table shows the different airports operated by JETBOND007 Airlines, in their different
locations.
Figure 0-3: AIRPORT RELATION
Figure 0-4: DESIGN VIEW AIRPORT TABLE

BOOKING RELATION
Gives a list of Booking ID’s, these were made by passengers
Figure 0-5: BOOKING RELATION
Figure 0-6: DESIGN VIEW BOOKING

CLASS RELATION
This relation shows the different class types for which passengers must choose in flight
booking.
Figure 0-7: CLASS RELATION
Figure 0-8: DESIGN VIEW CLASS

FLIGHT RELATION
The flight relation shows a list of available flights for JETBOND007
Figure 0-9: FLIGHT RELATION
Figure 0-10: DESIGN VIEW FLIGHT

FLIGHT SCHEDULE RELATION

The flight schedule table gives a list of schedules available for different flights.
Figure 0-11: FLIGHT SCHEDULE RELATION
Figure 0-12: DESIGN VIEW FLIGHT SCHEDULE

PASSENGER RELATION
This relation gives a record of all passengers who made reservations and bookings.
Figure 0-13: PASSENGER RELATION
Figure 0-14: DESIGN VIEW PASSENGER

PAYMENT RELATION
This relation gives an overview of the different payment methods applicable for flight.
Figure 0-15: PAYMENT RELATION
Figure 0-16: DESIGN VIEW RELATION

RESERVATION RELATION
Reservation relation gives details of reservations made by different passengers.
Figure 0-17: RESERVATION RELATION
Figure 0-18: DESIGN VIEW RESERVATION

TICKET RELATION
Ticket gives necessary details for passenger boarding of flight.
Figure 0-19: TICKET RELATION
Figure 0-20: DESIGN VIEW TICKET

RELATIONSHIP VIEW OF ALL TABLES/ ENTITIES
Figure 0-21: RELATIONSHIP VIEW OF ALL TABLES

CONCLUSION
CRITICAL APPRAISAL
Based on analysis of information critical to business, I was able to generate to an
initial E-R model for JETBOND007. This initial E-R model was able to identify 3 main
entities (Passenger, flight and Airport) and 3 main relations (booking, reservation and
schedule) for Airline Reservation and which are of importance in the development of
JETBOND007s’ database.
Upon conducting of thorough analysis of the initial E-R model developed, the
relations identified in this model were further resolved into more specific entities. The
final E-R model is formed when no more relations can be further broken down. In
other to ensure that the final E-R model is correct and accurate, the entity that
makes up the JETBOND007 database are normalized from the UNF to the 3NF;
breaking a complex table into simple relations. This is an indication that the model
developed is correct.
With this final E-R model, I was able to develop and implement an accurate, effective
database to provide reliable information system to support Airline reservation
operations in the Airline (JETBOND007). With its implementation passengers, staffs
and administrators of the database can speedily and accurately retrieve information
in response to database queries. The newly developed database system will foster a
speedy exchange of information and its overall implementation will definitely
enhance JETBOND007’s Reservation Systems.

REFERENCES
 Date, C.J. "An Introduction to Database Systems Vol 1 Forth edition" , Chapter 17
"Further Normalization" (publ: Addison Wesley 1986)-classic textbook introduction
to normalization
 Kent, W., "A Simple Guide to Five Normal Forms in Relational Database Theory"
Communications of ACM vol 26, no 2 ,Feb 1983- a very pragmatic introductory
paper
 Smith, H., "Database Design: Composing fully normalized tables from a rigorous
dependency diagram," Communications of the ACM vol. 28, no 8, Aug 1985 -
presents decomposition in a diagrammatic manner
 (D. R. Howe's book above also covers normalization)Martin, J., and C. McClure.
"Structured Techniques: The Basis for CASE," Prentice Hall, 1988.
 Ross, R.g. "Entity Modeling: Techniques and Application," Database Research

Group, 1987.
 Sclaer, S., and S. Mellor. "Object Oriented Systems Analysis," Prentice Hall, 1988.
 Weinberg, G.M. WIGGLE Charts a Sketching Tools for Designers,Part VII of

"Rethinking Systems Analysis & Design," Dorset House, 1988.
 Roussopoulos N. and Yeh, R. "An Adaptable Methodology for Database Design"

IEEE Computer , vol. 17, no. 5 May 1984- a good overview on all aspects of DB
design (note ACM above refers to the Association for Computing Machinery, ACM,
11 west 42nd St, New York, 10036).

Jet Bond 007

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Jet Bond 007

Enviado por

Direitos autorais:

Formatos disponíveis

018800006882 STANLEY-KEMUEL LLOYD SALVTION

TABLE OF CONTENT ................................................................................................................................ 1

DATABASE MANAGEMENT ASSIGNMENT Page 1

DATABASE MANAGEMENT ASSIGNMENT Page 2

DATABASE MANAGEMENT ASSIGNMENT Page 3

CURRENT BUSINESS ACTIVITIES AND OPERATIONS

AVAILABILITY DISPLAY AND RESERVATION:

DATABASE MANAGEMENT ASSIGNMENT Page 4

FARE TARIFFS AND TICKETING:

DOCUMENT AND FARES MANAGEMENT

CUSTOMER MANAGEMENT AND BOOKINGS

DATABASE MANAGEMENT ASSIGNMENT Page 5

INTERNET BOOKING ENGINE

DATA WAREHOUSE AND REPORT ENGINE

DATABASE MANAGEMENT ASSIGNMENT Page 6

 A passenger those demand cannot be met will be put in a waiting list.

DATABASE MANAGEMENT ASSIGNMENT Page 7

PURPOSE OF JETBOND RESERVATION SYSTEM

DATABASE MANAGEMENT ASSIGNMENT Page 8

ENTITY, ATTRIBUTES AND RELATIONSHIPS

ENTITIES AND ATTRIBUTES

DATABASE MANAGEMENT ASSIGNMENT Page 9

Figure 0-1: shows the initial E-R Diagram of JETBOND007

DATABASE MANAGEMENT ASSIGNMENT Page 10

DATABASE MANAGEMENT ASSIGNMENT Page 11

class_type, payment_id, payment_type, aircraft_type, aircraft_desc, price.

MULTIVALUED ATTRIBUTES: there are no multivalued attributes in the FLIGHT entity.

DATABASE MANAGEMENT ASSIGNMENT Page 12

NORMAL FORM (INF)

DATABASE MANAGEMENT ASSIGNMENT Page 13

DATABASE MANAGEMENT ASSIGNMENT Page 14

DATABASE MANAGEMENT ASSIGNMENT Page 15

NORMAL FORM (2NF)

DATABASE MANAGEMENT ASSIGNMENT Page 16

DATABASE MANAGEMENT ASSIGNMENT Page 17

NORMAL FORM (3NF)

DATABASE MANAGEMENT ASSIGNMENT Page 18

DATABASE MANAGEMENT ASSIGNMENT Page 19

Foreign key pass_id

DATABASE MANAGEMENT ASSIGNMENT Page 20

Foreign key Flight_schedules_no

DATABASE MANAGEMENT ASSIGNMENT Page 21

Figure 0-1: Final E-R diagram

DATABASE MANAGEMENT ASSIGNMENT Page 22

Payment This entity gives description of payment types available to users

Ticket This entity records tickets currently allocated to passengers.

1. The “#” symbols is an unique key (Primary key) attribute

DATABASE MANAGEMENT ASSIGNMENT Page 23

DATABASE MANAGEMENT ASSIGNMENT Page 24

DATABASE MANAGEMENT ASSIGNMENT Page 25

The Degree of relationships is shown by the following symbols:

Many to Many Relationships:

One ticket must have one cabin class in it.

One class must be in one ticket

DATABASE MANAGEMENT ASSIGNMENT Page 26

One ticket must be used to make one payment

One payment must be used for one ticket

One ticket must specify an aircraft.

At least one aircraft must be specified in 1 ticket.

One flight must have one flight schedule.

One flight schedule must be assigned to one flight.

1 TO MANY (1: M) RELATIONSHIP

One passenger may make 1 or more reservations.

One or more reservations may be made by 1 passenger.