Why is "Describing the solution instead of evaluating it." a common mistake in Reviewing outcomes?

Why it happens: Evaluation feels like explaining what it does. How to avoid it: Evaluate = JUDGE against criteria, weigh strengths vs weaknesses, give a verdict and recommendations. Use words like 'however', 'therefore'. Source: Edexcel 4IT1 examiner reports — candidates describe rather than evaluate.

Why is "Only testing with normal data." a common mistake in Reviewing outcomes?

Why it happens: Normal data is easiest. How to avoid it: Always test all three: NORMAL, BOUNDARY (both edges), and ERRONEOUS data. Boundary and erroneous reveal the real faults. Source: Edexcel 4IT1 examiner reports.

Why is "Test plans with no expected result." a common mistake in Reviewing outcomes?

Why it happens: Listing test data only. How to avoid it: A test must state the EXPECTED result so you can compare it with the actual result and decide pass/fail.

Why is "Vague recommendations ('make it better/faster')." a common mistake in Reviewing outcomes?

Why it happens: Not linking to evidence. How to avoid it: Recommend SPECIFIC improvements justified by the evaluation ('migrate to a database to handle 6,000 records and enforce integrity').

Why is "Evaluating without reference to the original requirements." a common mistake in Reviewing outcomes?

Why it happens: Forgetting the success criteria. How to avoid it: Always evaluate AGAINST the stated requirements/criteria — that is what 'fit for purpose' means.

Applying Information and Communication TechnologyPearson Edexcel IGCSE ICT 4IT1

Reviewing outcomes

Work through the notes, try the practice questions, then take the quiz. The report tells you exactly what to revise next.

PreviousNext

Learn this Topic

Start with the slides for the quick version, then go deeper with the full study notes.

Short Study Notes in the form of Slides

Read the notes first. If the method in a worked example clicks, you're ready for the questions.

Short Study Notes — Reviewing outcomes

Start with these resources to cover the key concepts, then work through the practice questions.

Page 1 / 0

Detailed Notes

Full prose, callouts and a recap — built for A* mastery, not just a quick scan.

Take these study notes with you

Download a branded PDF — full prose, callouts, recap and memorise list for Reviewing outcomes, ready to print or save offline.

Reviewing Outcomes — Edexcel IGCSE ICT (4IT1) Detailed Notes

How to evaluate an ICT solution: testing with the right data, judging fitness for purpose, gathering and analysing feedback, and recommending improvements. The evaluation skill that separates top grades.

What you’ll learn

Mapped to the Pearson Edexcel IGCSE 4IT1 syllabus (2026 onwards).

Test a solution with normal, boundary and erroneous data.
Construct a test plan with expected results.
Evaluate a solution against criteria and requirements.
Judge fitness for purpose.
Gather and analyse user feedback.
Recommend justified, prioritised improvements.

What is evaluation?

Judge against requirements; don't just describe.

Evaluation = judging whether a solution meets its requirements and is fit for purpose, then recommending improvements.

Key difference — describe vs evaluate:

DESCRIBE: 'The spreadsheet stores donor records and prints letters.'
EVALUATE: 'It works for the basic task, HOWEVER it struggles with 6,000 records and lacks data integrity, THEREFORE a database would be more fit for purpose.'

Evaluation criteria:

Functionality — does it do everything required?
Usability — easy for intended users?
Accuracy — correct results?
Reliability — works without crashing?
Efficiency — fast; good use of resources?
Cost / time — within budget; on schedule?
Scalability — copes with growth?
Compliance — meets legal needs (GDPR)?

Always evaluate AGAINST the original requirements/success criteria. That is the meaning of 'fit for purpose'.

Testing

Run the solution with planned data before release.

Testing checks a solution works correctly and meets requirements BEFORE real users rely on it.

Three types of test data:

Normal (valid) data — typical acceptable input. Example: age 50 in a 0–120 field → accepted.
Boundary (extreme) data — values at the EDGES of the range, tested on BOTH sides. Example: 0 and 120 (accepted); −1 and 121 (rejected).
Erroneous (abnormal) data — invalid input the system should reject. Example: text in a number field, blank required field, out-of-range value.

A test plan needs: what is being tested, the test data, the EXPECTED result, the actual result, and pass/fail.

Types of testing:

Functional — each feature works.
Validation — invalid data rejected, valid data accepted.
Usability — easy to use.
Reliability / load — works under heavy use without crashing.

Why test thoroughly? To find faults before users do, confirm requirements are met, and ensure accuracy and reliability.

Gathering and analysing feedback

Use real user input to evaluate and improve.

Feedback = information from users used to evaluate and improve a solution.

Methods:

Questionnaire / survey — reaches MANY users; quantitative; quick to analyse. Weakness: shallow, low response rates.
Interview — one-to-one; DEEP, detailed; can probe. Weakness: time-consuming; few people.
Observation — watch real use; reveals actual behaviour and problems users don't report. Weakness: people may act differently when watched.
Focus group — group discussion; varied views. Weakness: dominant voices skew it.
Analytics — automatic usage data (load times, click paths, abandonment). Objective and large-scale.

Quantitative vs qualitative:

Quantitative = numbers (ratings, %). Easy to compare.
Qualitative = opinions/comments. Rich detail.
Best evaluations use BOTH.

Analysing feedback:

Quantify issues (e.g., 'cart abandonment 68%').
Find patterns and root causes.
Compare results against TARGETS.
Rank issues by impact and effort.

Weighted mean for ratings: Mean = Σ(value × frequency) ÷ Σ(frequency).

Recommending improvements

Specific, justified, prioritised — then re-evaluate.

After evaluation, recommend improvements that are specific and justified by the evidence.

Avoid vague recommendations ('make it faster'). Instead: 'Compress mobile images and add caching to cut load time from 6s to under 2s.'

Prioritise by impact vs effort:

High impact + low/medium effort → do FIRST.
High impact + high effort → plan carefully.
Low impact → defer.

Justify each recommendation by linking it to a weakness found in the evaluation and the benefit it brings.

Example (charity spreadsheet): 'Migrate to a database — it handles 6,000+ records, enforces data integrity, supports complex queries and provides an audit trail for GDPR, addressing the volume, integrity and compliance weaknesses.'

The review cycle is iterative: Evaluate → identify weaknesses → improve → RE-MEASURE → repeat. Re-measuring after a change confirms it actually worked — this is continuous improvement.

How it’s examined

Paper 1: Identify test-data types (4–6 marks); construct/complete a test table (4–6 marks); evaluate fitness for purpose (8 marks); recommend improvements (6–8 marks); choose/justify a feedback method (4 marks).

Paper 2 (practical): Test your own solutions with appropriate data; check outputs are correct; refine the solution based on results.

Frequent stems: 'State the type of test data…', 'Complete the test table…', 'Evaluate whether… is fit for purpose…', 'Recommend improvements to…'

Sources: Pearson Edexcel International GCSE in Information and Communication Technology (4IT1) Specification — Issue 3; Edexcel 4IT1 Examiner Reports (2022–2024). Last reviewed 2026-05-20.

Master this Topic

Worked examples, formulae, definitions and the mistakes examiners flag — everything you need to push from a pass to an A*.

Take this whole topic with you

Download a branded revision sheet — worked examples, formulae, definitions and common mistakes for Reviewing outcomes, ready to print or save as PDF.

Step-by-step worked examples — Reviewing outcomes

Step-by-step solutions to past-paper-style questions on reviewing outcomes, written exactly the way a tutor would explain them at the board.

1Identify the evaluation criterion being described
Getting started• Edexcel 4IT1 style — short-answer (6 marks)• evaluation-criteria, AO1
Question
Name the evaluation criterion: (a) Does the solution do everything it was meant to do? (b) Is it easy for the intended users to operate? (c) Does it produce correct results? (d) Does it work without crashing? (e) Was it delivered within budget and on time? (f) Can it cope with more data/users in future?
Step-by-step solution
1. Step 1
  Match each description to its evaluation criterion.
Answer
(a) Functionality / meeting requirements.

(b) Usability / ease of use.

(c) Accuracy.

(d) Reliability.

(e) Cost and time (efficiency / value).

(f) Scalability.
Examiner tip
Evaluation criteria: functionality, usability, accuracy, reliability, efficiency, cost/time, scalability, fitness for purpose.
2Identify the type of test data
Building confidence• Edexcel 4IT1 style — short-answer (6 marks)• test-data, AO1
Question
A field accepts ages 0–120. Classify each test value: (a) 50. (b) 0 and 120. (c) −1 and 121. (d) 'abc' (text in a number field). (e) (blank). (f) 60 (when the real age is 60).
Step-by-step solution
1. Step 1
  Normal, boundary, erroneous/abnormal, and verification data.
Answer
(a) 50 → Normal / valid data (typical accepted value).

(b) 0 and 120 → Boundary / extreme data (edges of the allowed range).

(c) −1 and 121 → Erroneous / abnormal data (should be rejected).

(d) 'abc' → Erroneous data (wrong type — should be rejected).

(e) blank → Erroneous data (presence check should reject).

(f) 60 matching the source → tests accuracy / verification, not validation.
Examiner tip
Test data types: NORMAL (typical valid), BOUNDARY (edge of range — both sides), ERRONEOUS/ABNORMAL (should be rejected). Test all three.
3Identify the feedback-gathering method
Building confidence• Edexcel 4IT1 style — short-answer (5 marks)• feedback-methods, AO1
Question
Name the feedback method: (a) A set of written questions sent to many users. (b) A one-to-one spoken conversation with a user. (c) Watching users as they use the system. (d) An online form with rating scales. (e) A group discussion with several users.
Step-by-step solution
1. Step 1
  Standard feedback-collection methods.
Answer
(a) Questionnaire / survey.

(b) Interview.

(c) Observation.

(d) Online survey / feedback form.

(e) Focus group.
Examiner tip
Questionnaires reach many users (quantitative); interviews/focus groups give depth (qualitative); observation reveals real behaviour.
4Calculate test coverage
Building confidence• Edexcel 4IT1 style — calculation (5 marks)• test-coverage, AO1, AO2
Question
A test plan has 40 test cases. After running them: 34 passed, 6 failed. Calculate: (a) The pass rate as a percentage. (b) The fail rate as a percentage. (c) If 4 of the 6 failures are fixed and retested successfully, the new pass rate.
Step-by-step solution
1. Step 1
  Pass rate = passed ÷ total × 100.
Answer
(a) Pass rate = 34 ÷ 40 × 100 = 85%.

(b) Fail rate = 6 ÷ 40 × 100 = 15%.

(c) New passes = 34 + 4 = 38; new pass rate = 38 ÷ 40 × 100 = 95%.

Tracking pass/fail rates across test cycles shows whether the solution is improving toward release readiness.
Examiner tip
Show working: passed ÷ total × 100. State the unit (%). Retesting after fixes is called regression/confirmation testing.
5Calculate feedback rating averages
Higher• Edexcel 4IT1 style — calculation (5 marks)• feedback-analysis, AO1, AO2
Question
20 users rated a website 1–5 for ease of use: 5 stars: 8 users; 4 stars: 6 users; 3 stars: 4 users; 2 stars: 1 user; 1 star: 1 user. Calculate (a) the mean rating, (b) the percentage who rated 4 or 5, (c) state whether this meets a target mean of 4.0.
Step-by-step solution
1. Step 1
  Mean = Σ(rating × count) ÷ total users.
Answer
(a) Total points = (5×8)+(4×6)+(3×4)+(2×1)+(1×1) = 40+24+12+2+1 = 79. Mean = 79 ÷ 20 = 3.95.

(b) Rated 4 or 5 = 8 + 6 = 14 users; 14 ÷ 20 × 100 = 70%.

(c) Mean 3.95 < target 4.0 → the target is NOT quite met (just below). Recommendation: gather feedback on the low scorers and improve usability.
Examiner tip
Weighted mean = Σ(value × frequency) ÷ Σ(frequency). Always compare results against the stated target/requirement.
6Calculate the impact of an improvement
Higher• Edexcel 4IT1 style — calculation (5 marks)• improvement-impact, AO1, AO2, AO3
Question
A manual process takes 8 minutes per record for 500 records per week. A new automated solution takes 30 seconds per record. Calculate: (a) Weekly time for the manual process (hours). (b) Weekly time for the automated process (hours). (c) The percentage time saved.
Step-by-step solution
1. Step 1
  Time = per-record × number of records; convert to hours.
Answer
(a) Manual = 8 min × 500 = 4,000 min = 4,000 ÷ 60 = 66.67 hours.

(b) Automated = 30 s × 500 = 15,000 s = 15,000 ÷ 3,600 = 4.17 hours.

(c) Time saved = 66.67 − 4.17 = 62.5 hours; % saved = 62.5 ÷ 66.67 × 100 = 93.75% (≈ 94%).

Quantifying the benefit (≈94% time saved) is strong evidence the solution is fit for purpose.
Examiner tip
Quantified benefits ('saves 94% of time') score higher than vague claims ('it's faster'). Convert units carefully (min→hours, s→hours).
7Design a test plan
Higher• Edexcel 4IT1 style — extended (8 marks)• test-plan, AO1, AO2, AO3
Question
A school has built an online form for parents to book parents-evening slots. Describe how you would test it, including types of test data and what to check.
Step-by-step solution
1. Step 1
  Plan: what to test, test data types, expected results, and checks.
Answer
Test plan for the booking form:

1. Functional testing — does each feature work?

Can a parent select a teacher and a free slot?

Does booking remove that slot from availability?

Is a confirmation shown/emailed?

2. Validation testing — with three test-data types:

Normal data: a valid name, email, and free slot → should be ACCEPTED.

Boundary data: earliest and latest available slots; maximum-length name → should be accepted.

Erroneous data: blank name (presence check), invalid email format (format check), an already-booked slot (lookup check) → should be REJECTED with a clear message.

3. Usability testing.

Is the form clear and easy to complete on phone and desktop?

Are error messages helpful?

4. Accuracy/verification.

Does the confirmation match what was booked?

Does the teacher's schedule show the correct parent and time?

5. Reliability/load.

Does it work when many parents book at once (no double-booking)?

6. Test table.

Test Data Expected Actual Pass/Fail
Valid booking Normal Slot booked … …
Blank name Erroneous Rejected … …
Double booking Erroneous Blocked … …

Why test thoroughly: to confirm the solution meets requirements, is reliable and accurate, and to find faults BEFORE real users do.
Examiner tip
A* test plans (1) cover functionality, validation (3 data types), usability and reliability, (2) state EXPECTED results, (3) use a test table.
8Evaluate whether a solution is fit for purpose
Higher• Edexcel 4IT1 style — evaluate (8 marks)• evaluation, fitness-for-purpose, AO1, AO2, AO3
Question
A charity built a spreadsheet to manage 6,000 donor records and send thank-you letters. Evaluate whether this solution is fit for purpose and recommend improvements.
Step-by-step solution
1. Step 1
  Judge against criteria; give a justified verdict + recommendations.
Answer
Evaluation against criteria:

Functionality: A spreadsheet can store records and (via mail merge) generate letters — the basic task works. ✓ partial.

Volume/scalability: 6,000 records strain a spreadsheet; searching/sorting becomes slow and it won't scale as donors grow. ✗

Data integrity: Spreadsheets lack enforced relationships and strong validation — easy to enter duplicate or inconsistent data, or overwrite cells by accident. ✗

Usability: Fine for a skilled user but error-prone for others; no guided forms. ✗ partial.

Querying: Limited compared with a database; complex donor segmentation is hard. ✗

Compliance (GDPR): Poor audit trail and access control for personal data. ✗

Verdict: NOT fully fit for purpose. It works for the immediate task but is risky and won't scale.

Recommendations:

Migrate to a database/CRM for integrity, querying, multi-user access and audit trails.

Use forms with validation to reduce entry errors.

Keep mail merge for letters (it works well).

Add access control and backups for GDPR compliance.

Justification: the database addresses the volume, integrity, querying and compliance weaknesses while keeping the working mail-merge feature.
Examiner tip
Evaluation = judgement against criteria + JUSTIFIED verdict + specific recommendations. Don't just describe; weigh strengths vs weaknesses and conclude.
9Use feedback to recommend improvements
Stretch• Edexcel 4IT1 style — extended (8 marks)• feedback, improvement, AO1, AO2, AO3
Question
After launching a new e-commerce website, feedback shows: checkout is confusing (many abandon carts), the site is slow on mobile, and customers want more payment options. Describe how you would gather more feedback, analyse it, and recommend prioritised improvements.
Step-by-step solution
1. Step 1
  Gather → analyse → prioritise → recommend with justification.
Answer
1. Gather more feedback (multiple methods).

Analytics: measure cart-abandonment rate, page-load times, device breakdown (quantitative).

Surveys: short on-site survey at checkout ('what stopped you?').

Usability testing: observe real users completing a purchase.

Reviews/support tickets: mine existing complaints.

2. Analyse the feedback.

Quantify each issue (e.g., 'cart abandonment 68%', 'mobile load 6s vs 2s target').

Identify patterns and root causes (too many checkout steps; large unoptimised images on mobile).

Rank by IMPACT (on sales) and EFFORT (to fix).

3. Prioritise improvements (impact vs effort).

High impact / urgent: simplify checkout to fewer steps + guest checkout (directly reduces abandonment).

High impact: add payment options (PayPal, Apple Pay) — removes a stated barrier.

Medium: optimise mobile (compress images, responsive design, caching) to cut load time.

4. Recommendations with justification.

Fix checkout FIRST — biggest revenue impact for moderate effort.

Add payment methods — directly requested, increases conversions.

Improve mobile performance — growing share of traffic.

5. Re-evaluate (iterate).

After changes, re-measure abandonment, load time and satisfaction to confirm improvement (the review cycle repeats).

Why this works: decisions are EVIDENCE-BASED (data + feedback), PRIORITISED by impact, and VERIFIED by re-measuring — a continuous improvement cycle.
Examiner tip
A* answers (1) use MULTIPLE feedback methods incl. quantitative data, (2) PRIORITISE by impact vs effort, (3) JUSTIFY recommendations, (4) close the loop by re-evaluating.

Test	Data	Expected	Actual	Pass/Fail
Valid booking	Normal	Slot booked	…	…
Blank name	Erroneous	Rejected	…	…
Double booking	Erroneous	Blocked	…	…

Key Formulae — Reviewing outcomes

The formulae you need to memorise for reviewing outcomes on the Pearson Edexcel IGCSE 4IT1 paper, with every variable defined in plain English and a note on when to use it.

Test pass rate
$Pass rate (%) = (tests passed ÷ total tests) × 100$
When to use
Measuring how much of a test plan succeeds.
Example
34 ÷ 40 × 100 = 85%.
Weighted mean (ratings)
$Mean = Σ(value × frequency) ÷ Σ(frequency)$
When to use
Averaging rating-scale feedback.
Example
[(5×8)+(4×6)+(3×4)+(2×1)+(1×1)] ÷ 20 = 3.95.
Percentage time/cost saved
$Saving (%) = (old − new) ÷ old × 100$
When to use
Quantifying the benefit of an improvement.
Example
(66.67 − 4.17) ÷ 66.67 × 100 ≈ 94%.

Key Definitions and Keywords — Reviewing outcomes

Definitions to memorise and the exact keywords mark schemes credit for reviewing outcomes answers — sharpened from recent examiner reports for the 2026 Pearson Edexcel IGCSE 4IT1 sitting.

Evaluation
Examiner keyword
Judging whether a solution meets its requirements and is fit for purpose, against defined criteria, leading to recommendations.
Fitness for purpose
Examiner keyword
Whether a solution actually meets the user's real needs and requirements.
Testing
Examiner keyword
Running a solution with planned data to check it works correctly and meets requirements before release.
Normal (valid) data
Examiner keyword
Typical, acceptable input that the system should process correctly.
Boundary (extreme) data
Examiner keyword
Values at the edges of the accepted range, tested on both sides to check limits.
Erroneous (abnormal) data
Examiner keyword
Invalid input that the system should reject (wrong type, out of range, blank).
Usability
Examiner keyword
How easy and intuitive a solution is for its intended users to operate.
Reliability
Whether a solution works consistently without errors or crashes.
Feedback
Examiner keyword
Information gathered from users (surveys, interviews, observation, analytics) used to evaluate and improve a solution.
Iterative review
Repeatedly evaluating and improving a solution in cycles, re-measuring after each change.

Common Mistakes and Misconceptions — Reviewing outcomes

The traps other students keep falling into on reviewing outcomes questions — taken from recent Pearson Edexcel IGCSE 4IT1 examiner reports and mark schemes — and how to avoid them.

✕Describing the solution instead of evaluating it.
Edexcel 4IT1 examiner reports — candidates describe rather than evaluate.
Why it happens
Evaluation feels like explaining what it does.
How to avoid it
Evaluate = JUDGE against criteria, weigh strengths vs weaknesses, give a verdict and recommendations. Use words like 'however', 'therefore'.
✕Only testing with normal data.
Edexcel 4IT1 examiner reports.
Why it happens
Normal data is easiest.
How to avoid it
Always test all three: NORMAL, BOUNDARY (both edges), and ERRONEOUS data. Boundary and erroneous reveal the real faults.
✕Test plans with no expected result.
Why it happens
Listing test data only.
How to avoid it
A test must state the EXPECTED result so you can compare it with the actual result and decide pass/fail.
✕Vague recommendations ('make it better/faster').
Why it happens
Not linking to evidence.
How to avoid it
Recommend SPECIFIC improvements justified by the evaluation ('migrate to a database to handle 6,000 records and enforce integrity').
✕Evaluating without reference to the original requirements.
Why it happens
Forgetting the success criteria.
How to avoid it
Always evaluate AGAINST the stated requirements/criteria — that is what 'fit for purpose' means.

Practice questions

Exam-style questions with step-by-step worked solutions. Try one before checking the method.

Past paper style quiz

Get a report showing which sub-topics you've nailed and which ones still need work.

Reviewing outcomes

Short Study Notes in the form of Slides

Short Study Notes — Reviewing outcomes

Detailed Notes

What you’ll learn

How it’s examined

1Identify the evaluation criterion being described

2Identify the type of test data

3Identify the feedback-gathering method

4Calculate test coverage

5Calculate feedback rating averages

6Calculate the impact of an improvement

7Design a test plan

8Evaluate whether a solution is fit for purpose

9Use feedback to recommend improvements

Test pass rate

Weighted mean (ratings)

Percentage time/cost saved

Evaluation

Fitness for purpose

Testing

Normal (valid) data

Boundary (extreme) data

Erroneous (abnormal) data

Usability

Reliability

Feedback

Iterative review

✕Describing the solution instead of evaluating it.

✕Only testing with normal data.

✕Test plans with no expected result.

✕Vague recommendations ('make it better/faster').

✕Evaluating without reference to the original requirements.

Practice questions

Past paper style quiz

Assess your understanding