Human computer interaction is about how easily a person can use a screen, a form or a message. In Computer Science answers, you judge a design against clear criteria and give evidence.
Check the current syllabus scope with your teacher and at bpk.moe.gov.my. The lessons below use original fictional examples and train the reasoning.
How do the four lessons connect?
Each lesson adds one step to the same habit: look, judge, design, then test.
- Evaluating clarity, feedback and navigation gives you the words to judge a screen.
- Designing an accessible input form applies those words to a design.
- Explaining usability decisions teaches how to write the reason behind a choice.
- Testing a prototype with observable tasks shows how to check a design with real users.
A worked example
A fictional school kiosk shows a single green button labelled “OK” after a student scans a library card. The screen does not say whether the loan succeeded.
The problem is weak feedback. The button tells the student to continue, but nothing confirms the action. A better message reads “Atlas borrowed. Due on 14 March”, followed by a clear next button.
Notice the pattern. Name the problem, locate it, give the principle and propose a fix. That four-part answer is the one the lessons practise.
Where should you start?
- If you can describe a screen but not judge it, begin with the evaluation lesson.
- If you can judge but struggle to design, go to the form lesson.
- If your answers list features without reasons, read the explaining lesson.
- If you want a check on everything, try the practice set.
The ideas also support web work, so see testing interaction and data validation when you are ready.
If you want a teacher to review your answers, see online one-to-one Computer Science tuition.