Evaluation

1. Evaluation

2. Sub-stages • Discussion of the degree of success in meeting the original objectives • Evaluation of the client’s and user’s response to the system

3. Discussion of the degree of success in meeting the original objectives • CIE Computing Syllabus, Page 40:

4. Discussion of the degree of success in meeting the original objectives • CIE Computing Syllabus, Page 40: • Read page 322 - 323 (Text)

5. Evaluation of the client’s and user’s response to the system • CIE Computing Syllabus, Page 40:

6. Evaluation of the client’s and user’s response to the system • CIE Computing Syllabus, Page 40:

7. Degree of Success • A clear match between the agreed objectives and evidence that the objectives have been met • example: • Objective: System should be able to input data while ensuring that invalid data is rejected. • Result: Successfully achieved. • Evidence: See Page 9 for Input Form Design. See Page 67 for validation code that restricts invalid data in the fields of the form. • A discussion of the success or failure in meeting the objectives • The results that were obtained using “real” data rather than manufactured test data • Read Section 4.6 a 322 (Text)

8. Evaluation of the client’s and user’s response to the system • A letter from the client or end user stating that they have used the software solution and listing the things that they managed to do and those that they could not or features that need further work. • A completed questionnaire that helps the client or end user structure their responses about the solution. • Evidence to support the assertions made in the letter or questionnaire ( e.g. A printout showing an amendment to a record in the file) • An indication of the degree of success that you have achieved in the opinion of the client or end user • A description of how any inadequacies highlighted by the client or end user could be dealt with. • Desirable Extensions • What other features would you like to see in the new system? You do not have to be able to develop these features. • Feature list must be practical and related to the user’s requirements. • Read Section 4.6 b 322 - 323 (Text)

9. Evaluation of the client’s and user’s response to the system • The client or end user must indicate both that the solution is user friendly and that it fully meets the agreed specification. • To qualify for full marks, the syllabus states that there must be no known faults in the solution.

10. Project Approval Form • This should be used after every stage. • However, you must list ALL the deliverables you created. • Failure to list all may result in obtaining a lower mark. • Also put in a Project Approval Form immediately after the deliverable where it is absolutely necessary to have client approval (such as the Design Objectives, Output Design and Input Design.