Overview of business case:
A&H Boating is a small start-up company that sells small boats in Geelong. A&H Boating keeps its models in several showrooms across the city. At this stage customers cannot view the available models online so to order they must visit one of the showrooms. A&H Boating has been using an Excel spreadsheet to track their business activities, however, this has caused many redundancies and inefficiency.
With view to their expanding business and under the new management, they decided to investigate the option of implementing a database system. Accordingly, they hired you to design a relational database to better track and record their operational data.
A&B business rules and instructions for creating your ERD:
1. A&H Boating can get boats from several different manufacturers. Each manufacturer produces one or more different types of boats. Each and every type is produced by only one manufacturer. Every manufacturer is identified by a manufacturer code. The company name, street, city, state, postcode, phone number, and account number are kept in the system for every manufacturer. For each type, the type name (i.e. Paddle, Inflatable, Jet Ski, etc.) and purpose (i.e. fishing, day boating, etc.) are kept in the system.
- Create an ERD that represents the entities, attributes, the relationships between entities, and the cardinality and optionality of each relationship that are described by this business rule.
2. Every type has one or more models. Every model is produced as part of a type. For each model, the model number, engine, length, beam, suggested retail price, retail price and dry weight must be kept in the system.
- Add the entities, attributes, relationships between entities, cardinality and optionality of each relationship that are described by this business rule to the ERD that you created for business rule 1.
3. Each type’s models are stored in a specific warehouse. Each warehouse stores the models of only one type. Each warehouse is identified by a warehouse ID. For each warehouse address, postcode, phone number are kept in the system.
- Add the entities, attributes, relationships between entities, cardinality and optionality of each relationship that are described by this business rule to the ERD that you created for business rule 1 and business rule 2.
4. Each warehouse can be visited by prospective customers with prior booking. Customers can book a visit to a specific warehouse by calling A&H Boating hotline. Customers need to provide full name, date of birth, address, email address and contact number during booking a visit to a warehouse.
- Add the entities, attributes, relationships between entities, cardinality and optionality of each relationship that are described by this business rule to the ERD that you created for business rule 1, 2 and 3.
Rationale
This assessment item is designed to test your understanding of the following learning outcomes:
• Basic database design and modelling concepts,
• Identification and interpretation of business rules,
• Creation of an Entity Relationship Diagram from a set of business rules,
• Application of correct relationships, cardinalities, optionality using the Crows Foot modelling notation.
Task Marks Score
Task1 5
Task2 5
Task 3 5
Task4 5
Total
20
Rationale
This assessment aligns with the following subject outcomes:
- be able to gather, analyse and model business requirements using Enhanced Entity Relationship Diagrams (EERD);
Marking criteriaThe marking criteria for this assignment is:Comprehensive and accurate ERD that contains all entities, PK and FK, attributes, associative entities included if required, all relationships shown and identified with correct cardinality and optionality
TASKS |
HD |
DI |
CR |
PS |
FL |
|---|
TASK 1,2,3,4 |
Comprehensive and accurate ERD that contains all entities, PK and FK, attributes, associative entities included if required, all relationships shown and identified with correct cardinality and optionality |
Detailed and accurate ERD that contains all entities, PK and FK, attributes, associative entities included if required, all relationships shown and identified with correct cardinality and optionality |
Thorough and reasonably accurate ERD that contains all entities, PK and FK, attributes, associative entities included if required, all relationships shown and identified with correct cardinality and optionality |
Adequate ERD that contains most entities, PK and FK, attributes, associative entities included if required, all relationships shown with cardinality |
Incomplete or irrelevant ERD that contains some entities, relationships, and cardinality |
Presentation
Use https://www.draw.io to create your ERD
Requirements
Either save your ERD diagram as a PDF or embed it in a Word document.
Don't use any other file formats
Don't submit your file in XML
Please include your student ID, name and subject code in the diagram