The Seat table will contain many records for each plane in Dairy Air's fleet. Each record will contain, at the very least, the seat number and seat type.
| Field Name | Key? | Required? | Data Type | Range | Description |
|---|---|---|---|---|---|
| Plane Number | Yes | Yes | Integer | >=1 | The plane that this particular seat is on. |
| Seat Number | Yes | Yes | Integer | >=1 | A unique number assigned to each seat on a plane. |
| Seat Type | No | Yes | Enumerated | {WINDOW, CENTER, AISLE} | The seat's type. |
| Ticket Number | No | No | Integer | >=1 | The ticket that has "bought" that seat. |
Please expand on the reasoning behind the entry "Ticket Number". What is its purpose? Many people may buy tickets on a flight yet not all can have a seat (15% overbooking policy). Seats are not assigned when tickets are purchased, thus this field may be empty for most of the time a flight is in the system.
The table below shows the forms that will access the Seat database, the authorized users of those forms, and the table access level.
| Form Name | Security Group | Access Rights |
| Plane Information | Plane Administration | Read/Add/Modify/Delete |
| Boarding | Booking Agent | Read//Modify |
|
Security Group |
Admin Access |
Read |
Add |
Modify |
Delete |
| System Admin |
X |
X |
X |
X |
X |
| Flight Admin | |||||
| Plane Admin |
X |
X |
X |
X |
X |
|
Booking Agents |
X |
X |