Making a great Project 2
OCR 1994/2360
Design
Some candidates dive in, make a
database or spreadsheet, then try and
make a design afterwards.
This won’t work.
It’s too obvious.
Take care to plan it all out FIRST!
Design 1 – data structure
A data structure explains how the data is
related.
Whether you use a database or a
spreadsheet, every record is divided into
fields.
You should be able to decide on a title,
data type, and length for each field.
For detailed advice on spreadsheet design click here
Design 1 – data structure
Set your data structure out in a table.
Now make an alternative design – perhaps
some fields are missing, or are not
needed, or you could divide one field into
two or more.
Both the designs must do the job! Never
set out to make a “bad” design!
Design 1 – data structure
Describe the advantages and
disadvantages of each table.
Now choose one of them and say why it is
best for the job.
Design 2 – input formats
In a well-designed database, the end user
should NEVER see the data table.
You should use forms to access the data.
The forms will be used to enter new data
and amend existing data.
Design 2 – input formats
Design a suitable layout for the data form.
DO THIS ON PAPER OR IN A GRAPHICS
PROGRAM – never in the database itself.
Make sure it has all the fields that are on your
chosen data structure.
Now design an alternative layout for the form –
perhaps the fields could be laid out differently.
Design 2 – input formats
You don’t have to use a relational
database (ie one with more than one data
table).
But if you do, you must design input forms
for every table.
Design 2 – input formats
Once again, describe the advantages and
disadvantages of each one.
Choose which one you will use.
Give reasons why it is the best one for the
job.
Design 2 – input formats
It is a good idea to link your forms and outputs
with a main user screen or switchboard.
You can use buttons on the switchboard to open
forms, reports, and letters.
Design a switchboard. Design an alternative.
Describe the advantages and disadvantages of
each one.
Choose which one you will use. Say why.
Design 3 – output formats
Most outputs will be the results of
searches or queries.
Your User Requirements should tell you
what the user wants to be able to search
for.
Start by listing the queries that will be
needed.
Design 3 – output formats
In a well-designed database, the end user
should never see the queries.
They will either see a report, intended for
print, or a screen form.
If several searches could be carried out on
the same field, you could use a parameter
query.
Design 3 – output formats
Produce a design for each query output – make
it clear whether it is a screen form or a print
report. (Remember, not using the database
software itself!)
Produce an alternative design for each one.
You should also design the layout of any
mailmerged letters here.
Design 3 – output formats
Describe the advantages and
disadvantages of each output layout
Choose the ones you will use.
Say why they are the best for the job.
Design 4 – hardware & software
Here you get to say what equipment you
need.
Research possible computer systems.
Make sure they are suitable for the job.
DO NOT get too technical – you should
understand the specification.
Consider peripherals which might be
needed, such as printers.
Design 4 – hardware & software
List just two suitable hardware
specifications.
Describe the advantages and
disadvantages of each one.
Say why you have made your choice.
Design 4 – hardware & software
Now research suitable software. Normally
you will require database software.
You should compare at least two datahandling programs and their ability to do
the job.
You might also need a wordprocessor or
DTP.
Design 4 – hardware & software
Don’t waste time comparing operating systems –
different versions of Windows or Linux or
MacOS are not relevant.
Don’t waste time on incidental software like
antivirus or firewalls.
Don’t waste time comparing different versions of
a program or package, eg MS Office.
Design 4 – hardware & software
Give the advantages and disadvantages of
the software you have compared.
Make a choice and give valid reasons for
your choice.
Remember your reasons must be relevant
to the problem and your user’s
requirements.
Design complete…
That’s it! You should now have a suitable
design for a solution to the problem.
Your next step will be to carry out your
design.