R
RuiCosta
Hi, I have an assignment, and I don't know where to start with it. My
confusion centres around how many tables I should create, and which ones to
create relationships between. It's an annoyingly written question, any
help/advice for a novice would be diamond. Here is the question.....
A database stores information about flights, customers (who book flights),
and employees (or crew members). Carry out Entity/Relationship modelling for
such a database application where:
- Your data model should separate general flight information (flight number,
route) from instance related information (date/time of flight, crew,
passengers booked).
- Customers are described by: ID, name, and a contact phone number.
- Employees are described by: ID, name, and job title (e.g., pilot,
air-hostess etc.).
Continuing from the E/R model phase – or conceptual modelling - you must
implement a database capable of storing records for the above application.
The airline has just started trading, and as yet, does not have a
record-keeping system. Your task is to design and build a suitable database
for the billing-system.
The system should have 4 main components, these are: products, customers,
invoices and payments.
- The flights details component should have the ability to store date, time,
flight-number, number of passengers and number of crew for each flight.
- The customer component must be able to store a unique customer number,
customer name, phone-number, and credit-card details. Customers may have a
number of distinct credit-cards stored in the system. It is a business rule
of the airline, however that the multiple credit-card details for the same
customer, must all be distinct from each other.
- The Flight summary component must detail a reference to the actual flight
(i.e. where date, time, number of passengers etc. are stored), but must also
store the route. (Route information can just simply be: the destination
City/Airport name.)
- The Crew-Member component must detail the job-title, name, salary and
employee id of all crew-members employed by the airline.
confusion centres around how many tables I should create, and which ones to
create relationships between. It's an annoyingly written question, any
help/advice for a novice would be diamond. Here is the question.....
A database stores information about flights, customers (who book flights),
and employees (or crew members). Carry out Entity/Relationship modelling for
such a database application where:
- Your data model should separate general flight information (flight number,
route) from instance related information (date/time of flight, crew,
passengers booked).
- Customers are described by: ID, name, and a contact phone number.
- Employees are described by: ID, name, and job title (e.g., pilot,
air-hostess etc.).
Continuing from the E/R model phase – or conceptual modelling - you must
implement a database capable of storing records for the above application.
The airline has just started trading, and as yet, does not have a
record-keeping system. Your task is to design and build a suitable database
for the billing-system.
The system should have 4 main components, these are: products, customers,
invoices and payments.
- The flights details component should have the ability to store date, time,
flight-number, number of passengers and number of crew for each flight.
- The customer component must be able to store a unique customer number,
customer name, phone-number, and credit-card details. Customers may have a
number of distinct credit-cards stored in the system. It is a business rule
of the airline, however that the multiple credit-card details for the same
customer, must all be distinct from each other.
- The Flight summary component must detail a reference to the actual flight
(i.e. where date, time, number of passengers etc. are stored), but must also
store the route. (Route information can just simply be: the destination
City/Airport name.)
- The Crew-Member component must detail the job-title, name, salary and
employee id of all crew-members employed by the airline.