Computer Science
Advanced
80 mins
Teacher/Student led
What you need:
Chromebook/Laptop/PC

Testing, Debugging, and Milestones

In this lesson, you will log key milestones from your project using a timeline table, document comprehensive testing of your embedded system and model with results, identify and resolve at least one encountered problem, and detail your Python model or embedded algorithm. Finally, compile these into an 800-word Create section to meet the brief's requirements.
Learning Goals Learning Outcomes Teacher Notes

Teacher Class Feed

Load previous activity

    1 - Objectives

    By the end you will have:

    • Logged all your key development milestones so far
    • Carried out and documented full testing of your embedded system and model
    • Identified, explained, and solved at least one real problem you encountered
    • Detailed either your Python model or embedded algorithm (depending on what you built)
    • A complete Create section (approximately 800 words, worth 20 marks)

    2 - What the Brief Requires for the Create Section

    From page 9 of the official brief:

    “This section should include a description of the key milestones of the development process. You should describe the testing that took place throughout the development process. You should explain one of the problems that you encountered during the implementation and describe how you overcame the problem. You should describe, in detail, the model you have programmed as part of your coursework project. If you do not have a model, you should explain, in detail, the algorithm you designed for your embedded system.”

    These four elements are exactly how the 20 marks are awarded in this section.

    3 - Key Milestones You Must Describe

    Create a timeline of 5–8 key milestones from your project so far. Use this table like this:

    Date/WeekMilestoneWhat happened
    Week 1Theme chosenSelected wildfire risk after brainstorming
    Week 2Research completedGathered data on wildfire factors from reliable sources
    Week 3Design finalised
    Week 4Embedded hardware wired
    Week 5Basic code working
    Week 6Model coded
    TodayFull testing done

    4 - Testing Throughout Development

    Document your tests in this format (add at least 5 rows):

    Test #What testedExpected resultActual resultPass/Fail
    1Soil moisture sensor reading0–100 % scale
    2Temperature input in high conditions
    3Output trigger (e.g., buzzer on high risk)
    4Data storage over 10 minutes
    5What-if scenario 1 in model

    For failed tests, explain fixes in your narrative explanation. Run any new tests and fix issues.

    5 - Explain One Problem and How You Overcame It

    Choose a real issue you faced (e.g., inaccurate sensor readings, code loop crashing, data not loading in model). Use this template:

    During implementation, I encountered a problem where [describe the problem in 2–3 sentences].

    To solve it, I [steps you took, e.g., researched online, changed code, recalibrated hardware].

    After this fix, the system [how it improved].

    Aim for 150–200 words here.

    Unlock the Full Learning Experience

    Get ready to embark on an incredible learning journey! Get access to this lesson and hundreds more in our Digital Skills Curriculum.

    Copyright Notice
    This lesson is copyright of DigitalSkills.org 2017 - 2025. Unauthorised use, copying or distribution is not allowed.
    🍪 Our website uses cookies to make your browsing experience better. By using our website you agree to our use of cookies. Learn more