Before solving a problem, a computer scientist writes a clear problem specification so they understand every part of the problem first. A specification may include a problem statement, constraints and limitations, objectives and goals, input specifications, output specifications and evaluation criteria. This unit covers all six components. (This is B1.1.1, common to SL and HL, with no AHL-only material.)
Slide 1 / 4
Why write a problem specification
A computer scientist makes sure they understand every single word of a problem before thinking about how to solve it.
A specification may include six components: a problem statement, constraints and limitations, objectives and goals, input specifications, output specifications and evaluation criteria.
Writing it takes extra time but produces a much clearer solution to a well-understood problem.
It guides the whole build, including what data to process, how to store it and how to judge success.
Check you've got it
0/4
1. Which of these is the stronger problem statement?
2. "The project budget is limited to 10,000 dollars and this amount cannot be exceeded." Which component of a problem specification is this?
3. What best distinguishes a specific goal from a high-level objective in a problem specification?
4. Which of the following is one of the evaluation criteria the book recommends for judging a solution?
Free revision content. Multiple-choice answers are marked instantly. Written answers are marked by AI on /free-mark.