Software Design and Evidence-Based Feedback
Grade 11 | Computer Science | Unit 01
Teacher's Guide
Learning objectives
- Explain the central ideas of software design and evidence-based feedback using appropriate vocabulary.
- Apply the worked example and justify answers to the practice questions.
- Complete the investigation or design task and identify a limitation of its model or evidence.
Prerequisites: Basic programming, trace tables, and known-answer testing.
Suggested time: Two or three 45-minute sessions; extend the activity when needed.
Teaching sequence
- Elicit a prior explanation of the topic and note uncertain vocabulary.
- Discuss the concept section, distinguishing observations, models, and assumptions.
- Work through the example. Ask students to explain each step and check any units.
- Complete the activity, then use the five practice questions as an individual check.
- Review the two vocabulary questions and revisit misconceptions revealed by the answers.
Assessment and differentiation
Use the seven questions in the companion CSV for retrieval practice or a short quiz. Award one point per entry for an accurate answer; accept scientifically equivalent wording. Treat five correct answers as a suggested checkpoint for further review, with both reasoning and activity quality assessed separately. Support students with a labeled diagram, a word bank, or a completed first step. Extend by asking students to change one example condition, predict the effect, and explain a limitation.
Student Worksheet
Concept and helping material
Software design begins with a user need and measurable requirements. Break the work into parts, develop a prototype, and test it against the requirements. Documentation explains purpose, use, assumptions, and limitations. Feedback is useful when it identifies an observable problem rather than only a preference. Collaboration benefits from clear roles, shared conventions, and reviewed changes. A scientific application should show units, disclose missing data, and avoid presenting assumptions as measurements. Testing must check behavior and usability, including how the application handles invalid or incomplete inputs.
Vocabulary
- Requirement: A stated condition a system must satisfy.
- Documentation: Information explaining a systems purpose, operation, and limitations.
Worked example
A temperature-summary tool has a requirement: report the mean of valid Celsius readings and clearly identify excluded entries. A test with [10, missing, 20] should not silently treat missing as zero.
Investigation or design task
Prepare a one-page design specification, a test table, and a short user guide for a fictional classroom data tool. Ask a peer to trace its handling of missing data.
Practice
- Why define requirements before implementation?
- Why is silently replacing missing data with zero risky?
- What should a scientific tool display beside a numeric result?
- What makes feedback actionable?
- Why document excluded data?
Vocabulary retrieval
- Define Requirement.
- Define Documentation.
Reflection
Explain which evidence, calculation, or model supports one of your answers. State a condition under which your explanation might need revision.
Answer Key
- They make the intended behavior and success criteria testable.
- Zero is a real value and can bias the result.
- Units and relevant assumptions or limitations.
- A specific observable issue and enough context to reproduce or evaluate it.
- Users need to understand how the reported result was obtained.
Vocabulary definitions appear above and are also included in the CSV. Activity answers may vary; require a clear method or design, correct use of lesson concepts, and an explicit limitation. Reflection is assessed for reasoning rather than one fixed phrase.
Source Reference
Everything You Need to Ace Computer Science and Coding in One Big Fat Notebook, PDF viewer pages 79-120 (1-based). Page numbers refer to this supplied file and may differ from printed page numbers. The source is background reading for the grouped topic. Lesson explanations, examples, and questions are original teaching material; they do not reproduce the book's worksheets or illustrations.