Given the following business rules for the Happy Customer Garage: 1. A customer can own many cars. 2. Some customers do not own cars. 3. A car is owned by one and only one customer. 4. A car may generate one or more maintenance records. 5. Each maintenance record is generated by one and only one car. 6. Some cars have not (yet) generated a maintenance procedure. 7. Each maintenance procedure can use many parts. (Comment: A maintenance procedure may include multiple maintenance actions, each one of which may or may not use parts. For example, 10,000-mile check may include the installation of a new oil filter and a new air filter. But tightening an alternator belt does not require a part.) 8. A part may be used in many maintenance records. (Comment: Each time an oil change is made, an oil filter is used. Therefore, many oil filters may be used during some period of time. Naturally, you are not using the same oil filter each time – but the part classified as “oil filter” shows up in many maintenance records as time passes.) Tasks a. Draw an ER diagram showing the manager’s conceptual view of Happy Customer Garage. (5 marks) b. Using Crow’s Foot notation, transform the ERD into a normalised, logical, (relational) model, resolving any M:N relationships, and showing connectivity and cardinality. Add appropriate attributes to each relation and define primary and foreign keys. (5 marks) c. Summarise your proposed implementation in a simple data dictionary in tabular form, showing all designer-defined objects in the database including indexes on the customer name in the CUSTOMER table and product name in the PRODUCT, a SEQUENCE to generate unique maintenance record numbers starting from 1000, and a TRIGGER that sets a flag when a part’s quantity on hand falls below a designated minimum. The data dictionary should show the data types and any constraints on attributes. (5 marks) d. Provide a SQL script file to define the database…
