Weblog Directory | Westminster Technology Department

« February 2005 | Main | May 2005 »

April 25, 2005

IT database test

READ THIS VERY CAREFULLY

The brief

You are to design a database that can record the subject choices of grade 9 students as they enter grade 10.

The data you will work with includes;
Student first name - Subject name - Student last name - Subject Id. number - Student current advisory - Teacher first name - Student Id. number (to be set by your database) - Student gender - Teacher last name - Classroom number.

Follow this link to find the data you need to test your database with.
Remember that importing this should be the last stage of the process
You cannot seek any technical advice
You cannot talk to other students, If you need to say anything, raise your hand.
The test will take one hour of solid work

Remember this is a test - used to assess your learning


The test will be assessed on three tasks weighted as follows:
For specific criteria see blog entry below
One-third
for the first part, your design (entity) diagram, drawn on to a sheet of A4 paper in pen (not made on a computer).
One third,
for the second part,making your database.
One-third
for the third part, importing the appropriate data into the correct fields.

So, don't delay and concentrate just on the task at hand.

April 22, 2005

IT database test assessment criteria

Assessment criteria for Database Test

One-third
for the first part, your design (entity) diagram, for a database, which can do the job, as set out in the brief. This should be drawn on to a sheet of A4 paper in pen (not made on a computer).
You will get credit for the correct table (entity) configuration, and for showing appropriate relationships.
A correct configuration with the most feasible and /or appropriate relationships for the usage of this database will get a 7 for this section.
A design which demonstrates the correct configuration but fails to make appropriate or feasible relationships will be awarded a 5 or a 6
Designs which demonstrate a configuration that addresses the problem of a many to many relationship but fails to use the correct configuration will be awarded a four.
Designs which fail to demonstrate a configuration to address the above will be awarded three or less

One third,
for the second part, to construct a database to do the job set out in the brief.
You will get credit for the following even if your solution isn't completely functional:
Making value lists which are appropriate and functional, making accurate and appropriate calculation fields, making workable table relationships and fields formatted as pop-up lists, making accurate and appropriate aut-entered data fields

One-third
for the third part, importing the appropriate data into the correct fields.
7 will be awarded where the data in both cases has been imported accurately and appropriately.
5 or 6 will be awarded where the import has been accurate and appropriate in one case but there has been inconsistency in the second with regard to one or more aspects of accuracy or appropriateness.
4 will be awarded where in only one case the data has been imported appropriately and accurately.
3 or less will be awarded where one case has been imported and this is neither accurate or appropriate.