Reference no: EM131522717

In this assignment you will identify a business situation and design a database for it.

This assignment is to be done in groups of threes (two in a group is also acceptable) Note this is for Internals, Externals have this option also.

Please submit both parts of the assignment together.

Part A: Draw the ER diagram

Identify the business situation that you wish to design a database for. The situation needs to be a real life one (not an imaginary company for example) and ideally be something you are interested in or familiar with. Topics might include hobbies (cricket teams, online games), associations (hockey clubs, childcare centre), work-related concerns (fishing boats, student enrolments, art gallery) or other interests (Star Wars).

Try to pick an application that is relatively substantial, but not too enormous. If you decide to choose your own business situation will need to discuss with your lecturer if it is appropriate.

If you are unable to come up with your own you have the option of choosing from a list of cases. No group can choose the same case, unless there is sufficient difference in the case (Remember it will need to be based on a real practical situation).

For example, when expressed in the ER diagram, you might want your design to have a range of entities (more than 4), and a similar number of relationships.

You should certainly include different kinds of relationships (many-one, many-many) and different kinds of data (Alphanumeric, Numbers, etc.), as well as attribute types.

Please hand in the following:

• Describe the situation. Your description should be brief and relatively informal (maximum length 1 A4 page). If there are any unique or particularly difficult aspects of your proposed application, please point them out. Your description will be marked only on suitability and conciseness
• Include a list of business rules (can make assumptions as long as it is logical)
• Draw an ER diagram for your proposed database. You need to show attributes, primary keys, and relationships (needs to use Chen and Crows feet notation)

Part B: Map the ER diagram to 3NF

• Translate your ER Diagram into a schema of normalised tables. These must be in at least 3rd Normal Form (database schema)

Normalisation - Use a flat structure table include all attributes:

• Determine functional dependencies
• Use 3nf to develop the relations, show as Text notation