← QCE Digital Solutions Unit 1

Spotting missing or ambiguous information in a problem description

Details a problem description leaves out or words vaguely. List these gaps, note your assumptions, and ask the client questions to fill them before you design a solution.

Part of: QCE Digital Solutions Unit 1 — Understanding Digital Problems — Module 45

Understanding Spotting missing or ambiguous information in a problem description in QCE Digital Solutions Unit 1

What it does: The code line records a guess and flags it to be checked, which is how assumptions should be handled. The question asks for exactly the missing information about data, so the gap can be filled before design. Words like fast, easy or better are ambiguous. Ask the client for a measurable target before designing. Not knowing the users is a missing detail. It changes the needs, the accessibility features and the interface. Ask the client specific questions that fill the gap. Guessing risks building the wrong solution. Missing data details must be confirmed with the client. Collecting too much or too little data both cause problems.

Common mistakes: An assumption must be noted and then confirmed with the client. Skipping the check risks designing for the wrong users. It should read 'Assume: Year 7s - confirm'. You read the brief closely and find the gaps before building anything. Coding at once means the gaps are never found or filled. Step 1 should be 'read the brief closely'.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Spotting missing or ambiguous information in a problem description to a class →

This module's key terms are also in a printable crossword (Modules 1–58) and word search (Modules 1–81).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
A client says: "I need an app that is fast." What is the main issue with this description?
"Fast" is vague, so ask how fast, such as a load time in secondsIt is complete because every app should be fast
Matches
Description says 'lots of students'. Assume 500 and start building.
↓
Assuming a number for a vague phrase and building without confirming. The assumption should be listed and the client asked for the actual number.
Applying
Meanings
Term
missing or ambiguous information
Meaning
Details a problem description leaves out or words vaguely. List these gaps, note your assumptions, and ask the client questions to fill them before you design a solution.
Practice
Vague: quickly - how fast is quick?
Testing
Gaps
Gap type:
Check Answer
Spots
3Missing: who the users are
4Assume: Year 7s - skip asking

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Badger' badge — Determined Digger, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. A client says: "I need an app that is fast." What is the main issue with this description?
A. It is complete because every app should be fast
B. "Fast" is vague, so ask how fast, such as a load time in seconds ✓
Words like fast, easy or better are ambiguous. Ask the client for a measurable target before designing.
2. A school wants a booking system but does not say who will use it. What kind of gap is this?
A. Missing detail about users: are they students, teachers or parents? ✓
B. Missing detail about the colour scheme only
Not knowing the users is a missing detail. It changes the needs, the accessibility features and the interface.
3. Which is a good question to ask the client to fill a gap?
A. How many customers will use the system at the same time? ✓
B. Can I just guess how many customers there will be?
Ask the client specific questions that fill the gap. Guessing risks building the wrong solution.
4. A description says "store the customer data" but not which data. What should you do?
A. List it as a gap and ask which data items must be stored ✓
B. Store every piece of data you can think of
Missing data details must be confirmed with the client. Collecting too much or too little data both cause problems.
5. You assume that a gym app only needs to work on phones. What is the best next step?
A. Treat it as true and start designing
B. Write the assumption down and confirm it with the client ✓
Assumptions must be noted and checked. An unconfirmed assumption can lead to a solution that does not fit the need.

Match the Pairs

"Make it fast" - how fast? (no number given) → Vague wording: a word like fast has no measure, so ask the client for a number such as a time limit
Gap: Who will use the app? Ages? Skills? → Missing detail about users: the description does not say who the users are, so you record the gap and ask the client
An assumption is a guess you make about a gap, so you write it down and confirm it with the client → Assumption: users have a phone. Confirm with client?
A good client question targets a missing data detail and asks for a specific answer → Question: What data must be stored, and for how long?
Description says 'lots of students'. Assume 500 and start building. → Assuming a number for a vague phrase and building without confirming. The assumption should be listed and the client asked for the actual number.
Gaps found: none. The description looks fine, so no questions needed. → Not checking for missing details. Descriptions often leave out users, data or limits, so you should list gaps and ask questions.

Key Term

missing or ambiguous information
Details a problem description leaves out or words vaguely. List these gaps, note your assumptions, and ask the client questions to fill them before you design a solution.

Fill in the Blanks

1. Statement: "The app should load quickly." Gap type: vague Question: How many seconds is "quickly"?
Hint: Type the gap type for wording that can be read in many different ways.
2. Statement: "Store each student's results." Gap type: missing Question: Which data fields are stored?
Hint: Type the gap type for information that has been left out of the description.
3. Statement: "Staff will use the system." Assumption: Staff all have school laptops. Action: confirm it with the client
Hint: Type the verb for checking that an assumption is true before you rely on it.
4. Gap: the users are not stated Fill it by asking the client a question
Hint: Type the person who gave you the brief and can answer your questions.
5. Statement: "Show the best results." Vague word: "best" Question: What makes a result the best?
Hint: Type the vague word in the statement that has no clear measure.

Spot the Error

Question 1
A Brief: "A fast quiz app"
B Vague: "fast" - how fast?
C Missing: who the users are
D Assume: Year 7s - skip asking
E Ask: "Who will use the quiz?"
Line D — An assumption must be noted and then confirmed with the client. Skipping the check risks designing for the wrong users. It should read 'Assume: Year 7s - confirm'.
Question 2
A Step 1: start coding at once
B Step 2: list missing details
C Step 3: ask the client
D Step 4: then design
Line A — You read the brief closely and find the gaps before building anything. Coding at once means the gaps are never found or filled. Step 1 should be 'read the brief closely'.
Question 3
A Brief: "Make the site easy"
B Vague: "easy" means one click
C Ask: "What does easy mean?"
Line B — 'Easy' is vague wording, and this line treats a guess about its meaning as fact. Log it as vague and ask the client, e.g. 'Vague: "easy" - for whom?'.
Question 4
A Brief: "Show the weather"
B Missing: which town?
C Missing: how often it updates
D Ask: "Do you like weather?"
Line D — Client questions must target the missing details (location and update rate). Asking about personal opinion fills no gap. It should be 'Ask: "Which towns, how often?"'.
Question 5
A Brief: "App for the canteen"
B Missing: do users pay online?
C Assume: online pay is a fact
D Ask: "Will users pay online?"
Line C — An assumption is a guess that still needs confirming, so it cannot be called a fact. The line should read 'Assume: online pay - confirm'.

Student with a class code? Join your class →