9-12 Computer Science — Algorithms and Computational Thinking: Collaborative Investigation

Lesson snapshot

Subject: Computer Science · Grade band: 9-12 · Suggested time: 55 minutes · Format: Collaborative Investigation

This lesson is designed to build understanding through structured roles, evidence sharing, productive discussion, and an individual accountability product. It supports learners as they decompose problems, recognize patterns, design precise algorithms, and evaluate efficiency and correctness.

Learning objectives and success criteria

• Explain the central idea of Algorithms and Computational Thinking in learner-friendly and discipline-appropriate language.
• Use this reasoning process: define inputs and outputs, break the task into cases, write unambiguous steps, trace examples, and revise.
• Create an algorithm, trace table, edge cases, and revision and revise at least one decision from evidence or feedback.
• Apply the idea to a changed example without copying the modeled response.

Success is visible when the learner completes an appropriate task accurately, identifies relevant evidence, explains the method, and transfers the learning with the stated level of support.

Preparation, materials, and vocabulary

Materials: teacher-selected grade-appropriate example; student response sheet or notebook; display or chart space; exit ticket; privacy-safe device or unplugged computing cards.

Vocabulary: algorithms, computational, thinking. Add or replace terms to match the adopted local curriculum and learners’ language needs.

Before class, verify source permissions, accessibility, technology access, physical safety, privacy, and any required school procedures. Prepare one accessible entry example and one extension that deepens reasoning rather than adding repetitive work.

Launch the investigation — 7 minutes

Present a focused question or design challenge involving Algorithms and Computational Thinking. State the shared product, individual product, available evidence, constraints, and respectful discussion norms.

Roles and evidence collection — 18 minutes

Use roles such as facilitator, evidence tracker, skeptic/checker, and reporter; rotate or adapt roles for access. Groups define inputs and outputs, break the task into cases, write unambiguous steps, trace examples, and revise. Every claim must point to data, text, representation, test, observation, or documented criterion.

Cross-group comparison — 10 minutes

Groups exchange one claim and its evidence. The receiving group writes one clarification question and one alternative interpretation or test. Students distinguish disagreement about an idea from judgment of a person.

Revision and individual synthesis — 15 minutes

A learner traces an algorithm with normal and edge cases and identifies an ambiguous instruction. Each learner then creates a personal explanation or solution showing what changed after collaboration. The individual product prevents a polished group answer from being mistaken for individual mastery.

Debrief — 5 minutes

Ask which role or piece of evidence improved the work, which uncertainty remains, and how the group could collaborate more inclusively. Collect an algorithm, trace table, edge cases, and revision plus the individual synthesis.

Differentiation without lowering the learning goal

• Access: Chunk directions, model one step, use visuals or manipulatives, permit approved assistive technology, and reduce task length while preserving the target.
• Multilingual learners: Preview essential language, provide discussion rehearsal, allow home-language resources when appropriate, and assess disciplinary thinking separately from minor language difference.
• Additional support: Use a worked example, organizer, highlighted evidence, or smaller data/text set; document the support and plan how it will fade.
• Extension: Add a counterexample, competing source, changed constraint, new audience, proof, design trade-off, or request for generalization.

Follow the learner’s IEP, 504 plan, language-support plan, school policy, and teacher or specialist guidance. This lesson does not diagnose a disability or replace qualified support.

Teacher answer and feedback guidance

Do not look only for a single final answer. A satisfactory response should demonstrate this reasoning: define inputs and outputs, break the task into cases, write unambiguous steps, trace examples, and revise. It should include accurate evidence or representation, a defensible decision, explanation, and a check or limitation. Watch specifically for assuming a sequence works because it succeeds on one example. If it appears, ask the learner to compare the decisive feature in an example and nonexample before assigning more practice.

Homework or extension option

Ask learners to find or create one new, privacy-safe example of Algorithms and Computational Thinking from class, home, media, a public dataset, a text, or a designed scenario. They should explain why it fits, apply the lesson method, and identify one limitation. Do not require purchases, private family financial or health disclosures, unsafe activity, or access to a paid service.

Safety, rights, and source boundaries

Use teacher-approved materials, age-appropriate supervision, accessible formats, licensed or public-domain sources, and privacy-safe data. Verify current local rules for laboratory work, technology, health, CTE equipment, student records, media use, and community activity. Financial, health, legal, emergency, and career-program decisions require the appropriate official or qualified source.

Related Algorithms and Computational Thinking lessons

Concept Launch Lesson · Worked Example Workshop · Collaborative Investigation

Framework reference: 2026 CSTA PK–12 Computer Science Standards. This is an original independent Exams.fit lesson, not copied standards or an official state curriculum. Local expectations may differ. Reviewed August 2, 2026.