Get Instant Help From 5000+ Experts For
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing:Proofread your work by experts and improve grade at Lowest cost

And Improve Your Grades
myassignmenthelp.com
loader
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Guaranteed Higher Grade!
Free Quote
wave

Unit Learning Outcomes

This assessment item relates to the unit learning outcomes numbered 1, 2 and 3 as stated in the unit profile.

The sample solution of assignment 1 will be released on the unit website approximately two (2) weeks after the assignment 1 due date.  You must use that sample solution of assignment 1 only for the following tasks:

  1. Map the ERD, from the sample solution, into a set of relations in at least Third Normal Form (3NF). You must ensure that your relations meet 3NF. There is no need to show your
  2. Select any two (2) of your relations from the previous step, 1a), and perform the following for each of those two relations:
    • List all the functional dependencies exist in the
    • Demonstrate that the relation meets Third Normal Form (3NF).

For your help, an example for a Student relation’s 3NF justification has been provided below:

Student (StudentID, Name, Address, Date Of Birth)

i. The primary key is StudentID which identifies a student. There will be one student name per Student ID because only one name is recorded for each student. Even though a student may have multiple addresses (e.g. a home address and a work address), the case study states 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 birth for 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 guaranteed to be unique (two different students may have the same name).  Address is also not guaranteed to be unique. This means that Student ID functionally determines every other attribute in the table.  There is a single valued simple candidate key (StudentId) and therefore no partial dependencies are possible.  Hence, the relation is in 2NF.

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

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.

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

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.

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

  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.

  1. Display the highest amount of the claim-settlement(s) that has/have been done.
  2. 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, you need to put a bracket like [name].  Follow the same technique for other reserved words too.

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.

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

You must also provide a short implementation report describing your experiences with this assignment. You may discuss any of the following:

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

Microsoft Access databases file containing:

  1. Tables with sample data
  2. Relationships
  3. Queries
  4. Integrity constraints
  5. Report (object).

A Microsoft Word document containing:

  1. Two relations with functional dependencies and demonstration of normalization
  2. Implementation report

Your document should contain appropriate identification information (your student number, name, unit number, etc.) and should contain the relevant headings for each section. 

  • 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 document the 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.
Unit Learning Outcomes

The report is giving complete overview about CQI database that is implemented as normalized database in MS Access. The CQI database is containing queries, reports etc. that are very helpful for management.

ER Diagram Mapping

                         

Person (FielldPersonID, FielldPersonName, FielldStreet, FielldCity, FielldPostcode, FielldPersonType)

Assessor (FielldPersonID, FielldQualificationName, FielldDateQualified)

Foreign Key (FielldPersonID) References Person

Property (FielldPropertyID, FielldStreet, FielldCity, FielldPostcode, FielldPersonID)

Foreign Key (FielldPersonID) References Person

Policy (FielldPolicyID, FielldEffectiveFromDate, FielldPremiumAmount, FielldPaidDate, FielldIsHomeBuildingPolicy, FielldIsHomeContentsPolicy, FielldTotalPolicyAmount, FielldPropertyID)

Foreign Key (FielldPropertyID) References Property

Home_Building (FielldPolicyID, FielldHouseType, FielldYearBuilt, FielldIsAlarmFitted, FielldHasWindowsLocks, FielldInsuredAmount, FielldBuildingPremiumAmount)

Foreign Key (FielldPolicyID) References Policy

Home_Content (FielldPolicyID, FielldContentPremiumAmount)

Foreign Key (FielldPolicyID) References Policy

Content_Item (FielldItemID, FielldItemName, FielldManufacturer, FielldModel, FielldPurchasePrice, FielldQuantity, FielldClaimedStatus, FielldPolicyID)

Foreign Key (FielldPolicyID) References Policy

Claim (FielldClaimID, FielldLodgedDate, FielldStatus, FielldPolicyID, FielldPersonID)

Foreign Key (FielldPersonID) References Person

Settled_Claim (FielldClaimID, FielldSettledDate, FielldAmountSettled)

Foreign Key (FielldClaimID) References Claim

Rejected_Claim (FielldClaimID, FielldRejectedDate, FielldRejectedReason)

Foreign Key (FielldClaimID) References Claim

Items_Claimed (FielldClaimID, FielldItemID, FielldItemName, FielldQuantity, FielldItemStatus)

Foreign Key (FielldClaimID) References Claim

Foreign Key (FielldItemID) References Content_Item

Assessment_Report (FielldReportID, FielldReportDate, FielldInitialRecommendation, FielldReportType, FielldClaimID, FielldPersonID)

Foreign Key (FielldClaimID) References Claim

Foreign Key (FielldPersonID) References Assessor

Final_Assessment_Report (FielldReportID, FielldFinalAssessmentDate, FielldTotalAmount, FielldCostReportMemo)

Foreign Key (FielldReportID) References Assessment_Report

Assessor (FielldPersonID, FielldQualificationName, FielldDateQualified)

FielldQualificationName à FielldPersonID

FielldDateQualified à FielldPersonID

All assessor records are depending upon the Person ID as it is the primary key in the Assessor table.

Property (FielldPropertyID, FielldStreet, FielldCity, FielldPostcode, FielldPersonID)

FielldStreetà FielldPropertyID

FielldCityà FielldPropertyID

FielldPostcodeà FielldPropertyID

FielldPersonIDà FielldPropertyID

All property records are depending upon the Property ID as it is the primary key in the Property table.

The CQI database is designed as third normalized database by using the following rules-

  • Create new tables for separated data.
  • Set primary key in all newly created tables.
  • All fields depend upon the primary key only.
  • Transitive dependency should not occur in any table.

 (USA Informa 2018)

(BigennersBook 2017)

SELECT homeSubQuery.Home_Policy, contentSubQuery.Home_Content_Policy FROM (SELECT Count(*) AS Home_Policy FROM Home_Building)  AS homeSubQuery, (SELECT Count(*) AS Home_Content_Policy FROM Home_Content)  AS contentSubQuery;

                                                       

SELECT Person.PersonID, Person.PersonName, Person.Street, Person.City, Person.Postcode, Person.PersonType FROM Person WHERE Person.PersonID not in (Select PersonID from Assessment_Report) and Person.PersonType='Assessor';

                     

SELECT settledSubQuery.Settled_Claim, rejectedSubQuery.Rejected_Claim

FROM (SELECT Count(*) AS Settled_Claim FROM Settled_Claim)  AS settledSubQuery, (SELECT Count(*) AS Rejected_Claim FROM Rejected_Claim)  AS rejectedSubQuery;

                                                 

SELECT * FROM Person WHERE PersonID in (Select Property.PersonID FROM Property INNER JOIN (Policy INNER JOIN Claim ON Policy.PolicyID = Claim.PolicyID) ON Property.PropertyID = Policy.PropertyID Where Claim.Status='Rejected');

                   

SELECT TOP 1 ClaimID, AmountSettled, SettledDate FROM Settled_Claim ORDER BY AmountSettled DESC;

                                             

SELECT Policy.PolicyID, Policy.IsHomeBuildingPolicy, Policy.IsHomeContentsPolicy, Policy.PremiumAmount AS ['Total Premium Amount'] FROM Policy WHERE Policy.IsHomeBuildingPolicy<>0 and Policy.IsHomeContentsPolicy<>0;

                           

                                   

The assignment is giving lots of knowledge in the following fields-

  • Database SQL queries
  • Database report
  • Work on sub queries
  • Work on join queries

I faced complexity only in two areas-

  • Sub queries
  • Join queries

Conclusion

The report is completely based upon the CQI database and showing all the features that are used in making the CQI database like normalization, functional dependencies, queries, reports etc.

References

BigennersBook (2017), Normalization in DBMS: 1NF, 2NF, 3NF and BCNF in Database: Foreign Keys, Retrieved from:

https://beginnersbook.com/2015/05/normalization-in-dbms/

USA Informa (2018), SQL by Design: Why You Need Database Normalization.  Retrieved from:

https://www.itprotoday.com/risk-and-compliance/ibm-executives-press-us-lawmakers-not-adopt-eu-privacy-law.

Cite This Work

To export a reference to this article please select a referencing stye below:

My Assignment Help. (2020). Assignment 1: Implementation Of A Relational Database - CQI Essay.. Retrieved from https://myassignmenthelp.com/free-samples/coit20247-database-design-and-development/er-diagram-mapping.html.

"Assignment 1: Implementation Of A Relational Database - CQI Essay.." My Assignment Help, 2020, https://myassignmenthelp.com/free-samples/coit20247-database-design-and-development/er-diagram-mapping.html.

My Assignment Help (2020) Assignment 1: Implementation Of A Relational Database - CQI Essay. [Online]. Available from: https://myassignmenthelp.com/free-samples/coit20247-database-design-and-development/er-diagram-mapping.html
[Accessed 30 May 2024].

My Assignment Help. 'Assignment 1: Implementation Of A Relational Database - CQI Essay.' (My Assignment Help, 2020) <https://myassignmenthelp.com/free-samples/coit20247-database-design-and-development/er-diagram-mapping.html> accessed 30 May 2024.

My Assignment Help. Assignment 1: Implementation Of A Relational Database - CQI Essay. [Internet]. My Assignment Help. 2020 [cited 30 May 2024]. Available from: https://myassignmenthelp.com/free-samples/coit20247-database-design-and-development/er-diagram-mapping.html.

Get instant help from 5000+ experts for
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing: Proofread your work by experts and improve grade at Lowest cost

loader
250 words
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Plagiarism checker
Verify originality of an essay
essay
Generate unique essays in a jiffy
Plagiarism checker
Cite sources with ease
support
Whatsapp
callback
sales
sales chat
Whatsapp
callback
sales chat
close