CREATE RELATIONSHIPS AS APPROPRIATE

CREATE RELATIONSHIPS AS APPROPRIATE

Here, you are required to present a report covering all these aspects:

• Map the ERD, from the sample solution, into a set of relations in at least Third Normal Form (3NF).
• Create relationships as appropriate and 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.
• Implement integrity constraints within the database to enforce the mentioned requirements.
• Create queries to answer the mentioned information requests.
• Provide a short implementation report describing your experiences with this assignment.

Assessment task

1          Normalization

1. 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.
2. 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 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:

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

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:

• Fees/Chargesshould be positive currency and expressed in 2 decimals only.
• Date values should not be predated.
• Name of patients/medical specialistsshould not be null.
• State values should be limited to Australian States/Territories only.
• Skills and experience values should not be null.
• Discount amount should be positive and cannot exceed $50.

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 details of medical specialist(s) who has/have never performed/completed any appointment.
2. Display the details of appointment, name of the patient and medical specialist involved in the most expensive appointment.
3. For each of the medical specialists, display his/her name and the number of appointments completed so far.
4. For each of the appointmentcompleted, display the date, (start) time, name of the patient and total fees/charges of the appointment, discount amount and final amount payable. (Final amount payable = total appointment charges – discount amount )
5. Which patients have consulted more than one specialist? Display the details of such patients only.
6. Display the details of the patient(s) whose name contains the word “more”. Show the results in ascending order of the name.

ImplementationReport

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.

Assessmentcriteria

COIT20247 Assignment 2 Marking Sheet