1. Identify the entities and their relationships. Then create an ERD for the reservations system.
2. Create 3NF table designs for the system.
3. For each of the entities identified, design tables and identify the possible candidate keys, the primary key, a probable foreign key, and potential secondary keys.
4. Use sample data to populate the fields for three records.

Data items must include reservation number, Route Number, Date, Origin, Destinations, Departure Time, Arrival Time, Passenger Name, and Seat Number. For example, Route 97 leaves Monroe, VA, daily at 8:00 a.m. and arrives in Spencer, VA, 100 miles away, at 11:00 a.m. Scenic wants to use an alphabetic reservation code, similar to the codes that airlines use.

SOLUTION

1. A sample ERD follows. Note that the RESERVATION CODE DATA entity might store data about the Reservation Code, Date, Route Number, Passenger Name, and Seat Number. The ROUTE DATA entity might store data about the Route Number, Origin, Destination, Departure Time, and Arrival Time.

2. Sample 3NF table designs follow:
ROUTE DATA (ROUTE NUMBER, ORIGIN, DESTINATION, DEPART TIME, ARRIVE TIME)

RESERVATION DATA (RESERVATION CODE, DATE, ROUTE NUMBER, FLIGHT NUMBER, FLIGHT DATE, PASSENGER NAME, and SEAT NUMBER)

PASSENGER NAME (PASSENGER NUMBER, PASSENGER LAST NAME, PASSENGER FIRST NAME)

3. See the answer to Task 4.

4. The solutions for Tasks 3 and 4 have been combined. The first part of the solution shows the table design and keys that were created in Task 3. The second part of the solution shows the sample data.

ROUTE DATA (ROUTE NUMBER, ORIGIN, DESTINATION, DEPART TIME, ARRIVE TIME)
• Candidate keys: Route Number is the only candidate key. No other field will identify flights uniquely.
• Primary key: Route Number is the primary key.
• Foreign key: This record requires no foreign key.
• Secondary keys: