MCD: Good?
Solved
iunanih
Posted messages
4
Status
Member
-
iunanih Posted messages 4 Status Member -
iunanih Posted messages 4 Status Member -
Hello,
I am a beginner in Access and I have to do a big project on it for my courses...
Can you tell me if my DBD seems correct to you?
The idea is to create an app that can manage an airline company, manage customer reservations, flights, and staff...
Thank you in advance ;)
I am a beginner in Access and I have to do a big project on it for my courses...
Can you tell me if my DBD seems correct to you?
The idea is to create an app that can manage an airline company, manage customer reservations, flights, and staff...
Thank you in advance ;)
3 answers
yg_be
Posted messages
23437
Registration date
Status
Contributor
Last intervention
Ambassadeur
1 588
Hello,
I would start by making a list of your assumptions, and a list of the operations that will be performed.
Often, tickets allow you to connect two airports, via one or more flights.
Tickets also have conditions for cancellation, exchange, and refund.
The planes, depending on their model, have a capacity and a seating arrangement.
I would start by making a list of your assumptions, and a list of the operations that will be performed.
Often, tickets allow you to connect two airports, via one or more flights.
Tickets also have conditions for cancellation, exchange, and refund.
The planes, depending on their model, have a capacity and a seating arrangement.
Hello,
In another way, I was going to express the same thing as yg_be. We often see exercises like student grade management, library loan management, ... which are topics that can be confined to a limited number of data. The subject here, if we were to actually implement it, is enormous ;-). Therefore, you need to define the scope of what you will manage. Perhaps in agreement with your teacher?
For example, you will not manage employee payroll, so do not take their salary and bonuses, hiring date into account. If you want to handle seat reservations, there needs to be a whole plan for each type of aircraft. You can likely settle for knowing how many business and economy seats there are for one type of aircraft. What are consumables? Catering (meals, drinks), blankets, kerosene? Forget that.
The fare for a ticket (if we are only managing direct flights ;-) is at a minimum a combination of class and route.
And more factually:
pilot_age: in the database, we do not record the age, but the date of birth like for stewards; by the way, you should at least include the same data in both tables.
the passport number as client key, not great!
you have departure times but no date
--
a stranger is a friend we haven't met yet.
In another way, I was going to express the same thing as yg_be. We often see exercises like student grade management, library loan management, ... which are topics that can be confined to a limited number of data. The subject here, if we were to actually implement it, is enormous ;-). Therefore, you need to define the scope of what you will manage. Perhaps in agreement with your teacher?
For example, you will not manage employee payroll, so do not take their salary and bonuses, hiring date into account. If you want to handle seat reservations, there needs to be a whole plan for each type of aircraft. You can likely settle for knowing how many business and economy seats there are for one type of aircraft. What are consumables? Catering (meals, drinks), blankets, kerosene? Forget that.
The fare for a ticket (if we are only managing direct flights ;-) is at a minimum a combination of class and route.
And more factually:
pilot_age: in the database, we do not record the age, but the date of birth like for stewards; by the way, you should at least include the same data in both tables.
the passport number as client key, not great!
you have departure times but no date
--
a stranger is a friend we haven't met yet.