Unit 5 project: A program for a real job

You have written five programs this unit, each one following the book. Now your group writes one of its own, for a real person with a real job — and tests it the way programmers do: by predicting every answer before the computer gives it.

Work in groups of 3–4. One period. Save as our-program.py, with the test table in tests.ods.

Pick one, or propose your own:

• The fair price — ask for two boxes' prices and weights; say which is cheaper per kilo, and by how much.
• The grader — ask for an apple's size and whether it has scab; print A, B, C or Reject.
• The class average — store a week's temperatures (or attendance counts) in a list; print the mean, the highest and the lowest.
• The fee helper — ask how many months are paid; print what's still due and whether it's overdue.

Your program must use all of these at least once:

• input() with int(...) or float(...)
• variables with clear names, like_this
• at least two operators
• if / elif / else
• a list or a for/while loop
• comments (# like this) explaining the tricky lines

In tests.ods, fill at least five rows: Input · What we predict · What it printed · Right?

• Three ordinary inputs.
• One edge case — a value right on a border, like exactly 8 cm.
• One bad input — a word where a number should be, or a zero where you divide. What happens? Is that acceptable for the person who'd use it?

Predict every row before you run it. Where a prediction was wrong, write which of you was wrong — you, or the program.

Swap programs with another group. Dry-run theirs on paper for one input you choose: a column for each variable, one row per line that runs, and the final output. Sign with your roll number. This part is marked for you alone.