Reference no: EM133038886

Objectives

- To develop a conceptual data model diagram
- To perform logical design (optional)

Case Study - CQ Specialty Centre

Assignment Specification

In this assignment, you need to perform the following tasks for the given case study:

1. Draw an Entity Relationship (ER) diagram
2. Perform logical design (optional)
3. Create 3NF Relations (optional)

Please note that the above-mentioned optional components, logical design and 3NF relations, will not be marked, however these tasks are expected to enrich your skills in the creation of databases in future.

Assignment Requirements

In this assignment, you need to create an Entity Relationship (ER) diagram relevant to the above case study and optionally perform logical design to produce appropriate 3NF Relations.

A. 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

1. show all necessary entities, attributes and relationships
2. show identifiers/identifying attributes as necessary
3. show multi-valued attributes (if any)
4. show participation and cardinality
5. show associative entities (if appropriate)
6. show weak entities (if any)
7. use the notation described in the unit textbook
8. use consistent and appropriate naming for entities and attributes as specified in the unit textbook.

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 make an assumption 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 make an assumption 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 a surgeon might not have any lease so far, because it is assumed that the business records potential surgeons' details for future leases. 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.

B. Data dictionary

Provide the details of attributes for all the entities. You can use a suitable tabular format to provide these details. The details must include the following properties of attributes wherever appropriate:

1. name
2. size/length
3. minimum and maximum value and/or permitted value
4. required/not required for a new instance
5. brief notes that are relevant.

C. Assumptions and Business rules

Provide assumptions and business rules that are relevant to your ERD.

D. Create Logical Design (Optional):

If you would like to perform this optional component of this assignment, 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)

What to submit:

You should submit a Microsoft Word document containing:

1. A copy of your ERD.
2. Data dictionary
3. A list of business rules and assumptions including their justifications.
4. 3NF Relations (optional).

Attachment:- Perform logical design.rar