GCSE ICT WEB PAGE DESIGN COURSEWORK
WHAT ARE THE SECTIONS IN THE WRITE-UP OF A PIECE OF COURSEWORK?
USE & IMPLEMENT
DETAILS OF THE ‘IDENTIFY’ SECTION
You must describe some problem that needs to be solved by using ICT skill, as though you yourself
have been asked to provide a solution to a problem e.g. “Miss Ann Thrope, the chief executive of
Hags plc, needs to establish a web site to publicise the functions of her company and she has asked me to
compile this for her.”
You must give the name of the user that will benefit from the ICT-based solution you describe. This user
will be an imaginary person who will be role-played by someone if the coursework centres on an
imaginary business or organisation; in the example about the company mentioned above, someone
(usually your ICT teacher) would role-play the part of the intended user.
In the case of web design coursework, there is obviously no non-ICT alternative. Marks awarded in this
section will be based on how well you can justify your choice of software. Word 2000, Publisher 2000
and Front Page 2000 can all save as web (*.htm) pages. However, in producing identical web pages, these
three applications might generate widely differing amounts of HTML code. The best web pages would be
those which consist of as few lines of HTML code as possible, whilst sacrificing no detail. If you are
personally highly-skilled at programming in HTML, you could compile your web site directly in HTML:
anyone who can’t program directly in HTML will have to choose software to draw up the code for them.
Before you can even design your web site, you need to draw up one very simple web page in Word 2000
(with, for example one text frame, one graphic, a simple background colour, and no hyperlinks). You
must then recreate exactly the same web page in Publisher 2000 and Front Page 2000, and possibly also
directly in HTML, if you are that way inclined. You must compare the number of lines of HTML code
generated by each option, and use the information to choose the way in which you will actually generate
the web site that will form the basis of this coursework. You must save print-outs of your 3 or 4 sample
web pages, and you must print out the source code for each page from Word 2000 or Notepad.
DETAILS OF THE ‘ANALYSE’ SECTION
This is broken up into 3 sections: Input, Process and Output.
In this sub-section, you must write where the data, graphics etc. will come from in the imaginary
situation, as though the imaginary situation is real, and you are really acting as an ICT consultant
sorting things out for the intended user. So don’t write things like “I’m making up the logos to have
something to include in my web site.” You should write things like this: “I’m going to scan in some
pictures and I’m going to take some other pictures from the web site on http://www.xyz.com so that the
graphics will show what I’ve been commissioned to include.”
If you intend to use copyright material from a web site, you should e-mail the webmaster and ask
permission, stating that this is for the purpose of GCSE ICT coursework. This is an instance where you
can step outside your role-play. You should include a printout of any e-mail you send, and also a print-out
of any reply you receive.
In this sub-section, you must state, in outline, what processes the text and graphics will go through as you
use the features of the software on them. Don’t explain each process in detail: you just have to say what
you’ll do e.g. “I’ll link each page to the home page and vice-versa; I’ll also have links to the following
external sites……..” This part of your work cannot be too general: it must relate to the imaginary
situation of your coursework. You must state every function you intend to use, but details of the use of
each of these functions must be saved until you do the design section.
In this sub-section, you must state what the results will be of the processes the raw material undergoes.
An output in this case will be a description in words of the content of each web page and where you
intend each page to link to.
DETAILS OF THE ‘DESIGN’ SECTION
This section is make-or-break for the entire
piece of coursework!!
Any web pages MUST be designed with pen / pencil and paper before you ever get to produce even very
rough tentative versions on a computer screen. Your pen-and-paper versions must be annotated with
reasons for your choice of layout, font, size, text colour, background colour etc. This is so that the person
marking your coursework can check that the software files you generate actually relate to what you
planned to do in the first place. This is the one part of the write-up that must absolutely NOT be word-
You must also draw a site map showing each page and how it links to each other page. This may be done
using the drawing tools in Word 2000. An example is included below, but for GCSE, you must aim to
have an index page plus at least 8 sub-pages in order to achieve a suitably challenging level of
I-Zingari Cricket Club http://www.cricinfo.com
1st XI 2nd XI SOCIAL
These designs must be kept and handed in with the coursework. The rest of the material specified for the
design section must be in words i.e. handwritten or in a word processor document.
You must include details in writing of everything you include on each web page; it’s best to take one web
page at a time and consider each one as a sub-section in the design section. You must explain any special
treatment for graphics: web pages will only display your pictures as .jpg or .gif files, so you have to
explain how you intend to get your pictures into either of these formats if you will obtain them initially in
some other format like a .bmp or .tif file you would get from a scanner, for example.
and purpose of the application here, before you actually compile your web pages. It’s no use unless you
design to have such things in your web site: if you include them later anyway, like rabbits pulled out of a
hat, with no prior mention of their presence or purpose, you will get no marks for it.
In other words, you should explain where components come from, how they are collected and stored, how
they are treated and how they are stored and utilised once treated. The difference between this section and
the Analyse section is largely one of detail. In Analyse, you state what you want to achieve, in broad
terms. In Design, you must state every detail of what you intend to do. You should particularly explain
any features you’re designing that make things easier or more straightforward for your intended user(s),
or features that will make your pages load faster by causing their source code to be as lean as possible.
Last of all in this section, there must be a testing plan that you will carry out when you’ve actually set all
of this up. You must test whether each hyperlink works, you must test (if you have them) any mouse
include. You can’t give any results of tests in this section because you haven’t yet compiled your web
Each test you plan in advance ought to have a number; you must describe what the test will entail, and
you must describe the result you expect for your test if all goes well.
DETAILS OF THE ‘USE / IMPLEMENT’ SECTION
This is where you actually get to produce files in your chosen software application, and test that they
You must produce a word-processed section of work explaining all of the processes you mentioned first
in the Analyse section and then in the Design section; the text in this word-processed material must be
interspersed with printouts of the web pages.
You won’t have been able to do the work absolutely perfectly at the first attempt. No doubt, you’ll make
mistakes. This is quite O.K…………
Just make sure you never throw away any printout. Every printout you get should have your name
written on the back as soon as you get it out of the printer. You should also number the printouts by hand,
on the non-printed side. Every time you correct a mistake, you should annotate the old printout to indicate
where the mistake was, you should annotate the new printout to show how the mistake has been
corrected, and you should include in your word-processed document a description in words of what the
mistake was and how you corrected it.
You’ll have to be very organised to be able to do this, but you can score highly if there is physical
evidence that some correction cycle has taken place. If you are the sort of person who loses papers, can’t
organise anything in a logical order and is unable to spot mistakes, then you’ll only have yourself to
blame if you can’t cope with this section. It’s much easier to be disorganised, rather than organised. These
skills can’t be taught – either you’re prepared to make the effort, or you’re not.
Finally, in this section, you must give, test-by-test, results of the tests you planned in the Design section.
If you get the results you expected, you must say so. If you get unexpected results, you must give details
of any steps you take to put things right. You must then do the test again and confirm that you actually
got the result you originally expected. If you still don’t get the result you expected, you must have another
go at putting things right………..and so on!
Before you go any further, you must give all
the work you’ve done so far to the person who
is role-playing the part of your intended user.
You will get back a piece of paper with the
opinion and constructive criticism of your
intended user. This paper must be included in
the next (Evaluate) section.
DETAILS OF THE ‘EVALUATE’ SECTION
You must include, first of all, the written comments from your (role-played) intended user. You must
write a commentary to show how well (or otherwise, with reasons) your solution performed when the
intended user had to use it or otherwise rely on it to carry the intended task. You must describe details of
any improvements you would make (there will be some) in the light of your intended user’s comments.