Learn
B1.1.1 | PROBLEM SPECIFICATION
01 | BEFORE YOU BUILD ANYTHING
“Our equipment loans are a mess. Can you make an app?” This sounds like a programming task, but it leaves almost everything important unanswered. Who lends the equipment? What counts as available? What happens when an item is returned? How would anyone know the app had solved the problem?
Writing code immediately means guessing these answers. A program can run without errors and still solve the wrong problem. A problem specification is a clear description of the problem, what a successful solution must achieve and the boundaries within which it must work.
In this common SL/HL lesson, you will construct one step by step for a fictional school equipment-loan service. You do not need to design an algorithm or choose a programming framework yet.
02 | WHAT DOES CONSTRUCT REQUIRE?
The IB command term construct means to display information in a diagrammatic or logical form. Here you need to create the specification itself, not simply describe what a specification is.
An answer that says “include inputs and outputs” names two headings. An answer that specifies “the librarian enters a StudentID and EquipmentID; the system displays a confirmation containing the loan reference and due date” actually supplies their content.
Use details from the scenario, organise them clearly and check that they fit together. Where a scenario leaves something important unknown, record a question or an explicit assumption instead of silently inventing a fact.
03 | SIX CONNECTED PARTS
The IB content identifies a problem statement, constraints and limitations, objectives and goals, input specifications, output specifications and evaluation criteria. Think of these as connected views of the same problem rather than six unrelated lists.
| Part | Question it answers | Equipment-loan example |
|---|---|---|
| Problem statement | What is wrong, for whom, and why does it matter? | Staff cannot reliably identify which items are on loan. |
| Objectives and goals | What outcomes must improve? | Show whether an item is available and record each loan and return. |
| Constraints and limitations | What boundaries or restrictions apply? | Use the existing school computer; no live tracking of physical equipment. |
| Input specifications | What data enters, in what form, under what rules? | Required student and equipment identifiers selected from current records. |
| Output specifications | What information is produced, for whom, and when? | A confirmation for staff after a successful loan. |
| Evaluation criteria | What evidence would demonstrate success? | A second active loan for the same item is rejected without changing its existing loan. |
04 | UNDERSTAND THE CURRENT SITUATION
The librarian currently writes a student’s name, equipment description and loan date in a notebook. Return entries are sometimes missed, and two items have similar descriptions. Staff waste time checking shelves and asking colleagues before lending anything.
Notice that “we need an app” describes a proposed response. The underlying problem is unreliable loan information and the resulting delays. Keeping these separate allows people to consider whether better procedures, a spreadsheet or a dedicated system would be appropriate.
A useful problem statement describes the current difficulty and its consequences. It does not have to promise a particular technology before the requirements are understood.
05 | ASK THE PEOPLE AFFECTED
A stakeholder is someone who affects, uses or is affected by the proposed solution. The librarian records loans, students borrow equipment, technicians maintain the device and school managers may approve resources. Their needs can differ.
Ask the librarian to demonstrate a typical loan and return. Observe what happens when information is missing. Examine a suitably anonymised example of the current records. Ask the technician which equipment and software can be used.
“Would you like a good app?” reveals little. “What must you check before lending an item?” and “What should happen if that item already has an active loan?” reveal rules that can become precise requirements.
06 | WRITE A FOCUSED PROBLEM STATEMENT
A weak statement is “The school needs a better system.” It gives neither the affected process nor the reason for change. A stronger statement identifies the people, current process, difficulty and effect.
Worked statement: The school librarian records equipment loans and returns in a paper notebook. Incomplete return entries and ambiguous equipment descriptions make it difficult to identify current borrowers and available items, delaying lending. A solution is needed to maintain an accurate record of active loans and completed returns for staff at the lending desk.
This statement establishes the purpose without deciding screen colours, table layouts or specific code. Those decisions come later.
07 | GOALS BECOME SPECIFIC OBJECTIVES
A goal is a broad intended outcome, such as improving the reliability of lending records. An objective is a more specific result that contributes to that goal. The distinction helps you move from an aspiration to something a solution can actually deliver.
For this example, objectives are to record each accepted loan against a student and a uniquely identified item, show whether an item has an active loan, record its return and display overdue active loans. Each describes an observable capability or outcome.
“Make it efficient” is too open to interpretation. “Display an item’s active-loan status when staff select its EquipmentID” is clearer. If speed matters, agree a measurable response target and the conditions under which it will be checked.
08 | SCOPE: DRAW THE BOUNDARY
Scope defines what the proposed solution covers. Our first version covers staff recording loans and returns for school equipment. It does not cover buying equipment, collecting fines, parent messaging or students reserving items from home.
Explicit exclusions prevent different people from expecting different products. They also keep a small project achievable. Excluding online reservations is a boundary for this version; it does not claim reservations are inherently impossible.
A student specification should solve the given problem at a manageable scale. Adding every imaginable feature can create contradictions and distract from the required outcome.
09 | CONSTRAINTS AND LIMITATIONS
A constraint restricts the choices available when producing or operating the solution. The school may require the existing desktop computer, no paid subscriptions and completion within six weeks. These shape what can be delivered.
A limitation describes a boundary in capability or effectiveness. A record-based system cannot physically check whether equipment has really been returned; staff still need to inspect the item and record the event. Incorrect source records can also affect results.
These words sometimes overlap in practice. Explain the actual restriction and its consequence rather than relying only on a label. An offline-only constraint also limits remote access. Do not invent a budget or deadline unless the scenario supplies it or you clearly mark it as an agreed example assumption.
10 | AGREE THE RULES BEFORE CODING
Requirements often hide small but important decisions. Can a student borrow several items? How long does a loan last? Can an item be loaned twice at once? What counts as overdue?
For our worked example, assume the librarian has agreed: a student may borrow several different items; each item may have at most one active loan; loans are due seven calendar days after issue; overdue means an active loan whose due date is earlier than today. The due date itself is not overdue.
These are fictional rules agreed for this lesson, not universal school policies. A real project must confirm them. A specification becomes useful when terms such as “active” and “overdue” have one consistent meaning.
11 | INPUT IS MORE THAN A FIELD NAME
An input specification describes the data a solution receives, where it comes from, its form and the rules it must satisfy. “Student details” is too vague to tell a developer or tester what is needed.
When staff record a loan, they select a StudentID and EquipmentID from current records. The date of issue comes from the computer’s current date. A calculated due date is derived from that date; staff do not enter the due date in this version.
Separate user-entered data, data retrieved from existing records and automatically obtained values. Something needed by a computation is not automatically a new field for a person to type.
12 | WORKED INPUT SPECIFICATION
| Data and source | Form / example | Required rules and handling |
|---|---|---|
| StudentID: staff selection from student records | Text identifier, e.g. S0042 | Required; must identify an existing current student. Missing or unknown IDs prevent saving. |
| EquipmentID: staff selection from equipment records | Text identifier, e.g. E0017 | Required; must identify an existing item with no active loan. |
| IssueDate: computer date on acceptance | Date, e.g. 2026-10-24 | Automatically obtained; staff must keep the device date correct. |
| Return action: staff select an active loan | LoanID, e.g. L0123 | Must refer to an active loan; a completed loan cannot be returned a second time. |
| Report date: computer date when report opens | Date | Used to compare with due dates; staff do not type a separate report date. |
The identifier examples illustrate the school’s current records; a character pattern alone does not prove that an ID exists. If an input is invalid, the system displays a reason and does not save a partial transaction.
13 | VALID DATA IS NOT AUTOMATICALLY TRUE
Validation checks whether data meets stated rules. An unknown EquipmentID can be rejected by checking existing records. A selected item with an active loan can be rejected by checking its current status.
However, selecting a valid student does not prove that the selected student is the person at the desk. The librarian must confirm the borrower. Similarly, clicking “Return” does not prove that an item has physically arrived in good condition.
Include these practical responsibilities in the specification where they affect success. Do not claim that software can guarantee real-world truth simply by checking a format or displaying a confirmation.
14 | OUTPUTS NEED AN AUDIENCE AND A TRIGGER
An output specification describes what information is produced, its form, who receives it and when it appears. “A report” is incomplete: which report, containing which values, for whom?
After an accepted loan, staff see its LoanID, StudentID, EquipmentID, issue date and due date. After a rejected loan, staff see the reason and the existing loan remains unchanged. The feedback is an output even though no new loan was saved.
A due date is produced by processing the issue date. An overdue report is produced from stored active loans. Neither requires staff to re-enter all the information each time.
15 | WORKED OUTPUT SPECIFICATION
| Output | Contents and form | Audience and trigger |
|---|---|---|
| Loan confirmation | On-screen LoanID, StudentID, EquipmentID, IssueDate, DueDate | Librarian immediately after an accepted loan. |
| Rejection message | On-screen reason such as “Item already on loan”; no new loan created | Librarian after an invalid request. |
| Item status | Available, or On loan with current LoanID and DueDate | Librarian after selecting an EquipmentID. |
| Overdue report | On-screen table of LoanID, StudentID, EquipmentID and DueDate; ordered by earliest due date, then LoanID | Librarian when opening the report; show “No overdue loans” when empty. |
| Return confirmation | LoanID, EquipmentID and recorded return date | Librarian after an accepted return. |
The report is for authorised staff rather than a public screen. Access expectations belong in the requirements, even though the detailed authentication design is a later decision.
16 | EVALUATION CRITERIA MAKE SUCCESS CHECKABLE
An evaluation criterion is a stated basis for judging the solution. It needs an observable result and a way to gather evidence. “Works well” does not tell anyone what to check.
For example: “Given an available item and a valid student, accepting a loan creates one active loan containing those IDs, with a due date seven calendar days after issue.” A tester can supply a known example and inspect the result.
A test procedure then specifies the exact data, actions and expected result used to check that criterion. A specification can include illustrative tests, but a full test plan is a separate, more detailed artefact.
17 | FOLLOW ONE REQUIREMENT ALL THE WAY THROUGH
| ID / objective | Evaluation criterion | Example evidence |
|---|---|---|
| O1 Record loans | Accept valid IDs for an available item; create one active loan and display the specified confirmation. | Issue E0017 to S0042 on 24 October 2026; due date is 31 October 2026. Inspect the saved record and screen. |
| O2 Prevent simultaneous loans | Reject a loan for an item with an active loan; preserve the existing record and give a reason. | Attempt another loan of E0017 before its return. There is still exactly one active loan for E0017. |
| O3 Record returns | An accepted return completes the selected active loan and makes its item available. | Return L0123; inspect its return date, then confirm its EquipmentID can be lent again. |
| O4 Identify overdue items | Include only active loans whose due date is earlier than today. | Today 24 October: active due 23 included; active due 24 excluded; returned due 23 excluded. |
| O5 Protect staff-only functions | Only authorised staff can view loan records or change them. | Using the agreed staff and non-staff access cases, verify permitted and denied operations. |
Linking each objective to evidence is called traceability. It reveals objectives with no success check and tests that do not relate to any stated need.
18 | QUALITY MATTERS TOO
Functional requirements describe what the solution must do. Quality requirements describe how well it must operate or qualities it must have, such as usability, performance and accessibility. Both can affect whether it solves the problem.
For a classroom prototype, the librarian might agree that an item lookup should complete within two seconds on the existing school desktop with 1,000 equipment records. That target specifies the operation, limit, environment and workload. It is a fictional agreed target, not an IB-mandated number.
Usability can also be evaluated: after a short introduction, the librarian completes five representative loan/return tasks without developer help or errors. This gives useful evidence for that test, but does not prove every future user will succeed.
19 | ASSUMPTIONS ARE NOT CONFIRMED FACTS
An assumption is something provisionally taken as true. “The computer’s date is correct” may be a necessary operating assumption. “Students never lose items” is an unsafe way to avoid specifying a likely case.
Separate confirmed requirements, assumptions and unanswered questions. If the scenario does not say whether a damaged returned item can be borrowed again, record that question. Do not quietly build a policy into the code and present it as the user’s requirement.
When an assumption changes, review the affected inputs, rules, outputs and evaluation criteria together. A switch from calendar days to school days changes the due-date calculation and its tests.
20 | A COMPACT COMPLETE SPECIFICATION
Problem: The librarian needs reliable equipment availability and borrower information because paper loan and return records are incomplete and ambiguous.
Goal and scope: Support staff desk lending, returns, item-status lookup and overdue reporting. Exclude purchases, fines, reservations and physical item tracking.
Constraints and limitations: Use the existing desktop, no paid subscriptions, a six-week prototype period and one staff operator at a time. These are agreed fictional example conditions. Physical returns and the accuracy of current source records still depend on staff.
Inputs: Required existing StudentID and EquipmentID for a loan; a selected active LoanID for a return; computer date for issue, return and overdue comparison. Reject invalid operations without partially saving them.
Rules: One active loan per item; several different items per student permitted; due after seven calendar days; overdue only after the due date. Retain completed loan history.
Outputs: The confirmations, rejection messages, item status and ordered overdue report specified above, available only to authorised staff.
Evaluation: Apply O1–O5 and the agreed performance/usability checks. Record test evidence, unresolved assumptions and stakeholder feedback before judging success.
This is a worked teaching example. A larger or higher-risk system would need more detailed operational, security and data-handling requirements.
21 | REQUIREMENT OR DESIGN DECISION?
“Staff can find the current borrower for an item” is a requirement. “Use a blue button”, “store it in a Python dictionary” and “use a Flask route” are design or implementation choices unless a stakeholder has specifically imposed them as constraints.
A specification should give enough detail to determine correct behaviour without unnecessarily fixing how every part is built. If existing school policy requires a particular platform, record that as a confirmed constraint with its source.
Do not confuse being precise with writing code. You can precisely specify the due-date rule and rejection behaviour in plain language before selecting a language or algorithm.
22 | REPAIR A VAGUE REQUIREMENT
Choose a weak statement, then reveal a more testable version. Each improvement adds details that would need agreement in a real project.
23 | TRACE THE DUE-DATE RULE
Use this explorer to check the stated rule. The example evaluates one known loan, not a complete loan system. Dates are calendar dates, and a due date equal to the report date is not overdue.
24 | NOW CONSTRUCT YOUR OWN
A school environmental club currently collects workshop sign-ups on paper. Names are sometimes unreadable, staff cannot reliably see which sessions are full, and students need confirmation. Each workshop has a fixed capacity supplied by staff. A student may sign up once per workshop but may attend different workshops. The club can use an existing school computer and cannot pay for subscriptions.
Construct a problem specification in your book. Include a problem statement, objectives, scope, constraints/limitations, input and output specifications and measurable evaluation criteria. Consider a full workshop, a duplicate sign-up and a cancelled place. Identify what you would ask about cancellation and waiting-list rules.
Use a table to connect each objective to at least one evaluation criterion and example test. Label any invented policy as a proposed assumption requiring confirmation.
Reveal a suggested structure
Problem: unclear paper records make capacity and participation uncertain. Objectives: record valid sign-ups, prevent duplicate registrations, respect each workshop’s capacity and confirm the result. Inputs: required existing StudentID and WorkshopID; capacity retrieved from staff-maintained workshop data. Outputs: acceptance with the selected workshop, or a clear rejection reason; authorised staff see current participants and remaining places.
Evaluation examples: a new valid sign-up below capacity creates one registration; a repeated StudentID/WorkshopID pair creates none; a full workshop rejects the next request without exceeding capacity. Confirm who may cancel, whether cancellations release places and whether waiting lists exist before specifying those behaviours. Keep no-subscription and existing-computer constraints distinct from those unanswered policy questions.