Year 11 · ICT · Summer 2
After the exams · Lesson 5 of 5
Course evaluation
Theory7.6 Evaluation
Year 11 · ICT · After the exams · Lesson 5 of 5
You will learn to
- Evaluate the course: what helped you learn, and what did not.
- Identify the hardest topic or skill and the most useful lesson, with a reason for each.
- Suggest one change for next year's Year 11.
Year 11 · ICT · After the exams · Lesson 5 of 5
Success criteria
You have got it when you can say:
- I can give one specific example of something that helped me learn.
- I can name the hardest topic or skill and say why it was hard.
- I can write one clear, kind suggestion for next year.
Year 11 · ICT · After the exams · Lesson 5 of 5
Retrieval starter
Questions from before. Write your answers, then show them.
- Last unit
Job sharing means…
A Two people share one full-time jobB Working nightsC Working from home
A. Two people share one full-time job
- Last year
Selecting Year = 8 before merging…
A Changes the letter textB Sends letters only to Year 8C Prints everything twice
B. Sends letters only to Year 8
- Last unit
A foreign key…
A Links a record to a record in another tableB Is always uniqueC Is a password
A. Links a record to a record in another table
Year 11 · ICT · After the exams · Lesson 5 of 5
Key words (1 of 2)
- Questionnaire
- A set of written questions given to many people to collect their views.
- System specification
- A list of the hardware and software the new system needs.
- Check digit
- An extra digit calculated from the other digits, used to detect input errors.
- Test plan
- A table listing each test, its data, the expected and actual outcomes and any remedial action.
Year 11 · ICT · After the exams · Lesson 5 of 5
Key words (2 of 2)
- Live data
- Real data from the organisation, used to test the system with known results.
- Evaluation
- Judging the finished system against the original requirements after it has been used.
The explanation · step 1 of 2 · part 1 of 2
What evaluation checks
Evaluation happens after the system has been in use for a while. It asks: does the new system do the job well?
Efficiency: is it faster or cheaper than the old system? Does it use fewer resources?
Ease of use: can staff use it with little training? Do they make fewer mistakes?
Appropriateness: is it the right solution for this organisation and its problems?
The explanation · step 1 of 2 · part 2 of 2
What evaluation checks (continued)
The explanation · step 2 of 2 · part 1 of 2
How it is done and what comes next
The analyst compares the final system with the original user requirements from the analysis stage, one by one.
The analyst gathers user feedback by interviews and questionnaires, and compares results from the test plan.
Any limitations found are listed, with improvements to fix them. This may start the life cycle again.
The explanation · step 2 of 2 · part 2 of 2
How it is done and what comes next (continued)
The requirements written in analysis are the yardstick. Without them, there is no fair way to say whether the system succeeded.
Evaluation is not testing. Testing happens before the system goes live. Evaluation happens after it has been used for real.
Year 11 · ICT · After the exams · Lesson 5 of 5
Homework and the challenge
Homework
None.
End-of-unit challenge
No test. A showcase.