A development log for Criterion D
A record of each build session written against the four strands criterion D is marked on, worth 12 of the 30 marks. Its top band asks for choices that are evaluated rather than explained, which means naming the alternative that was rejected — while it is still remembered.
- 12 marks
- 1,000 words
- Kept from week 7
Free to use. Students join their class with a code from their teacher; teachers can create classes and track progress.
What is inside
- One entry per build sessionDate, the success criterion it advanced, what was built, the technique, the alternative rejected and how it was tested.
- What the log is worthHow many sessions carry an evaluated choice, which is what separates the top two bands.
- Criteria with no build behind themSuccess criteria no session has been logged against, because functionality is a strand of the same criterion.
Preview
The four fields, and the strand each one feeds
The fields are not a diary template. Each one is a strand criterion D is marked on.
| Field | Strand |
|---|---|
| What I built, or what broke | Functionality |
| The technique I used | Techniques |
| What I rejected, and why | Choices |
| How I knew it worked | Testing strategy |