1. Part A — Entity-Relationship Diagrams

(50 marks) (50 marks)

Draw an Entity-Relationship Diagram (ERD) for the data storage requirements described in the case study below.

The case study will contain conflicting, ambiguous, vague, and missing information. Seek clarification and/or make reasonable assumptions to complete the requirements: your assumptions and clarifications need to support all details of the ERD that are not already provided by the case study. Document any assumptions you make and clarifications you obtain in an appendix named‘Assumptions and Clarifications’. There are two options:

•  Seek clarification about the case study by searching the forums. If your question has not already been discussed, please post your question.
•  Make reasonable assumptions about missing or ambiguous information in the case study. However, marks may be lost for unreasonable assumptions. For example, it is unreasonable to assume that people only ever drive around with one passenger in their car.Notes:
  • Your ERDs should be neat, clear and easy to read.
  • Please follow the modelling standard used in the text book and lecture slides.The Case StudyWe are creating a web service/app that is a rideshare service to chauffeur kids to events such as school or extra-curricular activities. You will need to record information about the cars, the drivers, the kids and the trips that they make. When one person decides to drive somebody else’s kids, they both need to give permission, and these permissions need to be recorded. Please specify the data storage requirements.

COIT11237 – Assignment 2 Specifications Page: 1.

(50 marks)

How You Are Marked for the Entity-Relationship Diagram (ERD)

You need to ensure you pay attention to the following aspects when developing your ERD:

• Correct entities are identified
• Correct unique identifiers
• Appropriate attributes for each entity
• Appropriate notation
• Correct relationships and cardinalities (min/ max cardinalities)
• Assumptions/ clarifications support all details provided in the ERD

(6 marks) (6 marks) (8 marks) (10 marks) (10 marks) (10 marks)

COIT11237 – Assignment 2 Specifications

Page: 2.

Part B — Data Model Transformation (50 marks)

Implement the ER model you developed in Part A as a relational database design.
1. Transform your ER model into a relational database design. (25 marks)

Note: Document the tables in your design using the Relation Notation shown below.Customer(CID, Name, Street, Suburb, State, PostCode, DiscountPercent, Email)

SalesOrder(SOID, CID, Number, FullPrice, Discount, FinalPrice, TotalPaid, Status) foreign key (CID) references Customer(CID)

Provide a brief explanation about cascades for each foreign key.

How You Are Marked for the relational database design

Please pay attention to the following aspects when developing your ERD:

• Correct tables and primary keys
• Correct foreign keys
• Correct cascades
• Documentation of cascades

2. Implement enough of the database to demonstrate the following. You do not need to implement the entire database.

1. primary key constraints: provide five examples
2. foreign key constraints: provide five examples
3. cascading delete: provide one example
4. validation rule with a validation text: provide one example
5. table constraint (a constraint that compares more than one column): provide oneexample. You will need to check the SQL Server Compatibility (ANSI 92) for yourdatabase before you write an SQL alter table query. (5 marks)

You need to include a brief documentation (in a word document) that highlights where the above items are demonstrated in your database, e.g. where the primary key constraints are. Marks may be lost if your documentation is missing, unclear or not concise.

How and what to submit

Submit your assignment on the unit web site. Please submit two files:

1. A Microsoft Word document containing:
   • Your Entity Relationship Diagram (ERD) for Part A
   • Your reasonable assumptions/points of clarification for Part A (if you have any)
   • Documentation for Part B.
2. A Microsoft Access file containing the tables and features you have implemented to support the requirements for Part B.