The United Kingdom Awarding Body (UKAB) has asked me to design a system for the monitoring of its post-examinations re-marks.

Authors Avatar
Introduction

The United Kingdom Awarding Body (UKAB) has asked me to design a system for the monitoring of its post-examinations re-marks.

If a centre feels that the grade awarded to a candidate for an examination is lower than expected, the centre can ask for that script to be remarked. The UKAB expects all this to be completed within three weeks.

All the details must be stored for the purpose of analysis and monitoring

File Design

External file name: Re-Mark.dat

General name: Re-mark

Description: Stores details of all current candidates

Record structure

Field name

Field description

Data type

No. bytes

CandName

Candidate's Name

String

6

CandNo

Candidate's Number

String

4

CenterNo

Centre Number

String

5

DateSub

Date of the exam paper submitted

Date

0

SubRef

Subject Reference Code

String

5

OrgMr

Original Mark

Integer

2

OrgGr

Original Grade

String

2

PaperRt

Paper to be returned?

String

3

RemarkedMr

Remarked Mark

Integer

2

RemarkedGr

Remarked Grade

String

2

DateRt

Date of paper when returned

Date

0

Record size 61 bytes

Typical size of file 1 record per script. With 15 scripts= 990 bytes

Data Flow Diagram

Data Requirements

Data to be input:

The following details will be stored for the re-marks:

* Candidate name

* Candidate number

* Centre number

* Subject reference code

* Original mark

* Re-mark

* Centre requested script

* Date paper submitted

* Date paper re-marked

* Grade affected by remark

For a subject the following will be stored:

* Subject Reference Code

* Grade boundaries for grades A-E and U

* Date for the request of the re-mark

Data to be output:

Print out of all candidates remarks details

Print out of all specific centre number

Print out of all specific subject reference code

Print out of all re-marks that have not been returned in a three week period

Print out of all re-marks were the grade have been affected

Analysis of software

I have decided that there are four possible roots which I can follow to complete this project:

* Database

* Spreadsheet

* Bespoke programming

* Website

I will next analyse the pros and cons of each method of completing this task.

* Database:

A database is a very easy way, for a relatively low trained user, to enter data. Once the database has been set up the user can easily input data into the relevant fields. The database creator can create simple methods of data entry, such as Boolean fields, which makes the data entry more effective and reduces the risk of incorrectly entered data. A new record for each customer would be a simple and practical method that could be implemented. This would also provide the basis for a report, which could be more easily created on a database than on a spreadsheet. Data validation is easily implemented on the database package, with different types of validation, such as currency, Boolean, more than, less than, etc. The presentation of the data is more than adequate on a database.

Statistical analysis and mathematical functions are impossible to undertake on a database, details would need to imported and exported between a database and a spreadsheet. This means that if a database were to be used it would have to be used in conjunction with a spreadsheet package; therefore it seems slightly pointless to use a database, because a comprehensive spreadsheet package could do all the functions to complete this task.

* Spreadsheet:

Setting-up a spreadsheet can be undertaken with relative ease. The clear advantage spreadsheets have over and above the other options is the ease of entering mathematical formula and the ease with which numbers can be processed. Unlike the other packages in which data must be exported and imported through different packages, the spreadsheet is capable of completing all aspects of the task. Within the spreadsheet package there is also the opportunity to link sheets, which in this task will prove essential.

Validating data in a spreadsheet is a very simple operation, once a cell has been chosen Validation can be selected from the Data menu. Different types of validation can then be performed on the cells contents. The presentation of the data can be arranged well and easily. Using buttons with macros can make printing and saving operational from the actual spreadsheet page, rather than the user having to use menus.

When the form of the spreadsheet has to be designed it is harder to accomplish what you want, the cells must be stretched or shrunk, unlike a database in which the form can be specified very easily.

* Bespoke program:

The layout, style, form and function of a bespoke program could be tailored exactly to the user's requirements. The program would allow the least computer literate person to use the program; this is because that with enough programming the program created would have the complex workings hidden under a user-friendly face.

Out of all the possible options a well-designed bespoke program would work most successfully. But to gain this high level success a vast amount of time would have to be spent creating the program. Updating the program by a relatively low trained employee would be comparably harder than with the other options. It is the limiting factor of time that will prevent me from using a program over and above the other methods; the feasibility of the program is not very high.

* Website:

With a web site it would be easy to make the user interface and the structure for the application, with very positive results. But when a website is used no mathematical formulae can be entered. All formulae would have to be entered via the spreadsheet and then imported to the website.

It seems unnecessary to use a website because I could very easily cut out the "middle-man" and use the spreadsheet instead, since it has the capabilities to link pages very easily as well.

Form Design

Report Design

Data Validation & Integrity

There are a number of checks that I will carry out to ensure that data are correct whilst entering the data in the system. I will consider that information is available to the system at the point of data entry before validation method.
Join now!


The following validation that I will include is:

Field

Form

Validation check

Candidate Number

Candidate

. Length 4 digits

2. Type check (must be in digits not characters)

Candidate Name

Candidate

. Presence check (Must not be blank)

2. Type check (must be in characters not digits)

Centre Number

Candidate

. Length 5 digits

2. Type check (must be in digits not characters)

3. Range with in 10000 - 80000

Subject Reference Code

Candidate

. 5 Digits

...

This is a preview of the whole essay