One Way Exit (OWE transport) is a start-up bus transportation business aimed at the local market of
Fantastic news! We've Found the answer you've been seeking!
Question:
"One Way Exit" (OWE transport) is a start-up bus transportation business aimed at the local market of travellers (local travellers wanting a one-way ticket out of town!). OWE transport needs a database to track Buses, customers, fares, bus performance, and staff assignment. Since OWE transport is promoted as "...the fastest way out of town!" individual seats are not assigned. More specific notes about OWE transport are listed below:
- Information about a route includes its unique number, its origin, its destination, and estimated departure and arrival times. To reduce costs, OWE transport only has non-stop bus rides (Journeys) with a single origin and destination.
- Journeys are timetabled for a route on one or more dates with a Bus and a Staff assigned to each journey, and the available seats (remaining capacity i.e., seats not taken) noted. In a staff assignment, the staff ID and the role (position) are noted. It is a business requirement that the number of hours that journey staff (i.e., driver, assistant-driver, bus attendant) are on a journey must be recorded. There is no such requirement for non-journey staff (e.g., route supervisor, admin officers, mechanics etc..).
- Busses have a unique registration number, a made, model, year, a capacity, and a scheduled-service date.
- The service record of a buss includes a unique service number, a date, a description, the registration number of the bus, and the staff (mechanic) responsible for the maintenance/repairs.
- Staff have a unique staff ID, a full name (First and Last name), a contact phone, and a job role.
- Customers have a unique customer ID, a contact phone, and a name (it does not have to be their real name).
- A record is maintained of journey bookings including a unique booking ID, a journey number, a customer number, a date, a fare, and the payment method (can be cash, cheque, crypto currency, or credit card). If the payment is by credit card, a credit card number and an expiration date are part of the booking record.
QUESTION TO WORK ON:
- Create an entity-relationship diagram showing the data requirements of the system. Your ERD should be able to be implemented in a relational DBMS. You should use the ERD notation we have been using in the lectures, and should include a legend to explain the notation. You should include attributes in the ERD. The use of a drawing tool such as Visio will make this task easier. However, whichever tool you use, you must copy and paste the ERD into a word-processed document. This is because your tutor might not have access to the tools you have used. Please note that hand-drawn ERDs are not acceptable.
- List and explain any assumptions you have made in creating the data model.
- Follow the best practices taught in this unit! Refer to the lecture slides and learning materials.
- You must make use of the Crow"s foot Database Notation
Some important things to note:
- Marks will be allocated to each of the following functional areas:
- Legend---- Make sure to add legends
- Entities
- Have you included all required entities in the design?
- Have you included specialisation hierarchies where appropriate?
- Relationships
Related Book For
Managerial accounting
ISBN: 978-0471467854
1st edition
Authors: ramji balakrishnan, k. s i varamakrishnan, Geoffrey b. sprin
Posted Date: