IB COMPUTER SCIENCE | B1 ASSESSMENT
COMPUTATIONAL THINKING: END OF TOPIC REVIEW
Assess problem specifications, computational thinking concepts and applications, and accurate flowchart tracing through quick checks, applied tasks and developed written responses.
BEFORE YOU BEGIN
This review covers B1.1.1–B1.1.4, common SL/HL content. Attempt it independently before checking feedback. Use more than one session if needed, allowing time for the complete traces and written specifications.
Sections A and B award one point for each fully correct automatic item, with no partial credit within an item. Section C has separately suggested content marks. These are original practice questions, not an official IB paper, grade boundary or prediction.
Write working and Section C answers in your exercise book before revealing guidance. Answers last while the page remains open.
Automatic total: 32 points. Suggested written total: 72 marks, assessed separately.
C | WRITTEN COMMUNICATION AND SUBJECT KNOWLEDGE
Write in your exercise book before revealing guidance. Use the IB command terms supplied in the guide. Main commands are highlighted in the questions. For explain, give the reason or mechanism, not merely a concept name. For trace, follow every relevant action, even where your final answer seems obvious.
| IB command term | What to provide | Practical approach |
|---|---|---|
| Construct | Display information in diagrammatic or logical form | Supply the actual organised specification, not merely its headings. |
| Describe | Give a detailed account | State relevant features and a specific example. |
| Explain | Give a detailed account including reasons or causes | Connect the action to its effect using because, therefore, resulting in or leading to. |
| Trace | Follow and record the actions of an algorithm | Record decisions, current values, consumed inputs and outputs as requested. |
| Distinguish | Make clear differences | Refer to the concepts and explicitly state how their roles differ. |
A connective earns no automatic mark by itself. For example, “retaining timestamps preserves the measurement interval, therefore a two-day total is not incorrectly presented as one day’s consumption” links accurate ideas. Suggested marks reward subject knowledge and the requested actions, not extra unofficial grammar marks.
C1 | SPECIFY A WORKSHOP BOOKING SERVICE
6 suggested marks | COMMON SL/HL
A school receives workshop sign-ups on paper. Entries can be unreadable and capacities are sometimes exceeded. Students may book different workshops but only once per workshop. Existing records contain StudentID, WorkshopID and capacities. The school must use its current computer and cannot pay for subscriptions. Construct a compact problem specification containing all six syllabus components. Treat unprovided policy details as questions or assumptions.
The paper process creates unclear registrations and overfilled workshops, affecting students and staff. The goal is reliable allocation; objectives are to record valid sign-ups and prevent duplicates and over-capacity bookings. Use the existing computer with no paid subscriptions; physical attendance remains outside what registration alone can prove. Inputs are required existing StudentID and WorkshopID, with capacity retrieved from workshop records. Outputs are acceptance or a reason for rejection and staff participant lists. Evaluate acceptance below capacity, duplicate rejection and rejection at capacity without changing existing bookings. Confirm cancellation policy rather than silently inventing it.
SUGGESTED MARKING POINTS
- Focused statement of current problem and affected people.
- Specific goal/objectives for reliable sign-ups and rules.
- Scenario-based constraints and a meaningful capability limitation.
- Inputs with existence/required rules and capacity source.
- Outputs with relevant audience or trigger.
- Observable evaluation criteria connected to the rules.
Writing focus: Supply scenario content under clear headings rather than only naming the six parts.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC2 | MAKE SUCCESS CHECKABLE
6 suggested marks | COMMON SL/HL
Explain how a vague requirement, “the lending system must work well”, can be improved into checkable requirements and evaluation evidence. Include one functional criterion, one performance criterion and the limits of the evidence.
State required behaviour, such as rejecting a second active loan for an item without altering its existing loan. A test supplies known starting records, attempts that loan and inspects the message and stored state. For performance, agree that an item lookup completes within two seconds on the school desktop with 1,000 records. The environment and workload make the result interpretable. Link each criterion to its objective, because this exposes untested needs. Passing these cases supports those requirements under tested conditions; it does not prove every future situation or user will succeed.
SUGGESTED MARKING POINTS
- Replace vague approval with observable behaviour.
- A valid functional criterion.
- Specific test data/actions or expected state for that criterion.
- A measurable performance target requiring agreement.
- Relevant environment/workload conditions.
- Explain traceability or the limited scope of test evidence.
Writing focus: Connect precise wording to the evidence it enables, using because or therefore accurately.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC3 | DATA RULES AND REAL-WORLD TRUTH
6 suggested marks | COMMON SL/HL
Explain why a valid StudentID and a recorded return do not guarantee an accurate real-world equipment-loan service. Include input, output and staff responsibilities.
Checking that StudentID exists establishes a data rule, but the selected ID may still belong to another person. Staff must confirm the borrower. Clicking Return changes a record but does not show the equipment has arrived or is undamaged, so staff inspect the item before recording the event. The return operation should identify an active loan and reject invalid repeats. A confirmation reports the stored operation; it is not independent proof of a physical event. These responsibilities and limits should be stated in the specification.
SUGGESTED MARKING POINTS
- Existing ID checks rule compliance.
- A valid but wrong student can still be selected.
- Staff confirm borrower identity.
- Recorded return does not prove physical arrival/condition.
- Active-loan input/repeated-return rule or appropriate output detail.
- Explain why confirmation and real-world evidence differ.
Writing focus: Develop the gap between data validity and truth rather than repeating that people make mistakes.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC4 | DISTINGUISH THE FOUR CONCEPTS
6 suggested marks | COMMON SL/HL
Describe the four fundamental computational thinking concepts using a school library example. Make clear what each contributes.
Abstraction represents members, physical copies and loans with relevant identifiers and states, omitting unrelated appearance details. Decomposition separates receiving requests, checking availability, recording loans and reporting. Pattern recognition identifies shared loan checks across item types, supporting a reusable procedure while preserving exceptions. Algorithmic design specifies the ordered checks, recording and confirmation. Selecting data differs from dividing work, and recognising a common rule differs from spelling out its exact execution.
SUGGESTED MARKING POINTS
- Abstraction described through relevant representation.
- Decomposition described through coherent smaller tasks.
- Pattern recognition described through useful shared structure.
- Algorithmic design described through precise ordered actions.
- Distinguish selecting detail from dividing the task.
- Distinguish recognising a shared structure from defining its steps.
Writing focus: Use a detailed account, with a concrete role for each concept.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC5 | REPAIR AN OVER-SIMPLIFIED MODEL
6 suggested marks | COMMON SL/HL
A booking model stores only workshop capacities and current counts. Each student may book a workshop once. Explain the weakness and how the model and method should change. Include a contrasting one-activity-per-trip rule.
Counts permit a capacity check but cannot identify whether a particular student is already booked. Retain the student/workshop associations and check the pair before adding a new booking. This preserves the distinctions required by the rule while omitting irrelevant detail. For a trip permitting only one activity overall, check whether StudentID already has any allocation, rather than only checking the selected pair. Otherwise a student could obtain places in two different activities.
SUGGESTED MARKING POINTS
- Counts can check capacity.
- Counts cannot detect individual duplicate bookings.
- Retain student/workshop associations.
- Check for the existing pair before saving.
- For the trip check any allocation by StudentID.
- Explain the consequence of incorrectly reusing the pair-only rule.
Writing focus: Link each missing distinction to the rule it prevents enforcing.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC6 | COMPUTATIONAL THINKING WITHOUT CODE
6 suggested marks | COMMON SL/HL
Explain how a teacher can use computational thinking to organise a sports event without programming. Include all four concepts and one reason to revisit the plan.
Represent relevant team sizes, facilities and available times while omitting irrelevant uniform decoration. Divide work into fixtures, equipment, registration and results. Recognise the repeated structure of matches and share a scheduling approach, checking any age-group exceptions. Write precise check-in and fixture-allocation steps that staff can follow on paper. This is systematic representation and problem solving even without executable code. A clash or new access requirement found during a trial can require changing the model and method.
SUGGESTED MARKING POINTS
- Relevant abstraction.
- Coherent decomposition.
- Useful pattern and checked exception.
- Precise manual procedure.
- Explain why programming is not required for these actions.
- A test or changed condition leading to revision.
Writing focus: Show how the actions help the event instead of only listing the concept names.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC7 | ANALYSE MISSING METER READINGS
6 suggested marks | COMMON SL/HL
Same-time cumulative readings are 1200 kWh on 1 October, 1230 on 2 October, 1275 on 3 October and 1345 on 5 October. Explain how computational thinking supports a reliable daily-use report and what cannot be concluded.
Retain timestamps, units and meter identity with values. Separate validation, ordering, interval calculation and reporting. Calculate successive differences as 30 kWh over one day, 45 over one day and 70 over two days. Recognising a possible weekday pattern may suggest investigation but not causation. Report the two-day interval explicitly; its average is 35 kWh per day, not evidence that both individual days used 35. Missing daily observations therefore limit the daily comparison.
SUGGESTED MARKING POINTS
- Retain relevant timestamps/units/meter identity.
- Decompose preparation/calculation/reporting.
- Correct successive differences 30,45,70.
- Respect one-day versus two-day intervals.
- Average 35 does not reveal each daily value.
- Pattern can suggest investigation but does not prove cause.
Writing focus: Make the interval and its consequence explicit.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC8 | PREDICT A DELIVERY DURATION
6 suggested marks | COMMON SL/HL
Explain how computational thinking helps plan machine learning to predict journey duration before departure. Address features, decomposition, patterns and evaluation.
Represent deliveries with legitimate known-in-advance features such as planned distance and stops, with duration as target. Exclude actual arrival time because it is unavailable at prediction time and would leak the answer. Divide preparation, fitting, evaluation and monitoring into tasks. Learn possible relationships such as greater distance tending to increase time without interpreting them automatically as causal. Separate evaluation data before fitting preprocessing and assess suitable unseen predictions. Changed traffic or route conditions can make past patterns less reliable, so monitor performance.
SUGGESTED MARKING POINTS
- Known-in-advance features and duration target.
- Identify unavailable arrival time as leakage.
- Useful decomposition of the workflow.
- Patterns learned from examples are not automatically causal.
- Appropriate separation of evaluation and fitting/preprocessing.
- Explain generalisation or changed-condition limit.
Writing focus: Connect the workflow choices to realistic prediction rather than impressive training scores.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC9 | INVESTIGATE UNUSUAL NETWORK ACTIVITY
6 suggested marks | COMMON SL/HL
Explain how abstraction, decomposition, pattern recognition and algorithmic design support a review of failed network connections. Use the fictional rule “more than 20 failures per five-minute window”, and explain its limits.
Retain source, timestamp and relevant event type so counts can be grouped into comparable windows. Divide collection, preparation, detection, investigation and response. Compare activity with an appropriate baseline to identify unusual rates. Specify counting failures per source/window and flagging only when count exceeds 20; 20 is not flagged, 21 is. A flag focuses investigation rather than proving an attack, because updates or misconfiguration can also be unusual. Lower thresholds may increase workload, and verified labels are needed to estimate error rates.
SUGGESTED MARKING POINTS
- Relevant abstraction with source and time.
- Decomposition of detection from investigation/response.
- Useful comparison with patterns or baseline.
- Explicit greater-than rule and equality boundary.
- Flag is not proof, with legitimate alternative explanation.
- Explain threshold workload or need for verified error evidence.
Writing focus: State the mechanism, consequence and a genuine limitation.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC10 | TRACE A COUNTED LOOP
6 suggested marks | COMMON SL/HL
Use CHART 3 in Section B with Limit=3. Trace the changing Count, decisions and output sequence. Then explain why the final Count differs from the final output.
| Action | Count | Decision / output |
|---|---|---|
| Initialise | 1 | No output |
| Test; output; increment | 2 | 1 ≤ 3 true; output 1; increment |
| Test; output; increment | 3 | 2 ≤ 3 true; output 2; increment |
| Test; output; increment | 4 | 3 ≤ 3 true; output 3; increment |
| Final test | 4 | 4 ≤ 3 false; END |
Outputs are 1, 2, 3. Count becomes 4 after the final output; the next false comparison exits before 4 can be output.
SUGGESTED MARKING POINTS
- Count initialised to 1.
- Correct first true test/output/increment.
- Correct second true test/output/increment.
- Correct third true test/output/increment.
- Final false test at Count = 4.
- Output sequence 1,2,3 distinguished from final Count = 4.
Writing focus: Follow and record actions; do not replace the trace with only a final number.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC11 | TRACE A RUNNING TOTAL
6 suggested marks | COMMON SL/HL
Use CHART 4 in Section B with inputs 4, 7, 0, 9. Trace the actions, Total, Number and output. Then explain what happens if the repeated INPUT inside the loop is removed.
Initialise Total=0. Read 4, test true, add to obtain 4. Read 7, test true, add to obtain 11. Read 0, test false, output 11 and END. Number finishes at 0; the final 9 is not consumed. If the repeated input is removed after reading 4, Number stays 4, the condition stays true and 4 is added repeatedly without reaching the exit.
SUGGESTED MARKING POINTS
- Total initialised to 0.
- Read/test/add 4 giving Total 4.
- Read/test/add 7 giving Total 11.
- Read 0 and false comparison without addition.
- Output 11 once and leave 9 unused.
- Explain unchanged nonzero Number causes non-termination without repeated input.
Writing focus: Separate consumed input, stored state and output; explain the first cause of the infinite run.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC12 | TRACE A POST-CONDITION LOOP
6 suggested marks | COMMON SL/HL
Use CHART 5 with inputs −2, 0, 5, 7. Trace the run. Explain why the body executes at least once and why a true decision exits this loop.
Read −2 and test −2>0: false, follow NO to input. Read 0 and test 0>0: false, repeat. Read 5 and test 5>0: true, follow YES to output5 and END. Seven is unused. The input body comes before the first test, so it executes at least once. The condition is a stopping condition, and the YES arrow leads out rather than back.
SUGGESTED MARKING POINTS
- Read −2, false and return.
- Read 0, false and return.
- Read 5, true and exit.
- Output 5 once and leave 7 unused.
- Body precedes test, so at least one execution.
- Explain true stopping condition follows the YES exit.
Writing focus: Follow the actual labelled arrows rather than assuming true always means continue.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentCHECK THE QUALITY OF YOUR RESPONSE
Did you supply a scenario-specific specification for construct, a detailed account for describe, a valid reason or cause for explain, and a recorded route for trace? Check that arrows, comparison boundaries, variables and outputs agree.
Use the six marking points for each written question as guidance: one suggested mark per distinct point. Avoid double-counting repeated wording. Equivalent accurate methods can be valid. Keep the suggested 72 written marks separate from the 32 automatic points, then rewrite two weak responses after revising.
YOUR NEXT REVISION STEP
Submit the automatic sections for targeted revision links.
Record your own written marks using the suggested points. Choose two weaknesses and attempt new examples after revising. Use the B1 revision page for worked content and a personal flashcard list, or return to the IB course index.