By the end you will have:
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.
Create a timeline of 5–8 key milestones from your project so far. Use this table like this:
| Date/Week | Milestone | What happened |
|---|---|---|
| Week 1 | Theme chosen | Selected wildfire risk after brainstorming |
| Week 2 | Research completed | Gathered data on wildfire factors from reliable sources |
| Week 3 | Design finalised | |
| Week 4 | Embedded hardware wired | |
| Week 5 | Basic code working | |
| Week 6 | Model coded | |
| Today | Full testing done |
Document your tests in this format (add at least 5 rows):
| Test # | What tested | Expected result | Actual result | Pass/Fail |
|---|---|---|---|---|
| 1 | Soil moisture sensor reading | 0–100 % scale | ||
| 2 | Temperature input in high conditions | |||
| 3 | Output trigger (e.g., buzzer on high risk) | |||
| 4 | Data storage over 10 minutes | |||
| 5 | What-if scenario 1 in model |
For failed tests, explain fixes in your narrative explanation. Run any new tests and fix issues.
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.