- Computing and data
- Grade 11
Software engineering in practice – 11th Grade
Most of what goes wrong in a project was agreed in a corridor and never written down. What changes when a program stops being one student's file and becomes something a team keeps alive: writing down what it must do, splitting it into parts with clear edges, holding a history of every change, testing on purpose, and reviewing each other's work without anyone taking offence.
All lessons in Software engineering in practice (in learning order)
Common questions
What is Writing down what the program must do before building it?
Most of what goes wrong in a project was agreed in a corridor and never written down. A requirement that can be tested is the difference between finished and nearly finished.
What is Drawing the parts and the edges between them?
A design says which part is responsible for what and what each one is allowed to ask of the others. Where the lines fall decides how much has to change when a requirement changes.
What is Naming things so the next reader does not have to ask?
Code is read many more times than it is written, and usually by someone who was not in the room. A name that says what a thing is for saves more time than any clever shortening.
What is A record of every change, and the ability to return?
Version control keeps the project's whole past, so the question is never whether a change can be undone but which point you want to stand at. A change described in one honest sentence is worth more than a large one nobody can explain.
What does Software engineering in practice for 11th Grade cover?
What changes when a program stops being one student's file and becomes something a team keeps alive: writing down what it must do, splitting it into parts with clear edges, holding a history of every change, testing on purpose, and reviewing each other's work without anyone taking offence. The unit includes 7 ordered lessons covering Writing down what the program must do before building it, Drawing the parts and the edges between them, Naming things so the next reader does not have to ask, A record of every change, and the ability to return.