COIT20247 Database Design and Development Assignment
Added on -2019-09-19
| 5 pages
| 1749 words
| 456 views
Trusted by 2+ million users, 1000+ happy students everyday
Showing pages 1 to 2 of 5 pages
COIT20247 Database Design and Development (T12017) Assessment item 2—Assignment2Due date11:45pm on FridayofWeek10 (May 19, 2017)Weighting35%LengthNot applicableObjectivesThis assessment item relates to the unit learning outcomes numbers 1, 2 and 3 as stated in the unitprofile.IntroductionThe 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 ofassignment 1 only for the following tasks:Assessmenttask1Normalizationa)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 followingfor 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. There is a single valued simple candidatekey (StudentId) and 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 therequirements of first, second and third normalform.2Relational databaseimplementationNote: Use the relations that you created in the above step 1-Normalization to create adatabase. 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 ableto provide adequate support to you in the use ofthis tool.IfyouchoosetouseadifferentDBMS,thenthereisnoguaranteethatyourlecturer/tutorwillbeableto provide enoughsupport to you. The remainder of this document assumes that you are using MS-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. Apply cascade update and/or deleteoptions wherever necessary.Review the default index created 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.DataintegrityYou are required to implement integrity constraints within the database to enforce thefollowing requirements:Fees/Charges should be positive currency and expressed in 2 decimals only.Date values should not be predated.Name of patients/medical specialists should 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.
Found this document preview useful?
You are reading a preview Upload your documents to download or Become a Desklib member to get accesss