instruction is in the file attached. The objective of this exercise is to demonstrate an understanding of basic concepts covered in the course. The exercise is a straight forward application of those concepts – there are no “hidden” complexities – should you identify something in the key points or data that adds complexity, contact the instructor before submission – you may be over thinking the exercise.

Assignment Instructions

Term Project – week 8 – (17%):
You were just hired to create a database to track blood draws at a lab.
Discussions with the representatives focused on two entities, Blood Draws and Patients; the following key points were agreed:
1 Each blood draw is assigned a unique DrawNum
2 Each Patient has a unique PatID
3 The Contact Number may not be unique for each patient
4 Each blood draw is taken from one patient, each patient may have more than one blood draw.
5 No fields beyond those in the report / spreadsheet are needed

DrawNum is a unique number assigned to each blood draw, Date is the date of the blood draw, Nvials is the number vials drawn, PatID is the ID for the patient – it is unique for each patient, fName is the patient’s first name, lName is the patient’s last name, DOB is the patient’s date of birth, Contact number is the contact number for the patient (patients may have the same number)

The objective of this exercise is to demonstrate an understanding of basic concepts covered in the course. The exercise is a straight forward application of those concepts – there are no “hidden” complexities – should you identify something in the key points or data that adds complexity, contact the instructor before submission – you may be over thinking the exercise.
The sample data may not represent all possible values – consider each field’s domain during the design.
The objective is to replace the following report / spreadsheet with a relational database. The submission will consist of a word compatible document to record the design process, and an Access DB. (A matching Excel spreadsheet is attached. This is provided to reduce typos – do not assume the spreadsheet is a table in the normalized design.)



Here is the un-normalized table notation for the above report:
BloodDraws (DrawNum, Date, Nvials, PatID, fName, lName, DOB, ContactNum)

The functional dependencies are:
DrawNum – – > Date, Nvials, PatID, fName, lName,DOB, ContactNum
PatID – – > fName, lName,DOB, ContactNum

The specific tasks to perform are listed below, the percentage corresponds to the grade weight for each task: Organize your document to match the tasks.
Name your document Last Name_TermProject (i.e. Smith_TermProject). When you are asked to provide an explanation or description, you must include sufficient content to demonstrate that you understand the definition, term, concept, etc. and how it applies to this exercise.

SUGGESTION: Review the Terms and Concepts Forum, especially the Normalization One-To-Many example. There is also a normalization MP4 file that can be downloaded from the Resources section.

Follow the below outline in your submission – include the section numbers – not the questions or other content from the instructions.
1) Review the existing report, functional dependencies and sample data (consider field domains and common knowledge) then document any assumptions you feel are appropriate (beyond those in the key points) and identify the initial entities (person, place, thing). (10%)

2 Define functional dependency and explain each row of the functional dependencies provided above (use field names and values). (15%) (you do not need to describe full, partial or transitive dependency in this task)

3) Based on multiplicity – in plain English explain the relationship between the Entities provided in the above description – (either one-to-many, or many-to-many). (15%)  

4) Design: all tables and fields must be specified at each normal form level
a) First Normal Forum (1NF) assessment / action  10%
Copy the 1NF definition from the text (include quotes and page number)
Assess the UNF table provided and if necessary, make the changes needed to conform to the 1NF definition. Explain any action taken and why.
Document the resulting 1NF table(s) using relational schema notation or spreadsheet format (see the above example or page 111 Figure 4.2.6 of the text).
Explain how each table(s) meets the 1NF definition (use field names and values)

b) Second Normal Form (2NF) assessment / action   10%
Copy the 2NF definition from the text (include quotes and page number)
Assess the 1NF table(s) in the previous section and if necessary, make the changes needed to conform to the 2NF definition. Explain any action taken and why.
Document the resulting 2NF table(s) using relational schema notation or spreadsheet format.
Explain how each table meets the 2NF definition (use field names and values)

c) Third Normal Form (3NF) assessment / action  10%
Copy the 3NF definition from the text (include quotes and page number)
Assess the 2NF table(s) in the previous section and if necessary, make the changes needed to conform to the 3NF definition. Explain any action taken and why.
Document the resulting 3NF table(s) using relational schema notation or spreadsheet format.
Explain how each table meets the 3NF definition (use field names and values)

5) Using the 3NF tables in your design, create an new MS Access database, load the sample data provided, and ensure any table relationship are established.
Name your database Last Name_TermProject (i.e. Smith_TermProject). (5%).
6) Create a Query, for the following request: List each Patient and their blood draws; include the following fields PatID, fName, lName, DrawNum, date, and Nvials, sort Ascending by lName. Call the Query BloodDraws. (5%)
7) Create a Form: for New Patient Input, label the form NewPatient. (5%)
8) Create a Report: List all Blood Draws  (5%)
Upload the database to the assignment area as one of the deliverables
9) Submission content organization, clarity, spelling and grammar (10%)  
Contact the instructor with any questions.<o:p>

First Normal Form (1NF) BEGG PG. 418

A relation in which the intersection of each row and column contains one and only one value.

Second Normal Form (2NF) BEGG PG. 422

A relation that is in first normal form and every non-primary-key attribute is fully functionally dependent on the primary key.

Third Normal Form (3NF) BEGGPG. 423

A relation that is in first and second normal form and in which no non-primary-key attribute is transitively dependent on the primary key.

Begg, T.C. C. (2014). Database Systems: A Practical Approach to Design, Implementation, and Management. [VitalSource Bookshelf]. Retrieved from https://online.vitalsource.com/#/books/9781269875356/