Choosing the aspect of a problem to develop

Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.

Choosing the aspect of a problem to develop

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

1. A school canteen app problem has parts: online ordering, stock tracking, staff rostering. Which is a sound way to pick the aspect to develop?
A Compare each part by importance to stakeholders and how feasible it is to build in the time available
B Pick the part that sounds most impressive, even if you can't finish it
2. Which statement of a chosen aspect is clearer?
A The solution will develop an online ordering system so students can pre-order lunch before school.
B The solution will fix the canteen and make everything better for everyone.
3. Why must you link the chosen aspect to stakeholder needs?
A So you can avoid talking to stakeholders for the rest of the project
B So the part you develop solves something the users and other stakeholders actually need
4. A part is very important but needs skills and tools you don't have, and you only have 10 weeks. What does this show?
A It has low feasibility, so it may not be the best aspect to choose
B Importance is all that matters, so you should choose it anyway
5. How many aspects of the problem does your solution develop as its chosen aspect?
A Every sub-problem identified
B One manageable part

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left columnRight column
1Chosen aspect: online canteen ordering AA clear statement of the one part of the problem the solution will develop
2Importance: High | Feasibility: High BJustification: Students need shorter queues, so ordering ahead is the aspect to develop.
3The aspect is linked to a stakeholder need so the choice is justified CThe choice is not one manageable part. It tries to cover the whole problem, so the scope is too big and unclear.
4Parts of a problem are compared by importance and feasibility before one is selected DPart A: Importance 5, Feasibility 2 | Part B: Importance 4, Feasibility 5 -> choose Part B
5Chosen aspect: develop the whole school app with bookings, payments, timetables and messaging EThe choice is not justified by stakeholder needs or by importance and feasibility. It is only a personal preference.
6Chosen aspect: the timetable page, because I think it looks fun to code FA strong candidate for the chosen aspect because it matters a lot and can be built in the time and skills available

Definitions

Chosen aspect

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1.
IF importance = "high" ___ feasible = TRUE
2.
score ← importance + ___________
3.
IF score _ bestScore THEN bestScore ← score chosenAspect ← aspect
4.
reason ← "Meets need of " + ___________
5.
_____ "Chosen: " + chosenAspect

Spot the Error

Shade in the letter of the line that contains an error.

Question 1
A best ← 0
B for each part in parts
C score ← imp + feas
D if score < best then
E best ← score
Question 2
A budget ← 2000
B if cost > budget then
C feasible ← true
D else
E feasible ← false
Question 3
A stakeholder ← "Canteen staff"
B need ← "fewer queues"
C aspect ← "Colour theme"
D print "Meets: " + need
Question 4
A top ← 100
B for each p in parts
C if p.score > top then
D top ← p.score
Question 5
A problem ← "Slow canteen service"
B aspect ← "Fix everything"
C print "Chosen: " + aspect

Answer Key

Choosing the aspect of a problem to develop
Section A: Quick Questions
Q1
A — Compare each part by importance to stakeholders and how feasible it is to build in the time available
Q2
A — The solution will develop an online ordering system so students can pre-order lunch before school.
Q3
B — So the part you develop solves something the users and other stakeholders actually need
Q4
A — It has low feasibility, so it may not be the best aspect to choose
Q5
B — One manageable part
Section B: Match the Pairs
Q1
Chosen aspect: online canteen ordering → A clear statement of the one part of the problem the solution will develop
Q2
Importance: High | Feasibility: High → A strong candidate for the chosen aspect because it matters a lot and can be built in the time and skills available
Q3
The aspect is linked to a stakeholder need so the choice is justified → Justification: Students need shorter queues, so ordering ahead is the aspect to develop.
Q4
Parts of a problem are compared by importance and feasibility before one is selected → Part A: Importance 5, Feasibility 2 | Part B: Importance 4, Feasibility 5 -> choose Part B
Q5
Chosen aspect: develop the whole school app with bookings, payments, timetables and messaging → The choice is not one manageable part. It tries to cover the whole problem, so the scope is too big and unclear.
Q6
Chosen aspect: the timetable page, because I think it looks fun to code → The choice is not justified by stakeholder needs or by importance and feasibility. It is only a personal preference.
Section C: Definitions
Q1
Chosen aspect — The one manageable part of a problem your solution will develop, picked by importance and feasibility, linked to stakeholder needs, and justified.
Section D: Fill in the Blanks
Q1
IF importance = "high" AND feasible = TRUE
Q2
score ← importance + feasibility
Q3
IF score > bestScore THEN bestScore ← score chosenAspect ← aspect
Q4
reason ← "Meets need of " + stakeholder
Q5
print "Chosen: " + chosenAspect
Section E: Spot the Error
Q1
D — To find the most important and feasible part, you update best when the new score is greater than best. Using < would keep the lowest score. It should be: if score > best then.
Q2
B — A part is feasible when its cost fits within the budget. The test marks it feasible when it costs more than the budget. It should be: if cost <= budget then.
Q3
C — The chosen aspect must be linked to a stakeholder need. A colour theme does nothing for fewer queues. It should be an aspect like "Online ordering" that addresses the need.
Q4
A — The starting value must be low (0) so the first part's score can beat it. Starting at 100 means no part is ever chosen. It should be: top ← 0.
Q5
B — The chosen aspect must be stated clearly as one manageable part of the problem. "Fix everything" is vague and far too broad. It should name one specific part, such as "Online ordering".