PYTHON-02 · Foundation · ENGLISH · PLANNED
Predict the output, trace state, write a small program and debug it.
Study time is an initial activity estimate, excluding extra reading, revision and extended laboratory or project work. Videos and question bodies have not been produced by adding this outline.
Complete these courses or demonstrate equivalent knowledge. These are recommended prerequisites, not enforced enrolment locks.
YouTube playlist: ARK Python | Control Flow and Problem Solving
Playlist title reserved in the plan; no YouTube playlist or upload has been created yet.
Sign in to save this learning pathPractical outcome: Build a flowchart and test table for a parcel-price rule.
Explain and using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Explain or using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Explain not using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Explain nested conditions using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Use the first concepts from this section. Build a flowchart and test table for a parcel-price rule. Produce a labelled diagram, trace or calculation; explain each step and check one changed input.
3–6 questions on the preceding first-half concepts only: recall, visual interpretation, application and one plausible misconception. Explain each answer after submission.
Explain membership tests using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Explain truthy and falsy values using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Explain boundary cases using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Explain decision-table testing using a visual and one worked real-world example. Context: Build a flowchart and test table for a parcel-price rule. End with a prediction or check-for-understanding.
Build a flowchart and test table for a parcel-price rule. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering and, or, not and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Trace repeated totals and find an off-by-one error.
Explain while loops using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain loop state using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain for loops using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain range using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain accumulators using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Use the first concepts from this section. Trace repeated totals and find an off-by-one error. Produce a labelled diagram, trace or calculation; explain each step and check one changed input.
3–6 questions on the preceding first-half concepts only: recall, visual interpretation, application and one plausible misconception. Explain each answer after submission.
Explain counters using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain break using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain continue using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain nested loops using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Explain infinite-loop diagnosis using a visual and one worked real-world example. Context: Trace repeated totals and find an off-by-one error. End with a prediction or check-for-understanding.
Trace repeated totals and find an off-by-one error. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering while loops, Loop state, for loops and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Practical outcome: Split a unit-converter design into small independently tested functions.
Explain defining a function using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain parameters using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain arguments using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain return values using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain local scope using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Use the first concepts from this section. Split a unit-converter design into small independently tested functions. Produce a labelled diagram, trace or calculation; explain each step and check one changed input.
3–6 questions on the preceding first-half concepts only: recall, visual interpretation, application and one plausible misconception. Explain each answer after submission.
Explain default arguments using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain keyword arguments using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain pure functions using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain decomposition using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Explain docstrings using a visual and one worked real-world example. Context: Split a unit-converter design into small independently tested functions. End with a prediction or check-for-understanding.
Split a unit-converter design into small independently tested functions. Work without the example, compare two cases, record assumptions and limitations, then self-review correctness, reasoning and clarity.
6–12 questions covering Defining a function, Parameters, Arguments and the remaining section concepts, with cumulative retrieval from earlier sections. Include a new transfer problem; 70% unlocks progression.
Combine all three sections: Split a unit-converter design into small independently tested functions. Submit an original worked artifact, evidence or tests, assumptions and a reflection. Rubric: correctness, method, practical usefulness, reproducibility and communication. Self-reviewed, not certified.
6–12 balanced questions sampling every section of Control Flow and Problem Solving, including interpretation, calculation or reasoning, a misconception and a new application. Passing is 70%; review errors before retrying.
Coding, trace tables, tests and original portfolio projects. Guided work leads to an independent attempt, with a diagram, explanation, trace, calculation or tested artifact. Question bodies are generated when opened in your private learning path. Programming submissions are stored as text; the platform does not execute submitted code.
Use original or appropriately licensed datasets. Practical science activities use models or supplied data unless a qualified supervisor has reviewed a physical experiment.
Open the interactive practice sampler →