Software & Development

Overview

Subject: Technology
Level: Cambridge International AS Level (Year 12)
Duration: 58 minutes
Class size: 9 students
Curriculum: Cambridge International AS & A Level Computer Science (9618)
Topic: Software and Software Development
References:

• Cambridge International AS & A Level Computer Science syllabus (9618), Section 1 & 3 (Systems Software, Software Development)
• Learning Outcomes:
  • Understand different types of software and their purposes
  • Explain the stages of the Software Development Life Cycle (SDLC)
  • Identify tasks and outputs at each SDLC stage

---

Learning Objectives

By the end of the lesson, students will be able to:

• Define and classify types of software: system software, application software, and utility software (Cambridge 9618, Topic 1.1)
• Describe the major stages of the Software Development Life Cycle (SDLC) and explain key activities within each (Topic 3.1)
• Analyse the importance of SDLC in producing high-quality, maintainable software
• Evaluate common tools used within SDLC stages (e.g., IDEs, testing tools)
• Collaborate to plan a basic software development project outline

---

Suggested PowerPoint Structure and Activities

Slide 1 – Title

• Title: Software and Software Development
• Subtitle: Cambridge International AS-Level Computer Science (9618)
• Lesson Objectives:
  • Understand types of software
  • Learn SDLC stages and their significance
  • Apply SDLC knowledge through group discussion

Teacher Activity: Read aloud the objectives. Ask students why understanding software types is important before developing software.

---

Slide 2 – Types of Software

• Categories:
  • System software: Operating systems, device drivers, utilities
  • Application software: Word processors, games, browsers
  • Utility software: Antivirus, file compression, backup tools
• Visuals: Display icons/logos of Windows/MacOS, Microsoft Word, WinRAR, Norton Antivirus

Student Activity: Whole-class brainstorming – list as many software examples as they can think of and classify them into the three categories. Use a whiteboard or shared virtual board.

Assessment: Check student classifications against correct categories to measure understanding (formative).

---

Slide 3 – Software Development Life Cycle (SDLC)

• Stages: Analysis → Design → Implementation → Testing → Evaluation → Maintenance
• Diagram: Cycle chart with arrows
• Short description of each stage:
  • Analysis: Gathering requirements from users
  • Design: Planning software structure and UI
  • Implementation: Writing code
  • Testing: Verifying functionality and fixing bugs
  • Evaluation: Assessing if software meets requirements
  • Maintenance: Updating and fixing post-release

Teacher Activity: Explain the purpose of each stage with real-world analogies (e.g., designing a building).

---

Slide 4 – Deep Dive: SDLC Stages and Outputs

• Table with columns: Stage | Key Activities | Outputs/Documents
• Example:
  • Analysis | Requirements gathering, feasibility study | Requirement Specification Document
  • Design | Create flowcharts, data structures | Design Document, UML diagrams
  • Implementation | Coding, compiling | Executable software
  • Testing | Unit testing, system testing | Test reports, bug logs
  • Evaluation | Compare output to requirements | Evaluation report
  • Maintenance | Bug fixes, enhancements | Updated software versions

Student Activity: In groups of 3, receive one stage each and prepare a 2-minute presentation describing that stage’s activities and outputs.

---

Slide 5 – Real-World Software Development: Tools and Techniques

• Discuss Integrated Development Environments (IDEs), version control (Git), automated testing tools
• Explain benefits such as error detection, collaboration, efficiency
• Photos/screenshots of tools (e.g., Visual Studio Code, GitHub interface, Selenium)

Teacher Activity: Brief demo of a simple IDE if possible (e.g., opening VS Code and showing basic features).

---

Slide 6 – Collaborative Mini-Project: Plan a Simple App

• Scenario: Design a “to-do list” app using SDLC principles
• Tasks: Outline requirements, propose design ideas, list implementation languages/tools, suggest testing strategies
• Group work: 15 minutes with roles assigned (Analyst, Designer, Coder, Tester)

Assessment: Groups present their plans. Teacher provides feedback on completeness and real-world feasibility.

---

Slide 7 – Summary & Recap

• Key points revisited: software types, SDLC stages, real-world tools
• Ask questions:
  • Why is maintenance important in SDLC?
  • Give examples of system software and utility software you use daily.
• Clarify doubts

---

Slide 8 – Exit Ticket / Formative Assessment

• Short quiz (3 questions):

  1. What is the purpose of the Testing stage?
  2. Name two examples of utility software.
  3. Which SDLC stage involves gathering user requirements?

• Students write answers on small slips or submit digitally.

---

Differentiation & Inclusion

• Provide printed handouts with glossary of software terms
• Visual aids support EAL learners
• Group roles allow for differentiated peer support
• Adapt pace for learners needing extra time during group work

---

Resources Needed

• Computer + Projector/Smartboard
• PowerPoint slides prepared as per above structure
• Handouts: glossary, SDLC stages chart
• Whiteboard or virtual board for brainstorming
• Access to IDE demo (optional)

---

Teacher Reflection Notes

• Monitor engagement during the group mini-project to ensure participation
• Check understanding in formative quizzes, revisit complex points where necessary
• Encourage students to relate SDLC knowledge to any software development experiences they have had

---

This lesson plan is designed to align with Cambridge International AS & A Level Computer Science syllabus content, ensuring students develop foundational knowledge of software and its development processes with practical and collaborative elements to deepen understanding.