Computer Science · Grade 11

Active learning ideas

Introduction to Software Development Life Cycle (SDLC)

Active learning helps students grasp the Software Development Life Cycle by moving beyond abstract definitions to tangible, hands-on experiences. Each phase of SDLC becomes clearer when students simulate tasks, solve real problems, and collaborate in roles that mirror industry practice. This approach builds both conceptual understanding and practical skills needed for future coursework and careers.

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

• 25–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Stations Rotation
• 45 min · Small Groups

Stations Rotation: SDLC Phases

Create six stations, one for each phase: write user stories at requirements, sketch UML diagrams at design, pseudocode functions at implementation, devise test cases at testing, plan rollout at deployment, and suggest updates at maintenance. Groups rotate every 7 minutes, documenting outputs from each. Debrief as a class to connect phases.

Explain the different phases of a typical Software Development Life Cycle.

Facilitation Tip

During the Station Rotation, place a timer at each station to keep groups focused and ensure smooth transitions between phases.

What to look for

Provide students with a scenario describing a software project (e.g., a simple mobile game vs. a banking application). Ask them to identify which SDLC model (Waterfall or Agile) would be more appropriate and explain their reasoning in 2-3 sentences, referencing specific project characteristics.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 02

• Think-Pair-Share
• 25 min · Pairs

Think-Pair-Share: Model Comparison

Present a game app scenario. Students think alone for 3 minutes about Waterfall versus Agile application, pair up to debate pros and cons with examples, then share key insights with the whole class. Chart class findings on a shared board.

Analyze how different SDLC models (e.g., Waterfall, Agile) impact project outcomes.

Facilitation Tip

For the Think-Pair-Share, provide a structured comparison table so students organize evidence before sharing with the class.

What to look for

Present students with a list of activities (e.g., writing code, user interviews, bug fixing, system architecture planning). Ask them to categorize each activity into one of the SDLC phases and briefly explain why it belongs there.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 03

• Jigsaw
• 50 min · Small Groups

Jigsaw: SDLC in Action

Assign each small group one SDLC model and phase set. Experts teach their peers through mini-presentations and role-plays. Groups then apply combined knowledge to critique a flawed project case study collaboratively.

Justify the importance of each phase in producing high-quality software.

Facilitation Tip

In the Jigsaw, assign each expert group a project scenario with clear success criteria to guide their discussion and presentation.

What to look for

Facilitate a class discussion using the prompt: 'Imagine a project where requirements change frequently. How would using a Waterfall model versus an Agile model affect the team's ability to adapt and deliver a successful product? What are the potential trade-offs?'

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Activity 04

• Concept Mapping
• 30 min · Individual

Individual: Phase Card Sort

Provide cards listing tasks and phases. Students sort them individually into correct order for Waterfall and Agile models, then justify choices in pairs. Discuss variations as a class.

Explain the different phases of a typical Software Development Life Cycle.

What to look for

Provide students with a scenario describing a software project (e.g., a simple mobile game vs. a banking application). Ask them to identify which SDLC model (Waterfall or Agile) would be more appropriate and explain their reasoning in 2-3 sentences, referencing specific project characteristics.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

A few notes on teaching this unit

Teaching SDLC works best when you connect abstract phases to lived experiences, such as student projects or familiar apps. Avoid presenting models as rigid frameworks; instead, emphasize that models are tools to solve problems. Research shows that students retain concepts better when they confront misconceptions directly through guided comparisons and role-based simulations rather than lectures alone.

By the end of these activities, students should confidently explain the purpose and flow of each SDLC phase, compare Waterfall and Agile models using concrete examples, and justify model choices based on project characteristics. Successful learning includes accurate classification of activities, thoughtful model selection, and clear communication of reasoning during discussions and reflections.

---

Watch Out for These Misconceptions

• During the Station Rotation activity, watch for students who assume SDLC always follows the same sequence regardless of project type.

  Use the Waterfall and Agile stations to have students document differences in phase order and deliverables, then share findings during the whole-class debrief. Ask each group to explain why their model's sequence fits the project scenario provided at their station.

• During the Jigsaw activity, watch for students who believe testing happens only after coding is complete.

  Provide each expert group with a scenario that includes testing tasks scattered throughout the project timeline. Have them role-play how testing integrates during design, implementation, and deployment, then present examples of early feedback preventing major issues.

• During the Think-Pair-Share activity, watch for students who think project requirements are set in stone once gathered.

  Give students two versions of a project scenario: one stable and one evolving. Ask them to discuss how each model handles changes, using the comparison table to record specific adaptations in requirements during the pair phase before sharing with the class.

---

Methods used in this brief

• Stations Rotation
• Think-Pair-Share
• Jigsaw
• Concept Mapping