Reference no: EM132972947

ITD105 Database Management

Project overview

The ITD105 project gives you an opportunity to apply concepts and skills you acquired in the unit to a realistic database design scenario and reflect on the data requirements of an organisation.

The submission is divided into 2 parts due at different times during the semester. These parts will cover:
A. Design of a database
B. Creation and use of a database
1. Design an ORM conceptual schema for a business domain based on sample reports required for that domain.
2. Map a different ORM schema to a relational database schema.

Task 1

Complete the drawings of ORM conceptual schema for the following universe of discourse.

Add, where required, fact types, verbalizations of fact types, connections of objects to role boxes, internal and external uniqueness constraints, mandatory constraints, value ranges, etc. as discussed in lecture and tutorial notes.

You must also clearly discuss and show all steps in your final submission.

The completed diagrams must be consistent with the properties and/or the rules in the description of the universe of discourse.

Step 1: Transform familiar examples into elementary facts and apply quality checks.

List all the deep structure sentences that you can identify based on the familiar examples mentioned in the scenario. For example:

The TennisPlayer with TennisPlayerName ‘A. Molik' is from the Country with CountryName ‘Australia'.

Step 2: Draw the fact types and apply a population check.

Use the deep structure sentences from Step 1 to draw fact types. As an example, consider the only binary fact type shown in the diagram above. Note that this fact type is introduced based on the example deep structure sentence proposed in the description of Step 1.
Perform a population check by populating identified fact types with the fact instances captured in the deep structure sentences. This can be accomplished by drawing fact tables.
For all the identified fact types discuss/demonstrate that they are indeed elementary by performing all the necessary split and join operations on sample populations.

Step 3: Check for entity types to be combined and note any arithmetic derivations.

Discuss in text if it does or does not make sense to combine any of the entity types proposed in the diagram. In this discussion do not exceed the word limit of 300 words. If some fact types must be combined, perform necessary modifications to your diagram.
Discuss in text if it does or does not make sense to introduce arithmetically derivable fact types in the diagram.. If some arithmetically derivable fact types must be introduced, perform necessary modifications to your diagram.

Step 4: Add uniqueness constraints and check the arity (length) of fact types.

Introduce all the uniqueness constraints in your ORM model that you can identify based on the scenario.
For each introduced uniqueness constraint, briefly explain the rationale behind your decision to include it in the model.

Step 5: Add mandatory role constraints.

Introduce all the mandatory role constraints in your ORM model that you can identify based on the scenario. For each introduced mandatory role constraint, briefly explain the rationale behind your decision to include it in the model.

Task 2

Map the following ORM schema to a relational database schema. You must also clearly discuss and show all the steps that you've been taken.

Attachment:- Database Management.rar