# Software engineering in practice – 11th Grade

> Written with AI · Grade 11 · 2026-11-01 · https://lessoons.com/en/software-engineering-in-practice

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.

## Lessons in this topic (in learning order)

1. [What is Writing down what the program must do before building it?](https://lessoons.com/en/software-engineering-in-practice#lesson-1) (Grade 11) — 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.
2. [What is Drawing the parts and the edges between them?](https://lessoons.com/en/software-engineering-in-practice#lesson-2) (Grade 11) — 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.
3. [What is Naming things so the next reader does not have to ask?](https://lessoons.com/en/software-engineering-in-practice#lesson-3) (Grade 11) — 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.
4. [What is A record of every change, and the ability to return?](https://lessoons.com/en/software-engineering-in-practice#lesson-4) (Grade 11) — 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.
5. [What is Two people editing the same file, and how the merge is settled?](https://lessoons.com/en/software-engineering-in-practice#lesson-5) (Grade 11) — Working in parallel is the point of a team and the source of its collisions. Branching keeps the work apart on purpose, and merging is the moment where a person, not a tool, decides what the truth is.
6. [What is Tests that fail on purpose so the program does not fail later?](https://lessoons.com/en/software-engineering-in-practice#lesson-6) (Grade 11) — A test is a claim about behaviour that the machine can check every time. The valuable ones are the awkward cases: the empty list, the value at the edge, the input nobody expected a user to type.
7. [What is Reading someone else's code and saying something useful about it?](https://lessoons.com/en/software-engineering-in-practice#lesson-7) (Grade 11) — Review is where a team's standard actually lives. The skill is separating what is genuinely wrong from what is merely not how you would have written it, and saying the first clearly and the second lightly.

## Frequently Asked 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.
