Term 3 Week 9 - Week 1

Programming Practical Readiness

Practise reading scenarios, building short programs, testing logic, completing trace tables and submitting Task 7.

Learning Goals

  • Read a practical programming scenario accurately.
  • Create an input-process-output table and data plan.
  • Build short code using sequence, selection and iteration.
  • Use test data and trace tables to identify logic issues.
  • Submit Task 7 practical evidence through the LMS.

Five-Lesson Sequence

1

Annotate scenarios and build IPO/data plans.

2

Practise selection and iteration in a small study-session program.

3

Use normal, boundary and invalid tests with trace tables.

4

Complete a timed mock practical.

5

Complete Task 7 and begin Task 8 network requirements.

Detailed Lesson Pathway

Lesson 1

Read Before Coding

Identify what the program needs before opening the programming tool.

  1. Open the task scenario and read it twice.
  2. Circle input values.
  3. Underline processing steps.
  4. Box output requirements.
  5. Write likely variable names and data types.
  6. Draft the main sequence in pseudocode.

Evidence: Annotated scenario, IPO table and data plan.

Lesson 2

Build The Core Logic

Create a small program that uses sequence, selection and iteration.

  1. Build one input, calculation and output path.
  2. Add the decision logic.
  3. Test the lower boundary and upper boundary.
  4. Wrap the logic in a fixed loop.
  5. Add a counter or total.
  6. Show the final result after the loop.

Evidence: Practice code or pseudocode checked against the requirements.

Lesson 3

Test, Trace And Debug

Use test data and trace tables to find mistakes.

  1. Choose normal data.
  2. Choose boundary data.
  3. Choose invalid or unexpected data.
  4. Write expected results first.
  5. Run or trace the algorithm.
  6. Fix one identified error.

Evidence: Completed test table, trace table and corrected logic.

Lesson 4

Timed Mock Practical

Practise the full process under time pressure.

  1. Use the five-minute reading routine.
  2. Draft variables and pseudocode quickly.
  3. Build the simplest working version.
  4. Add the required selection and iteration.
  5. Complete test and trace evidence.
  6. Check the marking summary before submission.

Evidence: Mock practical file and self-check against the marking summary.

Lesson 5

Task 7 Practical Test

Complete and submit the supervised programming practical.

  1. Read the test paper carefully.
  2. Plan before coding.
  3. Build the required program.
  4. Test and trace before submitting.
  5. Upload the final file and evidence to the LMS.
  6. Begin Task 8 case-study reading if time remains.

Evidence: Final Task 7 LMS submission.

Student Checklist

  • I can identify inputs, processing and outputs from a short scenario.
  • I can choose suitable data types for names, numbers, decimal values and true/false values.
  • I can write meaningful variable names that explain what is stored.
  • I can write a sequence of steps before coding.
  • I can use one-way, two-way or multi-way selection correctly.
  • I can use fixed, test-first or test-last iteration when a task repeats.
  • I can select normal, boundary and invalid test data.
  • I can complete a trace table for a loop or decision.
  • I can identify syntax, run-time and logical errors.
  • I can add comments that explain important logic.
  • I can submit my final program and evidence through the LMS.

Common Mistakes To Avoid

Starting with interface design

Build the required logic first.

Using copied blocks instead of iteration

Use a loop when the scenario asks for repeated work.

Boundary values fail

Check whether the rule includes values such as 30 and 60.

Trace table does not match the code

Trace the exact variables and updates from the program.

Final count appears after every loop

Place final summary output after the loop when it should appear once.

No evidence of debugging

Record at least one issue found or corrected.

Useful Guides This Week

Weekly Checkpoint

By the end of the week, your Task 7 practical file and evidence must be submitted through the LMS.