Reference no: EM133668544
Database Design and Development
Assignment
Objectives
To develop a conceptual data model diagram
To perform logical design (optional)
Assignment Specification
In this assignment, you need to perform the following tasks for the given case study:
Draw an Entity Relationship (ER) diagram.
Create relational notation for 3 entities that you have identified.
Case Study
CQ Parcels Corporation (CQPC) is well known for its parcel handling business in Australia. They provide delivery services to Small-to-medium businesses (SMB) across Australia.
Customers of CQPC can request for parcels to be collected from the business locations on specific dates / times and then are delivered to the destinations as specified delivery addresses in Australia.
A new customer (sender of parcels) registers their product enquiry (a lead in CRM language) with CQPC via the website/call-centre. The First and last name, contact phone, email, date of birth are among the details of the customer that are considered to be vital. Once these details are available a sales employee at CQPC is assigned the lead. The sales employee will create a contract for the customer. Contracts can be of two types: Standard contract or Non-standard contracts. All contracts will have a ContractID, date of contract, term of contract, total value of contract (in AUD) among other fields. Standard contracts are based on fixed pricing at CQPC. There are no discounts, but the cost is lesser than sending parcels over the counter at the CQPC outlet. Non-Standard contracts are for large customers like Amazon that might send many parcels per year. These customers get better rates and high discount percentages.
Whenever a customer requests a parcel delivery, the parcel-delivery information such as the delivery address and receiver details are collected. The customer (sender of the parcel) is also recorded against the delivery.
Subsequently, one of CQPC employees collects the parcel from the sender, verifies whether the address for delivery is mentioned on the parcel, and then creates an invoice for the charges related to its delivery. Invoices are usually paid monthly. They are expected to be paid in full. Invoices usually details the amount payable and the due date of payment among other important detail.
For each parcel-delivery, CQPC also maintains the details of the delivery employee involved, the date and time of collection/pick-up and delivery. CQPC prides itself on redelivering parcels (maximum of 2 times) in case the customer was not available the first time.
However, if parcels cannot be delivered because it was lost in transit or were damaged, then the customer can lodge a compensation claim to CQPC. The compensation claims are verified and provided as a discount on the invoice by CQPC if they are responsible for the loss.
Assignment Requirements
In this assignment, you need to create an Entity Relationship (ER) diagram relevant to the above case study and provide the relational notation for any 3 entities that you have identified.
The attributes for various entities have not been purposely described in the case study so that the students are encouraged to further research and list the pertinent attributes in addition to the required identifier for each entity in their ERD.
Draw an appropriate ER diagram.
Use the symbols as prescribed in your unit-textbook to draw the ER diagram (ERD) for the above case study.
Your ERD must
show all necessary entities, attributes and relationships.
show identifiers/identifying attributes as necessary.
show multi-valued attributes, if any
show participation and cardinality.
show associative entities, if appropriate
show weak entities, if any
use the notation described in the set text or as taught during the tutorials.
use consistent and appropriate naming for entities and attributes as specified in the unit text book
Some business rules or other aspects of the case study may not be clear to you when you read the case study. If this is the case, then you should either approach your lecturer or tutor for clarification, or you may simply assume and then develop your ERD accordingly. For example, the case study might not mention all relevant participation information (also called minimum cardinalities). If so, you may assume about what the minimum cardinalities might reasonably be, and then show them in your ERD accordingly. You should justify
each assumption in terms of the business, for example: it is assumed that each customer must have at least one order because it is assumed that the business does not record customer details until the customer makes an order with them. To get yourself started, ask yourself, 'If I were running this business, what things I need to keep a list of?' Write those things down. For each thing, what information would you need to record about it? How can it be identified? The answers to these questions will help you to develop your ERD.
Assumptions and Business rules
Provide assumptions and business rules relevant to your ERD.
Create Relational Notation / Logical Design for any 3 entities
You can map your Entity Relationship diagram (ERD) into relations and make sure that all the relations are in 3NF. Provide all the relations in the following format:
Customer (CustomerId, CustomerName, Street, Suburb, State, PostCode, Email)
Invoice (InvoiceNumber, InvoiceDate, Total, CustomerId)
foreign key (CustomerId) references Customer(CustomerId)