Reference no: EM131974797

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 assignment only for the following tasks:

Assessment task

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 (2) of your relations from the previous step, 1a), and perform the following for each ofthose two relations:

- List all the functional dependencies exist in the relation.

- 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.

Name cannot be used to functionally determine any other attribute in the table since two different students may have the same name; likewise for address and date of birth. Therefore there are no transitive dependencies in the table. Therefore it meets the requirements of first, second and third normal form.

Relational database implementation

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 reason for recommending Microsoft Access is that your unit lecturer/tutor will be able to provide adequate support to you in the use of this tool. If you choose to use a different DBMS, then there is no guarantee that your lecturer/tutor will be able to provide enough support to you. The remainder of this document assumes that you are using MS-Access.

In implementing the ER model provided, you must complete the following tasks:

Create all the relations in a Microsoft Access database. Consider each attribute in every table and make appropriate choices regarding data types & sizes, indexes, required/not required and validation rules. Your choices should be appropriate for each attribute and should support data integrity. (Note: see the Data Integrity section below for specific data integrity requirements)

Create relationships as appropriate. Enforce referential integrity for all appropriate relationships in the database. Apply cascade update and/or delete options wherever necessary.

Review the default index created by Access for each table. You should ensure that the indexes follow the guidelines given in the unit textbook.

Populate the database with sample data of your own. You must include sufficient sample data to test your queries and report. Please note that the expected result of query questions may depend on the actual sample data populated.

Data integrity

You are required to implement integrity constraints within the database to enforce the following requirements:

Insured amount should be positive currency and expressed in 2 decimals only.
Policy date should have appropriate date value.
Name of persons such as customer and assessor should not be null.
Each policy should be related to one property/home.

Information requests
Create queries to answer the following information requests:
Note: Do not use the Access query builder (QBE) to create your queries - you should type the queries manually using SQL view/editor.

The marking process of the queries for information requests may also consider the effectiveness of your SQL statements that have been used in the queries. It is important that your SQL statement must reflect the correct business logic & SQL syntax. (Use enough sample data so that the output is produced by each and every query).

Display the number of policies issued/created for each category of policies.
Display the details of assessor(s) who has/have never performed/completed any assessment report.
Display the number of settled and rejected claims.

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.

Display the highest amount of the claim-settlement(s) that has/have been done.

Display the total amount of premium paid for each of combined Home-buildings-contents policies.

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 this assignment. You may discuss any of the following:

Any two interesting things/procedures you learnt by doing this assignment.

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 that arise when implementing a relational database.

Attachment:- Assessment item.rar