Use the notes within this page to help structure the Evaluation section of your programming project. There are no set determined number of pages for this section.

3.4 Evaluation

Structure and Description of content needed for Programming Project
Evaluation

3.4.1 Testing to inform the evaluation as part of the evaluation process you are now ready to prove that the solution you have created works and meets the criteria you agreed in the analysis section of the project. This should be a methodical process that clearly evidences what has been achieved with visual evidence to prove that ALL SUCCESS CRITERIA have been ACHIEVED or ATTEMPTED by including the following:

  • Dedicated TEST TABLE to prove EACH SUCCESS CRITERION. This should be written in detail to explain each test to a layman could conduct the test and arrive at the correct outcome. EACH test must use NORMAL/ BOUNDARY/ ERRORNEOUS test data.

3.3.2 Testing to inform development 

Testing
During your Development Log you should give evidence of testing. Ideally this should be formalised testing using a testing table for each stage in the development, At the very least you should DESCRIBE and ANNOTATE what you are testing and how you will test that specific area. 

Fixes
You will need to identify and record ACTION you have taken to fix problems. You should state:

  • What the problem was.
  • What it was related to. 
  • How you identified the problem (what test)
  • How you have fixed it.
  • Justify why you needed to fix it to meet your success criteria