Computer Science · Grade 10

Active learning ideas

Prototyping and Iterative Design

Active learning works for prototyping and iterative design because students must experience the discomfort of testing unfinished ideas and the satisfaction of improving them. By handling materials and seeing peers respond to their work, they grasp why quick, rough drafts beat polished but untested designs in real software projects.

• Ontario Curriculum Expectations
• CS.HS.D.3
• CS.HS.D.4

• 20–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Project-Based Learning
• 35 min · Pairs

Pairs: Paper App Prototype

Students pair up and sketch a paper prototype for a simple app solving a class-chosen problem, like a study planner. They role-play users navigating screens by flipping pages, note pain points on sticky notes, then iterate the design twice based on partner feedback. Pairs present final versions to the class.

Construct a prototype (paper or digital) for a proposed software solution.

Facilitation Tip

During Paper App Prototype, circulate with guiding questions like 'What problem does this screen solve?' to keep pairs focused on user goals rather than aesthetics.

What to look for

Present students with a scenario: 'You are designing a new mobile app for ordering groceries.' Ask them to sketch a single screen for this app as a low-fidelity prototype. Then, ask them to list two specific questions they would ask a user to get feedback on this sketch.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 02

• Project-Based Learning
• 45 min · Small Groups

Small Groups: Digital Wireframe Cycles

In small groups, students use a free tool like Figma to build a low-fidelity wireframe of their app. They conduct two feedback rounds: first with another group, then revise into a high-fidelity version. Groups demo changes and explain iteration decisions.

Evaluate the effectiveness of different prototyping methods for gathering user feedback.

Facilitation Tip

In Digital Wireframe Cycles, set a strict 15-minute timer for each wireframe version to prevent over-refinement before testing.

What to look for

Have students share their low-fidelity prototypes (paper or digital) with a partner. Instruct the assessor to provide feedback on two specific aspects: 1. Clarity of the main user flow. 2. Potential usability issues. The student receiving feedback should then list one change they will make based on this assessment.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 03

• Project-Based Learning
• 25 min · Whole Class

Whole Class: Feedback Carousel

Display all prototypes around the room. Students rotate every 5 minutes, leaving anonymous feedback on sticky notes about usability. After rotations, creators review notes and plan one iteration, discussing as a class how feedback drives design.

Explain how iterative design cycles lead to improved product outcomes.

Facilitation Tip

For Feedback Carousel, post the rotation schedule where everyone can see it to reduce transitions and maximize peer discussion time.

What to look for

Ask students to write one sentence explaining the primary difference between a low-fidelity and a high-fidelity prototype. Then, ask them to name one benefit of using iterative design in software development.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 04

• Project-Based Learning
• 20 min · Individual

Individual: Iteration Portfolio

Students document their prototype evolution in a digital portfolio: initial sketch, feedback summary, revised version, and reflection on improvements. They self-assess against criteria like user feedback integration, then share one key insight with a partner.

Construct a prototype (paper or digital) for a proposed software solution.

Facilitation Tip

When reviewing Iteration Portfolios, look for evidence of multiple versions and dated notes explaining changes to reinforce the iterative mindset.

What to look for

Present students with a scenario: 'You are designing a new mobile app for ordering groceries.' Ask them to sketch a single screen for this app as a low-fidelity prototype. Then, ask them to list two specific questions they would ask a user to get feedback on this sketch.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

A few notes on teaching this unit

Teachers approach this topic by treating prototypes as conversation starters, not deliverables. Avoid letting students spend excessive time on visual polish early on, as this distracts from the core skill of testing assumptions. Research shows that students learn iteration best when they experience failure early and often, so design activities that force them to confront incomplete ideas in low-risk ways. Use real-world analogies, like comparing software prototyping to drafting an essay, to help students see iterative design as a standard part of creating anything valuable.

Successful learning looks like students confidently explaining why a messy first sketch often leads to a better final product. They should articulate how feedback loops shape their work and adjust prototypes based on clear, actionable input from others.

---

Watch Out for These Misconceptions

• During Paper App Prototype, watch for students insisting their sketches must look 'professional' before sharing them for feedback.

  Redirect them by asking, 'Which parts of this sketch would you want a user to see first?' and remind them that the purpose is to test the flow, not the drawing skills. Point to the example of sticky note flows used by professional designers to normalize rough work.

• During Digital Wireframe Cycles, watch for students treating high-fidelity tools as a first step rather than a later validation stage.

  Stop the group and ask, 'If we tested this wireframe tomorrow, what feedback would we get?' Use their answers to show how low-fidelity prototyping catches bigger issues earlier, saving time before adding colors or fonts.

• During Iteration Portfolio, watch for students only making changes at the end of the process.

  Ask them to point to specific feedback they received after each prototype version and how it led to a change. If they can’t, have them revisit their notes and add missing reflections to practice recognizing iteration as continuous improvement.

---

Methods used in this brief

• Project-Based Learning