Task To Complete
1. Perform normalisation to 3NF for the data depicted in the sample documents. Note that only one normalisation is required for the function room evaluation, you have been provided with two samples so you can appreciate some of the variety which occurs. The approach you are required to use is the same approach as shown in the normalisation lab solution (see QB and QC). The normalisation must begin by you representing each of the supplied type of documents as a single UNF form and then taken through to 3NF, this process must be repeated for each different type of document. The documents must not be consolidated into one UNF at the start.
? Not add surrogate keys. They may be added after you have reached a final set of relations if desired (alternatively you may add them on your task 2 logical model).
? You must include all attributes (you must not remove any attribute as derivable)
? Clearly show UNF, 1NF, 2NF and 3NF.
? Clearly identify the Primary Key in all relations.
? Clearly identify all partial and transitive dependencies (if they exist) in all 1NF relations. You may use a dependency diagram or alternative notation (see the normalisation tutorial sample solution for a possible alternative representation). If none exist you must note this by stating: No partial dependencies present and/or No transitive dependencies present
Based on your assignment 1A conceptual model, your markers feedback, your reading of this case study and the normalisations you carried out in step 1 above, prepare a logical level design for the Monash Functions database.
? The logical model must be drawn using the Oracle Data Modeler. The information engineering or Crow’s foot notation must be used in drawing the model. Your logical model must not show datatypes.
? All relations depicted must be in 3NF
? You are required to add at least one surrogate key to your design (you are free to select the most appropriate relation to make this change in), you may add more if you wish
? All attributes must be commented in the database (ie. the comments must be part of the table structure, not simply comments in the schema file).
? Check clauses/look up tables must be applied to attributes where appropriate.
? You MUST include the legend as part of your model. If your laptop username is a nickname please edit the legend panel to show your actual name
? Note that your GIT repository must clearly indicate your development history with multiple commits/pushes as you work on your model