AdvertisementYour brand could be hereYour brand hereOn every Darslab page · students, parents and teachersinfo@darslab.comAsk for pricesPricesinfo@darslab.com
☰ Year plan · Computing

Build it in small steps

Week 14 · 1.9 Physical computing · 3 lessons
3

Judge your own work

Computing 9: Topic 1.9, pp. 155–167
GoalEvaluate how a micro:bit project was built, with positive and negative points about the product, the way of working and the teamwork.
New words
evaluation · a review that gives both the good points and the weak points of somethingdevelopment log · a short record of each version: what was added, how the test went and what changed
Explanation

When a project ends, evaluate it. An evaluation says what went well and what went wrong, and gives a reason for each. Your points can be about three things: the final product, the way you made it, and how you worked with other people. A development log makes this easy, because it lists every version, test and change. Positive points are not boasting, and negative points are not blame: both help the next project. A good evaluation is specific. ‘It was fine’ says nothing, but ‘the test at 10 jumps failed because I used > 10, and I fixed it’ tells the reader something useful.

Area to coverExample question
The final productdoes it meet every requirement?
The way it was madewhich tests found faults, and how were they fixed?
Working with otherswere the jobs shared fairly, and did we listen to each other?
Worked examples
VersionAddedTest resultWhat changed
1count and show jumpspassednothing
2button B starts againpassednothing
3happy face at 10 or morefailed at 10 jumps> 10 changed to > 9
4radio to the coachcoach’s lights stayed blanknot finished
A development log for the jump counter. Each row is one pass round the loop. The log shows that only one pass, version 3, ended in a change to the code. It also shows the one thing that was never finished: the radio version.
StatementPositive or negative?Area
The counter shows the right number after every shake.positiveproduct
Our test at 10 jumps failed because we used > 10.negativeway it was made
Building one part at a time made faults easy to find.positiveway it was made
We ran out of time, so the radio part does not work.negativeproduct
Mia built the code and Leo wrote the tests, and we checked each other’s work.positiveworking with others
Sorting evaluation points. Every sentence is a point about the project. The table says whether it is positive or negative and which area it belongs to. The sentence about the radio is negative, because the product does not meet its fourth requirement.
Skipper’s micro:bitradio set group4setjumpsto0on startchangejumpsby1radio send numberjumpson shakeCoach’s micro:bitradio set group5on startshow numberreceivedNumberon radio receivedreceivedNumber
Version 4, the radio part. The skipper’s micro:bit sends the number in group 4, but the coach’s micro:bit listens in group 5. Only micro:bits in the same group hear each other. The user shakes three times and the coach’s lights stay blank. Changing the coach’s group to 4 would make them show 1, 2 and 3.
Class activity

Write an evaluation (no computer). Think of a group job you did, such as making a poster or planning a picnic, or use an invented micro:bit project. Draw three columns: product, way it was made, working with others. In each column write one positive point and one negative point, each with a reason. Read them to a partner. Did every point say what happened, or are some too vague, like ‘it was good’?

Practice
1
Say whether each statement is positive or negative, and whether it is about the product, the way it was made, or working with others. (a) Our program never stopped working in testing. (b) We did not write the requirements, so we kept changing our minds. (c) Ravi did all the work while Omar waited. (d) The finished program did only 2 of the 4 requirements. (e) Testing after each change helped us find mistakes early.
2
The sender’s micro:bit and the receiver’s micro:bit are both in group 6. The user presses A, then B, then A. What does the receiver show after each press?
Sender (group 6)radio set group6on startradio send number2on buttonApressedradio send number8on buttonBpressedReceiver (group 6)radio set group6on startshow iconyesshow numberreceivedNumberifreceivedNumber>5thenelseon radio receivedreceivedNumber
3
The user presses A once. What do the lights show, in order, and how long do the three pauses take altogether?
Start countdownsettimeto3show numbertimepause (ms)1000changetimeby-1show numbertimepause (ms)1000changetimeby-1show numbertimepause (ms)1000show iconyeson buttonApressed
4
Use the log to write an evaluation of this door-sign project. Give at least one positive and one negative point, and name the area of each.
VersionAddedTest resultWhat changed
1A shows the yes iconpassednothing
2B shows the no iconA after B still showed nowrong block in A, replaced
3shake shows a sad facenot startedran out of time