`Ticket` table

Overview

The Ticket database will contain information on all passengers who have not yet flown their flights with Dairy Air.

Fields

Field Name	Key?	Required?	Data Type	Range	Description
Ticket Number	Yes	Yes	Integer	>= 1	A unique, system-assigned number for every ticket.
Flight Number	No	No	Integer	>= 1	The specific flight number the passenger is booked on.
Departure Date	No	Yes	Date	Julian Calendar Date	The date the passenger's flight departs.
Original Cost	No	Yes	Currency	> 0	How much the flight costs.
First Name	No	Yes	String	Alphabetic	The passenger's first name.
Last Name	No	Yes	String	Alphabetic	The passenger's last name.
Phone	No	Yes	String	(xxx) xxx-xxxx	The passenger's phone number.
Address	No	Yes	String	Alphanumeric	The passenger's address.
Number of Times Delayed	No	No	Integer	>= 0	The number of times the passenger was delayed due to overbooking.
Ticket Insurance?	No	Yes	Boolean	{True, False}	Was insurance purchased or not?
Method of Payment	No	Yes	Enumerated	{Cash, Cheque, Credit Card}	Method of payment used for ticket purchase (space will be provided for credit card number and expiry date).
Date Purchased	No	Yes	Date	Julian Calendar Date	The date on which the ticket was purchased
Time Purchased	No	Yes	Time	24-hour clock	The time at which the ticket was purchased

Back to index of Changes

Dairy Air comments and questions are in blue emphasis

The term "Number of Times Delayed" could be renamed "Number of Times Overbooked" as a flight can be delayed (in terms of time) confusing the issue.

Primary Key

Ticket Number

Relationships

"Source" Relationships

Every record in the Ticket database will be linked to one record in the Flight database. (Every ticket must be on a given flight)
Every record in the Ticket database may be linked to one record in the Seat database. (One ticket may occupy one seat)

"Destination" Relationships

Every record in the Flight database may be linked to at least one record in the Ticket database. (Every flight may have a ticket for it)
Every record in the Seat database may be linked to one record in the Ticket database. (Any seat may have a ticket "occupying" it)

Accessor Forms

The table below shows the forms that will access the Ticket database, the authorized users of those forms, and the table access level.

Form Name	Security Group	Access Rights
Edit Flight	Flight Schedulers	Read/Add/Modify/Delete
Book a Ticket	Booking Agent	Read/Add
Edit a Ticket	Booking Agent	Read/Add/Modify/Delete

Security Setting:

Security Group	Admin Access	Read	Add	Modify	Delete
System Admin	X	X	X	X	X
Flight Admin		X	X	X	X
Plane Admin
Booking Agents	X	X	X	X	X

Ticket table