Reference no: EM133922040
Database and Information Management
Project - Logical Database Design
In this assignment, steps in the logical database design are conducted (as described below) as well as revising the requirement analysis and conceptual design of assignment 1, and a report is written.
This assignment has 3 parts as specified below.
(Note: if the provided solution EER in template is not used in assignment 2, zero mark will be given for assignment 2.)
Re-do requirements and EER diagram (i.e., all the content of Assignment 1), according to the provided solution EER, and make a necessary discussion to point out the differences between the provided EER and the EER you submitted for your assignment 1.
A solution EER in the template document for the project is provided as a file in the same directory (Note: the file will be available in the week 7, after all assessments are collected.) Get expert-level assignment help in any subject.
You are required to use this EER as a source of correct information to complete all the tasks that are required by assignment 1, including Part 1- Requirements and Part 2 - EER Model with the data dictionary. Or in other words, you re-do all tasks specified in assignment 1, but make sure the EER is the one provided in EER-A1.pdf
You need to make sure all the content (such as data type, data dictionary) is consistent with the provided EER (e.g., EER has an entity Item, of which the attributes are itemNo, title, publisher, author (0 to 10), year, description, notes, and subject, and other attributes in subclasses. Then you must have these attributes in your data Item when you do data requirement analysis).
You also need to make the necessary discussion to point out the differences between your submitted EER and the solution EER (Your approaches can be wrong, or right but just different ways of expression). The places to be discussed can be the entities (including superclasses and subclasses), the attributes, relationships, relationship attributes, etc. The length of this section is limited to half to one page.
Note: you need to insert the solution EER (pdf file) into your report. As to the exact way of doing the insertion, you can search Internet.
Map the solution EER model to the relational model. Document the relational schema in DBDL (Sample format is given below)
ISBN (id, number, itemNo)
Primary Key id
Alternate Key number
Foreign Key itemNo references Book(itemNo)
ON UPDATE CASCADE, ON DELETE CASCADE
Normalize the schema to Boyce-Codd Normal Form (if any relation is not already in BCNF). The final normalised schema must be documented in DBDL.
The final report should include the following:
Necessary discussion to point out the differences between your submitted EER and the solution EER.
Requirement Specification (including data requirements, transaction requirements and business rules), based on the solution EER.
EER Diagram and Data Dictionary, based on the solution EER.
The relational model mapped from the solution EER (i.e., before normalisation)
Normalized Relational Schema in DBDL. Ensure that normalisation steps are shown if any.