Introduction to Software Development Lifecycle (SDLC)

Active learning works because students need to *feel* the friction of skipping steps or misaligned communication, just as real software teams do. By role-playing phases or comparing models through games, they connect abstract concepts to tangible consequences like delayed deadlines or buggy code.

• 11th Grade
• Computer Science
• 4 activities
• 35 min–60 min

Learning Objectives

1. Explain the purpose and activities of each phase within the Software Development Lifecycle (SDLC).
2. Analyze the impact of neglecting specific SDLC phases on the quality and success of a software product.
3. Compare and contrast the core principles and workflows of Waterfall and Agile SDLC models.
4. Design a simplified SDLC plan for a small software project, justifying phase order and methodology choice.
5. Evaluate the suitability of different SDLC models for various project constraints and requirements.

Concept Mapping

⏱ 45 min·Small Groups

Role-Play: SDLC Phases Simulation

Assign groups roles like analyst, designer, coder, tester. Provide a project brief for a school event app. Groups cycle through phases in 5-minute intervals, documenting decisions and passing artifacts. Debrief on phase dependencies.

Prepare & details

Explain the different phases of the Software Development Lifecycle (SDLC).

Facilitation Tip: During the Role-Play: SDLC Phases Simulation, assign roles like project manager or tester so students experience delays when requirements change mid-phase.

Setup: Tables with large paper, or wall space

Materials: Concept cards or sticky notes, Large paper, Markers, Example concept map

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

Concept Mapping

⏱ 50 min·Pairs

Model Comparison: Waterfall vs Agile Board Game

Create game boards showing project milestones. In Waterfall path, teams move sequentially but risk backtracking on changes. Agile path allows sprints with feedback cards. Play twice, track completion time and quality scores.

Prepare & details

Analyze the importance of each phase in delivering a successful software product.

Facilitation Tip: For the Waterfall vs Agile Board Game, provide a one-page cheat sheet of rules and SDLC definitions to reference during play.

Setup: Tables with large paper, or wall space

Materials: Concept cards or sticky notes, Large paper, Markers, Example concept map

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

Case Study Analysis

⏱ 35 min·Small Groups

Case Study Analysis: Real-World SDLC Analysis

Distribute articles on software failures like a banking app glitch. Students map events to SDLC phases in a graphic organizer, identify missed steps, and propose fixes using Agile principles. Share findings class-wide.

Prepare & details

Differentiate between various SDLC models (e.g., Waterfall, Agile).

Facilitation Tip: In the Case Study: Real-World SDLC Analysis, give each group a printout of a flawed app (e.g., TikTok’s early privacy issues) to trace back to skipped phases.

Setup: Groups at tables with case materials

Materials: Case study packet (3-5 pages), Analysis framework worksheet, Presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Concept Mapping

⏱ 60 min·Small Groups

Mini-Project: Agile Sprint Planning

Teams plan a 2-week sprint for a basic web tool using sticky notes on a board: backlog, tasks, daily stand-ups. Implement one feature, demo, and retrospect. Adjust for next sprint based on feedback.

Prepare & details

Explain the different phases of the Software Development Lifecycle (SDLC).

Facilitation Tip: For the Mini-Project: Agile Sprint Planning, use a timer for 10-minute sprints so students feel the pressure of time-boxed work.

Setup: Tables with large paper, or wall space

Materials: Concept cards or sticky notes, Large paper, Markers, Example concept map

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

Teaching This Topic

Teachers should avoid lecturing the phases in order, as students need to *discover* the pain points themselves. Start with a relatable problem—like a broken school app—then let them map it to SDLC phases. Emphasize that documentation isn’t busywork; it’s the team’s memory. Research shows that analog simulations stick longer than slides, so prioritize tactile or visual activities over abstract discussions.

What to Expect

Successful learning looks like students confidently articulating why a phase matters, selecting the right model for a scenario, and critiquing their own or peers’ work against SDLC criteria. They should also recognize when shortcuts lead to problems in prototypes or plans.

Watch Out for These Misconceptions

Common Misconception

During the Role-Play: SDLC Phases Simulation, some students may assume SDLC only applies to large teams.

What to Teach Instead

During the simulation, assign small student projects (e.g., a class attendance app) and have teams present how SDLC phases helped them manage scope. Ask peers to identify which phase caught a critical error early.

Common Misconception

During the Mini-Project: Agile Sprint Planning, students might think Agile lacks structure.

What to Teach Instead

Use the sprint review board to show how Agile relies on backlog grooming and daily stand-ups. Point to the printed user stories and acceptance criteria as evidence of continuous planning.

Common Misconception

During the Model Comparison: Waterfall vs Agile Board Game, students may overgeneralize that Waterfall is always slower.

What to Teach Instead

After the game, display the results on a whiteboard and ask teams to compare turn-based (Waterfall) vs iterative (Agile) progress. Highlight scenarios where Waterfall was faster due to clear requirements.

Assessment Ideas

Quick Check

After the Role-Play: SDLC Phases Simulation, give students a 5-minute written prompt: ‘List the phases you completed for your app. Identify one phase where your team struggled and explain why. How could you have improved it?’ Collect responses to gauge understanding of phase dependencies.

Discussion Prompt

During the Model Comparison: Waterfall vs Agile Board Game, pause after round 2 and ask, ‘What changed in your approach when the client’s requirements shifted midway? How did your model handle it?’ Use responses to assess adaptability and phase selection.

Peer Assessment

After the Case Study: Real-World SDLC Analysis, have groups swap their case study write-ups. Peers answer: ‘Does the write-up include all core phases? Which phase was most critical to the failure, and why?’ Use rubrics to evaluate depth of analysis.

Extensions & Scaffolding

• Challenge: Ask students to design a hybrid SDLC model for a project requiring both strict compliance (e.g., healthcare) and rapid iteration (e.g., UX feedback).
• Scaffolding: Provide a partially filled SDLC checklist for the Mini-Project, leaving key questions for students to complete together.
• Deeper exploration: Have students research DevOps practices and propose how they could integrate into their Agile sprints.

Key Vocabulary

Requirements Analysis	The phase where user needs and project goals are identified and documented. This ensures the software built meets the intended purpose.
Software Design	This phase involves creating the blueprint for the software, outlining its architecture, modules, interfaces, and data structures.
Implementation	The phase where developers write the actual code based on the design specifications. This is where the software is built.
Testing	This phase focuses on identifying and fixing defects or bugs in the software to ensure it functions correctly and meets requirements.
Deployment	The process of releasing the software to users or the production environment. This makes the software available for use.
Maintenance	Ongoing support and updates for the software after deployment, including bug fixes, enhancements, and adaptations to new environments.