Modelling
Overview of business case:
Alive & Boating (A&B) is a small start-up company that sells small boats in Wagga. A&B 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&B 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&B 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, A&B retail price and dry weight must be kept in the system.
• Add the entities, attributes, the relationships between entities, and the cardinality and optionality of each relationship that are described by this business rule to the same copy of 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, the relationships between entities, and the cardinality and optionality of each relationship that are described by this business rule to the same copy of the ERD that you created for business rule 1 and business rule 2.
Tool: MySQL
NOTE
Use Flow Chart Maker & Online Diagram Software (https://www.draw.io) to create your ERD
Use Crows Foot notations
Any M:N relationship is to be resolved to a 1:M relationship
Manually drawing the ERD is NOT acceptable.
Rationale
This assessment item is designed to test your understanding of basic database design and modelling concepts, and your ability to interpret business rules into an Entity Relationship Diagram.
Additionally, your ability to apply correct relationships, cardinalities, optionalities, and the use of Crows Foot modelling notations are tested.
Marking criteria
The marking criteria for this assignment are:
Task HD DI CR PS
Create an ERD that represents the entities, attributes, the relationships between entities, and the cardinality and optionality of each relationship that are described by the three business rules The ERD accurately identifies and correctly shows all entities, PKs, attributes, relationships, associative entities (if applicable), cardinalities and optionalities The ERD accurately identifies and correctly shows all entities, PKs, attributes, relationships, and associative entities (if applicable) but some of the cardinalities and optionalities are incorrect The ERD accurately identifies and correctly shows most entities, PKs, attributes, but some of the relationships, associative entities (if applicable), cardinalities and optionalities are incorrect The ERD identifies and shows some entities, PKs, attributes, but most of the relationships, cardinalities and optionalities are incorrect