​​QTasks The Hospice requires a Microsoft Access 2013 relational database to manage and organise information about their volunteers. Their current database is a large flat file which is becoming increasingly difficult to both maintain and access information. Using the un-normalised structure provided you should complete the following tasks: Relational Modelling  Model the Data using ERM and ERD techniques  Normalise the data to 3 Database Using your relational model produce a database using Microsoft Access 2013, your implementation should include the following:  Tables based upon the results of your relational model  Data input mechanisms (MS Access Forms)  Pre written queries  Formatted reports that detail the following: rd Normal Form o A single Volunteer's details o Departments and their Volunteers o Volunteer Safety Training completed, grouped by category and order date ascending o Volunteers who have not completed Safety Training  Appropriate input masks and constraints. Testing You should devise a test plan and generate sufficient sample data to test the functionality of all aspects of your database. Documentation  Technical database documentation (as a minimum your schema)  User documentation Assignment Details Submission Requirements 1. Database design documentation including your ERM and Normalisation process 2. Access 2013 database 3. Completed test plan 4. Documentation Databases will be demonstrated in class during sessions 26th May 2016 Assignment Details Assessment Criteria 1. Design and Implement an appropriate relational database for the given scenario using the appropriate database design techniques discussed on the course. 2. Efficiently store data so as to eliminate data anomalies and redundancy. Database design is fit for purpose and implemented appropriately. Implementation is based upon design work [D- to C] Clear evidence of structured design. Relationships are clearly derived and data is normalised to 3NF [C+ to B ] Thoroughly documented design process indicates clear understanding of the application domain. Domain assumptions are appropriately documented [B+ to A+] Implementation provides effective structure for the application [D- to C] Implementation provides efficient structure for the application against most of the use cases identified in the brief [C+ to B] The data structure provides an efficient structure for all the use cases provided. Clear consideration has been given to the ease with which the data structure could be adapted to support future development [B+ to A+] 3. Allow the user to interrogate the database using the interface described so as to return meaningful and timely result sets based upon input. A simple range of queries allow the user to extract information from the application [D- to C] Queries have been implemented which capture the full range of use cases detailed in the scenario [C+ to B] Users are easily able to extract complex/compound sets of relevant information from the application [B+ to A+] Assignment Details 4. Produce design and test documentation for your solution. Documentation clearly covers all aspects of the brief. Testing is structured [D- to C] Documentation is professionally presented and testing covers all aspects of the application [C+ to B] Testing and documentation cover all aspects of the application domain and follow a coherent strategy. There is clear evidence of the application of further reading [B+ to A+] Assignment Details A+ Excellent 24 Distinction A 21 A- 18 B+ Good 17 Commendation B 16 B- 15 C+ Satisfactory 14 Merit C 13 C- 12 D+ Weak 11 Pass D 10 D- 9 F1 Marginal Fail 7 Fail F2 Fail 4 F3 Poor Fail 2 F4 Very Poor Fail 0 Assignment Details Late Submissions Where work is submitted between one and three days after the published deadline without an agreed extension the mark for the assessment will be reduced in accordance with the table below. Quality of Work Grade Awarded A+ B+ A B A- B- B+ C+ B C B- C- C+ D+ C D C- D- D+ F1 D D- F1 F2 F2 F3 F3 F4 F4