Computer Science · Class 12

Active learning ideas

Open Source vs. Proprietary Software Models

Active learning helps students grasp abstract concepts like software licensing by making them concrete. When students debate, role-play, and analyse real cases, they move from passive listening to active decision-making. This topic often feels dry until students see how licences affect real-life choices, such as government projects or start-up budgets.

• CBSE Learning Outcomes
• CBSE: Societal Impacts - Intellectual Property Rights - Class 12

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

Activity 01

• Philosophical Chairs
• 45 min · Small Groups

Debate Rounds: Open Source vs Proprietary

Divide class into teams of four. Assign half to argue for open source and half for proprietary in a school project context. Each team presents three points with evidence, followed by rebuttals and class vote. Conclude with reflections on key factors.

Differentiate between open source and proprietary software models.

Facilitation Tip

During Debate Rounds, assign clear roles (e.g., developer, government official) to push students beyond generic arguments and into context-specific reasoning.

What to look for

Pose the question: 'Imagine you are advising a small startup in Bengaluru on choosing an operating system and office suite. What factors would you consider to recommend either open source or proprietary options? Justify your recommendation with specific reasons.'

• Analyze
• Evaluate
• Self-Awareness
• Social Awareness

Activity 02

• Gallery Walk
• 50 min · Small Groups

Gallery Walk: Software Examples

Groups research pairs like Ubuntu vs Windows or MySQL vs Oracle, create posters on licensing, development, and costs. Students rotate to view posters, note comparisons, and discuss in pairs. Summarise class insights on a shared chart.

Analyze the economic and social benefits of the open-source movement.

Facilitation Tip

For Case Study Gallery Walk, place software examples on separate tables with guiding questions on posters to keep students focused during movement.

What to look for

Present students with short descriptions of software scenarios (e.g., a large enterprise needing a custom database, a student needing a word processor). Ask them to identify whether open source or proprietary software would likely be a better fit and briefly explain why, referencing licensing or cost.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 03

• Philosophical Chairs
• 35 min · Pairs

Project Pitch: Choose Your Software

In pairs, select open source or proprietary tool for a database management task. Prepare a two-minute pitch justifying choice with criteria like cost and customisation. Present to class for feedback and vote.

Justify the choice between using open source or proprietary software for a specific project.

Facilitation Tip

In Licence Role-Play, provide sample licence texts (simplified) so students practise negotiating terms without feeling overwhelmed by legal jargon.

What to look for

Divide students into pairs. Assign one student to argue for the benefits of open source software and the other for proprietary software in a given context (e.g., developing a new mobile app). After a short preparation time, they debate their points. The other students in the class can then vote on which argument was more convincing and why.

• Analyze
• Evaluate
• Self-Awareness
• Social Awareness

Activity 04

• Philosophical Chairs
• 30 min · Pairs

Licence Role-Play: Negotiation Scenarios

Assign roles: developer, user, company rep. Pairs negotiate terms for software use in an Indian e-governance project. Switch roles and debrief on open vs proprietary differences.

Differentiate between open source and proprietary software models.

Facilitation Tip

For Project Pitch, give a template slide with sections like 'Cost', 'Support', and 'Customisation' to structure student presentations.

What to look for

Pose the question: 'Imagine you are advising a small startup in Bengaluru on choosing an operating system and office suite. What factors would you consider to recommend either open source or proprietary options? Justify your recommendation with specific reasons.'

• Analyze
• Evaluate
• Self-Awareness
• Social Awareness

A few notes on teaching this unit

Experienced teachers approach this topic by starting with everyday examples students know, like WhatsApp (proprietary) versus VLC (open source). Avoid diving too deep into technical details; instead, focus on the economic and ethical implications that matter to students. Research shows that when students see how licences affect their own technology use, they engage more deeply than with abstract definitions.

By the end of these activities, students will confidently compare open source and proprietary models. They will justify choices using evidence from case studies, debates, and licence analyses. Successful learning appears when students shift from saying 'open source is free' to explaining 'GPL ensures freedom with redistribution obligations.'

---

Watch Out for These Misconceptions

• During Debate Rounds, watch for students claiming 'Open source software costs nothing and needs no licence.'

  Use the debate to redirect: 'Refer to the GPL licence text provided during Licence Role-Play. Explain what ‘free’ means in open source and when a licence is mandatory for redistribution.'

• During Case Study Gallery Walk, watch for students assuming 'Proprietary software is always superior in quality and security.'

  Point to the Heartbleed case study on the Linux table. Ask them to compare update timelines and community responses to demonstrate how peer review strengthens open source.

• During Project Pitch, watch for students stating 'Open source lacks support or updates.'

  Refer them to the Red Hat case study on the Linux table. Ask them to explain how firms provide paid support and how update histories compare to proprietary systems.

---

Methods used in this brief

• Philosophical Chairs
• Gallery Walk