All posts by Deleted User

How to produce a good evaluation
Evaluations are always badly written as most students believe that they are writing about what they DID and not whether they did what they were supposed to do. Comments like ‘If I had more time’ or ‘I was doing well until the printer broke down’ should now be a thing of the past as there is no formal project at AS level, although they still could appear at A2 level. You are not writing about what you learnt by doing the task, how you used the
packages, a lack of time or how much help you were given.

Your testing consists of three main elements:
• Testing using the performance indicators (within analysis) to prove that your solution does what your client wants it to do.
• Testing through development; this is testing the solution as you develop it.
• Testing during operation; this is using the test plan.
▫ During this section we can test the solution further.
▪ Unit testing – each individual element is tested and then the elements combined are                tested to check the data flows properly.
▪ System testing – the whole system is tested.
• User testing – this is where the end user tests the system as though it were in real life to see if everything works as it should.

A test plan uses test data that ensures:
• The validity of the data input.
• The accuracy of the data input.
• The presentation of the output.
• That the solution meets the needs of the client.
• That the solution is usable by the end user and / or intended audience.
• That it incorporates the data to be used for testing the solution and the expected results of each test.

Evaluation is very important as it looks back at the work that has been produced and reviews the progress in meeting the requirements set by the client. In order to produce a good evaluation you need to understand what  has been done and any mistakes you have made must be corrected.