Testing a solution - CCEAEvaluating your solution

Once the development stage is complete you must complete integration, system and acceptance testing on your code and evaluate your solution.

Part ofDigital Technology (CCEA)Digital development practice (programming)

Evaluating your solution

The final component of the Controlled Assessment requires you to evaluate your solution to the task set by CCEA. The evaluation should refer to the user requirements and show how you met them.

Your evaluation should also consider any elements that failed tests and how you attempted to solve these. Finally, you should come up with recommendations to make the software better.

Here are some words that you could use to help form your comments:

SaveFindUseGenerateDevelopOrganiseShare
ExchangeControlAchieveSolveDescribeCombineIdentify
SelectTranslateMeasureRecordAnalyseDesignConsider
ApplyReasonUnderstandCollectInterrogateQuestionRecognise
AddAmendCombineSenseExplorePredictCompare
OrganiseStructureFunctionAssessRefineEnquireVary
Save
Find
Use
Generate
Develop
Organise
Share
Exchange
Control
Achieve
Solve
Describe
Combine
Identify
Select
Translate
Measure
Record
Analyse
Design
Consider
Apply
Reason
Understand
Collect
Interrogate
Question
Recognise
Add
Amend
Combine
Sense
Explore
Predict
Compare
Organise
Structure
Function
Assess
Refine
Enquire
Vary

You should evaluate the success of your program and comment on how useful it might be to a real end user. Consider the following:

1. User interface: Strengths, weaknesses and improvements

Evaluate the effectiveness of your user interface.

  • Is it user friendly, if so how?
  • What components make it user friendly?
  • Quality of graphics – are they appropriate for the end user/audience?
  • Is it intuitive (will people know what to do automatically)? If so, how/why?
  • Is your accessible for users with special considerations (visually impaired, hearing impaired, issues with dexterity/use of hands)?
  • Does the user interface provide feedback (error messages/text output on screen)?
  • Is it informative (does it explain how to use the system)?
  • Is it too complex?
  • How does your user interface compare to a professionally produced program?
  • How would you improve the layout/appearance/functionality of your user interface?
  • What elements of a typical or have/would you include and why?
  • Is the interface cluttered or organised?
  • Is the user interface intuitive – will users be familiar with the concepts of your user interface or is there a steep learning curve?

2. Programming techniques used and efficiency of your code: Strengths, weaknesses and improvements

Evaluate your programming techniques in detail.

  • What techniques did you employ and why? Think: (, ), (, ), , lists, functions/procedures, unique elements and libraries of your chosen language.
  • Is your solution efficient?
  • Is it fully functional?
  • Is your code organised?
  • Could it be more readable?
  • Is your code clearly commented?
  • Is your logic and reasoning clear or complex?
  • Could you implement a simpler algorithm to solve some of the issues?

You must evaluate all major functions and scripts in your final coded solution.

3. The IDE used

Evaluate the features of the programming environment you used.

  • What features did you use? For example, / // / .
  • What were the advantages/disadvantages of the features that you used?
  • Was the IDE accessible/easy to use?
  • How did you develop your skills?
  • What problems did you encounter with your chosen IDE?

You will need to finish your evaluation with a final paragraph or conclusion summing up every aspect listed above.