Consider the following set of requirements for a Flight reservation database: We conduct numerous flights departing from and arriving at various airports. We maintain a record of airport codes and addresses. Here is our requirements: Each airline schedules many flights. A flight may be shared among multiple airlines, and therefore the flights can be scheduled by many airlines. When multiple airlines share the same flights, each flight can be scheduled by many airlines. The passenger capacity of each flight varies depending on the aircraft's size and can accommodate up to 220 passengers. We collect and store essential information such as the passenger's ID, name, credit card, and mileage plan number. To account for fluctuating prices, we must save the total cost at the time of booking as prices are subject to change. Every booking must be assigned to precisely one flight and be associated with at least one passenger. A newly introduced flight does not have any existing bookings. Note: The definition of passenger requires that all passengers hold a booking. Note: Passengers and travelers are used interchangeably and refer to the same existence Draw an ER diagram for this application. Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete. Create a conceptual data model corresponding to the scenario above and represent that using Entity-Relationship Diagram (ERD) . Document any assumptions you make or constraints you will enforce, and include this documentation in your final submission for this assignment. All entities and relationships must be included and named. All entities must have key attribute. All attributes of all entities must be included and named. Cardinalities of all relationships must be indicated on the ERD diagram.
Consider the following set of requirements for a Flight reservation
We conduct numerous flights departing from and arriving at various airports. We maintain a record of airport codes and addresses. Here is our requirements:
- Each airline schedules many flights.
- A flight may be shared among multiple airlines, and therefore the flights can be scheduled by many airlines.
- When multiple airlines share the same flights, each flight can be scheduled by many airlines.
- The passenger capacity of each flight varies depending on the aircraft's size and can accommodate up to 220 passengers.
- We collect and store essential information such as the passenger's ID, name, credit card, and mileage plan number.
- To account for fluctuating prices, we must save the total cost at the time of booking as prices are subject to change.
- Every booking must be assigned to precisely one flight and be associated with at least one passenger.
- A newly introduced flight does not have any existing bookings.
Note: The definition of passenger requires that all passengers hold a booking.
Note: Passengers and travelers are used interchangeably and refer to the same existence
Draw an ER diagram for this application.
Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete.
Create a conceptual data model corresponding to the scenario above and represent that using Entity-Relationship Diagram (ERD) .
- Document any assumptions you make or constraints you will enforce, and include this documentation in your final submission for this assignment.
- All entities and relationships must be included and named.
- All entities must have key attribute.
- All attributes of all entities must be included and named.
- Cardinalities of all relationships must be indicated on the ERD diagram.
Trending now
This is a popular solution!
Step by step
Solved in 4 steps with 2 images