Reviewing (evaluating) your work
Are
you always sure that what you have done meets all the requirements for the
task? Of course not! It is always necessary to check that you have
done what you set out to do - and that it meets the requirements of the
task. Take this little example below where a user has set about installing
a game on their home computer. It is important that it will work correctly
later in the day when a friend comes round to play the game:
-
Buy the game CD from a computer game shop
-
Switch on the computer
-
Logon to the computer
-
Insert the CD in the CD drive of the computer
-
Wait for the auto install routine to start (if
it doesn't start then find te "setup.exe" program and start it
myself
-
Wait for the setup program to finish
-
Check that a new icon for the game has been
added to the Windows desktop
-
Logoff the computer and shut down.
The above list looks perfect - except one vital
step has been missed. How does the user know that the game will work
properly when the computer is switched back on. So step 9 should have
been: "Start the game to check it works
properly."
When you review (evaluate) your work - always
include the following in your notes:
 | What went well and what went badly? |
 | What new skills did you have to develop to do
the task/work? |
 | What existing skills did you find useful? |
 | What software and hardware did you use? |
 | Why did you choose to use one program instead
of others? |
 | What alternative ways could you have used when
doing the task? |
 | If you did the task again in what ways would
you do things the same - and what would be different? |
 | What have you done to improve your work as you
have been working through the task? |