Evaluation Guidelines

Expectations and Mark Scheme

Expectations

see marking scheme below.
always aim at the highest level.
please pay attention to the independent feedback point and think about how you are going to obtain that, i.e. peer review? target users review?

When marking your work, I will be checking…

have you given consideration as to how well the outcome meets the initial requirement?
have you reflected on the objectives originally set and considered how their solution measures up to those objectives?
have you obtained independent feedback and reflected upon this?

Mark Scheme

Evaluation (4 marks)

Effective Evaluation

If you have numbered your objectives and requirements you will find completing the Evaluation section much easier to complete and it will make it a lot easier for the teacher and moderator to follow.

There is no need to repeat evidence from your testing in this section, but you should refer back to the results.

Your evaluation must be critical. You should be honest and open as this will give you more to write about. It is good to talk about the errors and bugs that you have encountered along the way and this may also help when considering the limitations of of your project and what further development you would consider going forward.

Evaluating the Solution as a Whole

You should first evaluate your solution as a whole. Consider how well it solves the overall problem that your end-user(s) or stakeholders were experiencing or the problem that you were investigating.

Remember you need to be critical. Even is all of the requirements have been met you should consider what could be improved as well as the good features of the project. It is advised to bring in the opinions of your end-user(s), stakeholders or supervisor at this point to show their overall opinion of the project.

Evaluation How Well the Requirements Are Met

You will need to go through each of the requirements in your project and evaluate them in turn. When doing this you should:

Give your own critical evaluation - what are the positive and negatives of the solution/investigation for each objective?
Independent feedback - what does your end-user(s)/supervisor or another third party think of how well you have met each objective?
What is your evaluation of their feedback?
How could the system/investigation be improved?

You may wish to complete this as a table that maps against each of your objectives, or as written prose related to each of the objectives

When you are writing your evaluation you will need to make sure that for each objective you make sure that your write up includes the following features:

It mentions the objective(s) it is applied to
It is specific about why the solution meets the objective
It shows the limitations of the solution if applicable
It outlines how the solution could be improved
It explains that the achievements and improvements are grounded in Computer Science reasoning

Independent Feedback

Your evaluation needs to incorporate independent feedback from a third party. Ideally, this should be one of the end users for your solution or the supervisor of your investigation.

You will need to encourage the person giving you the feedback to be specific feedback that gives details of why a solution is good and what improvements could be made to it.

Good independent feedback should contain the following features:

It should mention the objective(s) it is applying to
It should be realistic and useful
It should give specific reasons why the system has performed/not performed well
It should give suggestions on how the system could be improved

Evaluation of Independent Feedback

To achieve the highest marks for the evaluation, you will need to discuss the feedback that you have been given.

You will need to write about whether you agree or disagree with the comments from the independent feedback, giving reasons and suggestions for how you could answer the writers suggestion in your project.

Presenting Your Evaluation

Structure

Organise your write up in three sub-sections:

- evaluate aganist the requirements/objectives - how well the outcome meet the requirements. Referring back to the tests you have done that show you have met certain requirements/objectives.
- future improvement/different approaches if were to re-visit the same problem with reasons.
- detailed and realistic independent review/critique of the outcome. Get some feedback from your intended users. This can be a survey, interview summaries.

A sensible approach would be to copy the objectives from the analysis into the evaluation so that each can be easily commented on. For each objective, the student could judge how effectively it has been met and also comment (if appropriate) on how the solution might be improved in this area.

The student should aim to explain, in outline, how they might go about implementing the possible improvements. It is important that any third party feedback obtained is analysed by the students, not simply included as, for example, an email from the person.

In addition to commenting on the individual objectives, students should also give an overview of the effectiveness of their solution, as it may be that some points would not be covered by commenting on the objectives alone. For example, some ideas for improving the system might be outside of the selected objectives.

The actual feedback obtained from the third party should be included in an appendix. If feedback was also obtained at an earlier stage in the production of the project, for example based upon a prototype, then this could be referenced to in this evaluation so that it could be considered for credit.

To Do List:

Evaluate how well each requirement/objectives have been met
Give reasons, including technical as to why parts of the solution have been programmed well or not so well
Identify areas of the solution that could be improved
Obtain independent feedback that is useful and realistic
Evaluate and discuss the independent feedback in a meaningful way

Page updated

Report abuse