Computer Science · Grade 11 · Object-Oriented Programming and Design · Term 2

Introduction to Software Development Life Cycle (SDLC)

Overview of the stages involved in software development, from requirements gathering to deployment and maintenance.

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

About This Topic

The Software Development Life Cycle (SDLC) structures the process of creating reliable software through defined phases: requirements gathering, design, implementation, testing, deployment, and maintenance. Grade 11 students examine models like Waterfall, a sequential method ideal for stable projects, and Agile, an iterative approach that welcomes changes and frequent feedback. These elements align with Ontario curriculum standards CS.HS.D.1 and CS.HS.D.4, emphasizing design processes and their impact on outcomes.

In the Object-Oriented Programming unit, SDLC links planning to coding by showing how requirements drive class structures and testing ensures robust applications. Students analyze model effects on timelines, adaptability, and quality, cultivating skills in evaluation and justification essential for programming careers.

Active learning suits this topic well. Students simulate phases in group projects, such as developing a simple inventory app, to grasp interdependencies. Role assignments and iterative revisions make abstract models concrete, while peer reviews highlight real-world trade-offs, boosting retention and practical understanding.

Key Questions

1. Explain the different phases of a typical Software Development Life Cycle.
2. Analyze how different SDLC models (e.g., Waterfall, Agile) impact project outcomes.
3. Justify the importance of each phase in producing high-quality software.

Learning Objectives

• Explain the purpose and key activities of each phase in a standard Software Development Life Cycle.
• Compare and contrast the Waterfall and Agile SDLC models, identifying their strengths and weaknesses.
• Analyze how the choice of SDLC model can influence project timelines, budget, and final product quality.
• Justify the necessity of thorough requirements gathering and design phases for successful software development.
• Evaluate the impact of testing and maintenance phases on the reliability and longevity of software applications.

Before You Start

Introduction to Programming Concepts

Why: Students need a basic understanding of what code is and how it functions to appreciate the implementation phase of the SDLC.

Problem Solving and Algorithmic Thinking

Why: Understanding how to break down problems and create step-by-step solutions is foundational for the design and implementation phases.

Key Vocabulary

Requirements Gathering	The initial phase where stakeholders' needs and project objectives are identified and documented.
Software Design	The phase where the system architecture, database structure, and user interface are planned based on gathered requirements.
Implementation	The phase where developers write the actual code for the software based on the design specifications.
Testing	The phase where the software is verified and validated to ensure it meets requirements and is free of defects.
Deployment	The phase where the developed software is released and made available for users.
Maintenance	The ongoing phase after deployment, involving updates, bug fixes, and enhancements to the software.

Watch Out for These Misconceptions

Common Misconception

SDLC follows one rigid sequence for all projects.

What to Teach Instead

Models vary: Waterfall is linear, while Agile iterates. Station rotations let students experience both, comparing outcomes to see how flexibility suits changing needs. Peer teaching reinforces model selection based on context.

Common Misconception

Testing occurs only after all coding finishes.

What to Teach Instead

Quality checks integrate throughout phases, especially in Agile. Simulations with role-plays demonstrate early testing's value in catching issues, as groups revise code mid-project and discuss efficiency gains.

Common Misconception

Requirements stay fixed once gathered.

What to Teach Instead

Agile accommodates evolving needs via sprints. Group projects show change impacts, with students adapting plans collaboratively, highlighting why iteration prevents costly late fixes.

Active Learning Ideas

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.

45 min·Small Groups

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.

25 min·Pairs

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.

50 min·Small Groups

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.

30 min·Individual

Real-World Connections

• Tech companies like Google use Agile methodologies to rapidly develop and update features for products such as Google Maps, allowing for quick responses to user feedback and market changes.
• Aerospace manufacturers, such as Boeing, often employ more structured SDLC models like Waterfall for developing critical aircraft systems, where safety and rigorous validation are paramount before deployment.
• Video game studios, like Ubisoft, balance iterative development (Agile) for core gameplay with more defined phases for final release and post-launch content updates, managing complex projects with many dependencies.

Assessment Ideas

Exit Ticket

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.

Quick Check

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.

Discussion Prompt

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?'

Frequently Asked Questions

What are the main phases of the Software Development Life Cycle?

The SDLC includes requirements gathering to identify needs, design to plan structures, implementation for coding, testing to verify functionality, deployment to release the software, and maintenance for updates. Each phase builds on the last, ensuring quality. In class, students map these to real apps like social media tools, seeing connections to object-oriented design.

How do Waterfall and Agile SDLC models differ?

Waterfall progresses sequentially with all requirements upfront, suiting fixed projects but risking late changes. Agile uses short iterations, sprints, and feedback for adaptability, ideal for dynamic needs. Students compare via scenarios: Waterfall for a calculator app, Agile for a chat feature, analyzing risks and benefits for project success.

Why is SDLC important in Grade 11 Computer Science?

SDLC teaches systematic software creation, linking to object-oriented programming by showing how phases shape code quality and reliability. It prepares students for industry practices, where poor planning leads to failures. Analyzing models builds decision-making for careers, meeting Ontario standards on design processes.

How can active learning help students understand the SDLC?

Active methods like phase stations or mini-projects immerse students in SDLC flow, assigning roles to experience interdependencies. Iterating on a class app reveals Agile's adaptability versus Waterfall's structure. Group debriefs clarify misconceptions, with data from simulations showing phase impacts, making theory practical and engaging for retention.