Active learning ideas
Evaluating digital solutions is the final, critical stage of the development cycle. Students must step back from their creations and objectively assess whether they have met the initial user requirements and prescribed criteria. This involves rigorous testing, using data-driven methodologies to find bugs, and gathering user feedback to identify areas for improvement. It is not just about checking if the code works; it is about checking if the solution actually solves the problem for the intended audience.
Activity 01
Students swap their completed applications with a partner. Each student has 15 minutes to try and 'break' the other's program by entering unexpected data (e.g., letters in a number field). They record every 'bug' found in a formal testing log for their partner to fix.
How do we measure the success of a digital solution?
Activity 02
Applications are set up around the room. Students move from station to station, spending 5 minutes using each app and providing feedback on a 'Plus/Delta' sheet (what worked well and what could be changed), focusing on the user interface and data accuracy.
What testing methodologies ensure robustness?
Activity 03
After receiving peer feedback, students individually list three 'must-have' refinements and three 'nice-to-have' features. They share their roadmap with a partner to justify why they are prioritising certain changes over others based on the original user requirements.
How does user feedback inform refinements?
A few notes on teaching this unit
Watch Out for These Misconceptions
Testing is only done at the very end of the project.
Students often leave testing until it's too late to fix major issues. Active 'sprint reviews' throughout the project help them see that testing should be an ongoing, iterative process that informs development at every stage.
User feedback is just 'opinions' and isn't as important as technical criteria.
A technically perfect app that no one can use is a failure. Role-playing 'client meetings' where students must defend their design choices against user complaints helps them value the 'human' side of evaluation.
Methods used in this brief
Data and information
Students explore how data is collected, stored, and transmitted in digital systems. They analyse the difference between raw data and meaningful information.
8 methodologies
Relational database concepts
Students design relational databases using entity-relationship diagrams and data dictionaries. They understand primary keys, foreign keys, and data integrity.
8 methodologies
Data-driven programming
Students write code to interact with databases, performing CRUD operations. They use SQL and programming logic to manipulate data.
8 methodologies