User-centred design
Designing a solution around the needs of its real users, by finding out what they need and involving them throughout development, using their feedback to revise the design.
Understanding User-centred design in VCE Software Development U4O1
What it does: The code shows users trying a prototype and giving feedback, which is how users are involved in development. The design is updated using the feedback, which completes the user-centred design cycle. Surveys, interviews and observation find out what users actually need. Feedback is used to revise the design. A working program can still fail its users. The real users, here students and canteen staff, determine the needs the design must meet. Users try the prototype and their comments show what to improve. Revisions are driven by user needs, not by adding features for their own sake.
Common mistakes: Lists have no .len() method. Use len(feedback) to count how many pieces of user feedback were collected. The loop should print each single need, so it must use the loop variable need. Printing needs shows the whole list every time.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 3–79) and word search (Modules 3–114).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
user-centred designFill in the Blanks
Spot the Error
Student with a class code? Join your class →