Preview

The whole resource, exactly as a class sees it. Answers and marking are held back.

Turtle practical checkpoint

Independent brief

Create a Turtle graphic for a visitor information screen. Your image must show a clear location or event theme and must be assembled from reusable subprograms. Examples might include a museum entrance, wildlife centre, transport hub or local landmark, but the final design is your own.

This checkpoint assesses your planning, implementation, testing and refinement. It does not provide a step-by-step construction or a finished solution.

Required features

Your program must include:

a short decomposition plan before the implementation;
at least three meaningful drawing subprograms;
at least one subprogram with parameters;
at least one purposeful use of repetition;
deliberate positioning using Cartesian coordinates;
safe movement with penup and pendown;
at least one filled closed shape;
at least one circle or arc;
intentional drawing order or layers;
evidence of component testing and one later refinement.

Use the Turtle methods in Pearson's programming subset. Do not replace the task with an unrelated graphics library.

Part A: plan

Complete the planning comments in the starter code before writing the procedures.

Your plan must identify:

the overall visual outcome;
at least three components;
useful parameters for position, size or colour;
a sensible layer order;
one repeated pattern.

Part B: construct components

Implement and test each drawing subprogram separately. Start with simple arguments and a clear position. Record one component test in the evidence comments.

A meaningful subprogram draws a recognisable component or performs a reusable operation. A procedure containing only one ordinary forward call would not demonstrate useful decomposition.

Part C: integrate

Write a clear main program that calls the components in the planned order. Reuse at least one parameterised component with different arguments.

Inspect both the code and canvas. Correct unwanted lines, incorrect headings, open fill boundaries, hidden details and inconsistent scaling.

Part D: refine and explain

Record one change made after testing the integrated image. State:

what the problem or weakness was;
what you changed;
how the change improved the result.

Teacher review criteria

Your teacher will review the following evidence:

Decomposition: the plan and subprograms divide the problem meaningfully.
Programming constructs: repetition, calls and parameters are purposeful and correct.
Turtle control: position, heading, pen, fill and circle/arc methods produce the intended image.
Composition: repeated components and layers form a coherent result.
Testing and readability: the student tests components, records a refinement and uses helpful names and comments.

Meeting a feature once is not enough if it does not contribute to the intended solution. Your teacher will judge the complete evidence rather than automatically matching one canvas.

Final checklist

Run the program from the beginning, not only after editing one section.
Confirm the final canvas matches the brief and your plan.
Confirm every called procedure is defined.
Confirm no pass statements remain in required procedures.
Confirm every intended fill begins before and ends after a closed boundary.
Confirm the testing and refinement comments are complete.
Save your final code before handing it in.

Starter code

import turtle

screen = turtle.Screen()
screen.setup(1000, 700)

artist = turtle.Turtle()
artist.speed("fastest")

# PART A: DECOMPOSITION PLAN
# Intended location or event theme:
# Component 1:
# Component 2:
# Component 3:
# Useful parameters:
# Layer order:
# Repeated pattern:


# PART B: SUBPROGRAMS
# Define at least three meaningful drawing subprograms.
# At least one must accept useful parameters.


# COMPONENT TEST EVIDENCE
# Procedure tested:
# Arguments used:
# Expected result:
# Actual result and correction:


# PART C: MAIN PROGRAM
# Call the components in the planned order.
# Reuse at least one parameterised component with different arguments.


# PART D: INTEGRATION REFINEMENT
# Weakness found after running the complete design:
# Change made:
# How the change improved the result:


turtle.done()