Assignment: Database Design and Development
Objectives
This assessment item relates to the unit learning outcomes numbered 1, 2 and 3 as stated in the unitprofile.
Introduction
The sample solution of assignment 1 will be released on the unit website approximately two (2) weeks after the assignment1 duedate. You must use that sample solution of assignment1 only for the following tasks:
Task
1 Normalization
a) Map the ERD, from the sample solution, into a set of relations in at least Third Normal Form (3NF). You must ensurethat your relations meet 3NF. There is no need to show yourworking.
b) Select any two of your relations from the previous step, 1a), and perform the following for each ofthose two relations:
• List all the functional dependencies exist in therelation.
• Demonstrate that the relation meets Third Normal Form (3NF).
For your help, anexample for a Student relation's 3NF justification has been provided below:
STUDENT (StudentID, Name, Address,DateOfBirth)
i. The primary key is StudentID which identifies a student. There will be one student name per Student ID because only one nameis recorded for each student. Even though astudent may have multiple addresses (e.g. a home address and a work address), the case studystates that there is a need to record the home address only and hence there will be only one address for each student. There will be only one date of birthfor each student. Thus, there are no repeating groups. Hence, this relation is in 1NF.
ii. The primary key is StudentID. This is the only candidate key since Name is not guaranteedto be unique (two different students may have the same name). Address is also notguaranteed to be unique.This means that Student ID functionally determines every other attribute inthe table. There is a single valued simple candidatekey (StudentId) and therefore no partial dependencies are possible. Hence, the relation is in 2NF.
iii. Name cannot be used tofunctionally determine any other attribute in the table since two different students may have thesame name; likewise for address and date of birth. Therefore there are no transitive dependenciesin the table. Therefore it meets the requirements of first, second and third normalform.
2 Relational databaseimplementation
Note: Use the relations that you created in the above step 1-Normalization to create a database. The recommended tool for this work is Microsoft Access, version 2010 or later. One reasonfor recommending Microsoft Access is that your unit lecturer/tutor will be able to provide adequate support to you in the use ofthis tool.IfyouchoosetouseadifferentDBMS,thenthereisnoguaranteethatyourlecturer/tutorwillbeableto provide enough support to you. The remainder of this document assumes that you are usingMS-Access.
In implementing the ER model provided, you must complete the followingtasks:
• Create all the relations in a Microsoft Access database. Consider each attribute in every tableand make appropriate choices regarding data types & sizes, indexes, required/not requiredandvalidation rules. Your choices should be appropriate for each attribute and should supportdata integrity. (Note: see the Data Integrity section below for specific data integrityrequirements)
• Create relationships as appropriate. Enforce referential integrity for all appropriaterelationships in the database. Applycascade update and/or deleteoptions wherever necessary.
• Review the default indexcreated by Access for each table. You should ensure that theindexes follow the guidelines given in the unittextbook.
• Populate the database with sample data of your own. You must include sufficient sample data to testyour queries and report. Please note thatthe expected result of query questions may depend on the actual sample datapopulated.
Dataintegrity
You are required to implement integrity constraints within the database to enforce thefollowing requirements:
• Insured amountshould be positive currency and expressed in 2 decimals only.
• Policy date should have appropriate date value.
• Name of persons such as customer and assessor shouldnot be null.
• Each policy should be related to one property/home.
Informationrequests
Create queries to answer the following information requests:
Note: Do not use the Access querybuilder (QBE) to create your queries - you should type the queries manually using SQLview/editor.
Themarking process of the queries for information requests may also consider the effectivenessofyourSQL statements that have been used in the queries.ItisimportantthatyourSQLstatementmustreflectthe correct business logic & SQLsyntax.(Use enoughsampledataso that the output is produced by each and every query).
1. Display the number of policies issued/created for each category of policies.
2. Display the details of assessor(s) who has/have never performed/completed any assessment report.
3. Display the number of settled and rejected claims.
4. Display the details of customer(s) whose claim(s) has/have been rejected.
Note:Amongst many claims by a single customer,even if anyone claim has been rejected you need to display the details of that customer.
5. Display the highest amount of the claim-settlement(s) that has/have been done.
6. Display the total amount of premium paid for each of combined Home-buildings-contents policies.
Note: The word ‘name' is a reserved word in MS Access. Wherever you use it for SQL query, youneed to put a bracket like [name]. Follow the same technique for other reserved words too.
Report
Create a simple report object showing the details of rejected claims.The report should provide the details of claim, policy and property details in ascending order of claim date.
Hints:
• Create a query that lists all details needed for a report. If you are unable to formulate this query, then create a report that is based directly on the table(s). [Note: you will not be able to obtain full marks for the report creation if you base your report directly on the table(s) and some criteria are not met in your reports.]
• Use the report wizard to generate a basic report based upon your query [or the table(s) if you were unable to formulate the query].
• Once the report wizard finishes, switch to design view and rename the labels appropriately.
Implementation Report
You must also provide a short implementation report describing your experiences with thisassignment. You may discuss any of thefollowing:
1. Any two interesting things/procedures you learnt by doing this assignment.
2. Any one requirement of the assignment that was relatively difficult/complex to solve but successfully completed by you.
Use the implementation report to demonstrate that you have thought carefully about the issues thatarise when implementing a relationaldatabase.
What you shouldsubmit
Microsoft Access databases filecontaining:
1. Tables with sampledata
2. Relationships
3. Queries
4. Integrityconstraints
5. Report (object).
A Microsoft Word documentcontaining:
1. Two relations with functional dependencies and demonstration ofnormalization
2. Implementationreport
Your document should contain appropriate identification information (your student number, name,unit number, etc.) and should contain the relevant headings for eachsection.
Importantpoints
• You must work individually on this assignment.
• The model solution to this assignment will be released approximately two (2) weeks after the due date.
• Assignments that are submitted after the release of the model solution will receive zero marks.
• You must state in your word documentthe details of all materials and sources that you used to complete this assignment. This may be as simple as 'This assignment was completed using only the COIT 20247 unit materials'.
• Extension requests (by filling in an online form) should be submitted before the assignment due date.
• Before submitting your assignment, review the marking criteria provided on the last page of this document. Ensure that all the criteria are addressed in your submission.
• Penalties related to late submission and plagiarism will be applied as per University policy.