Reference no: EM132309612

Database implementation using MS Access

Introduction

You must use that sample solution of assignment only for the following tasks:

Assessment 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.  The candidate key, StudentId, is a simple and single valued attribute. 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 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 reasonfor recommending Microsoft Access is that your unit lecturer/tutor will be able to provide adequate support to you in the use ofthis tool.The remainder of this document in Part A 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 that the expected result of query questions may depend on the actual sample data populated.

Data integrity

Select one table that contains at least three different data type attributes, such as date, text and currency value attributes.For that selected table, develop and implement suitable integrity constraints for its attributes. You need to provide those integrity constraints in the following tabular form:

Attribute

Data type

Integrity constraint implemented

Error message

Information requests

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.

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 statements must reflect the correct business logic & SQL syntax.

Attachment:- Sample Solution.rar