Co-developing requirements with a teacher or user

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Your teacher gives you a list of things your app must do. What is this?

A A final bug report

B Teacher-provided requirements

2. Which is a good way to find out what a user needs?

A Ask the user questions like 'What do you want the app to do?'

B Guess what the user wants and never check

3. You are making a quiz app for a Year 3 class. Which question helps you co-develop requirements?

A What will the Year 3 students need to see on the screen?

B What is my favourite colour?

4. After you and your classmates list ideas, what is the next step?

A Agree on a final list of requirements

B Throw the list away and start coding

5. Which one is a requirement the group could agree on?

A The app should be cool

B The app must have a big Start button

Match the Pairs

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

Left column		Right column
1Teacher-provided requirements		AAgree on a final list: 1. Big buttons 2. Show the score 3. Easy to read
2Ask the user: "What do you need this app to do?"		BThe group skipped agreeing on a final list. Talk it through and agree on the final requirements before building.
3After collecting ideas from the user and classmates, you check them together and agree on the final list.		CAsking the user questions to find out what the solution must do.
4Co-developing requirements means working together by asking, listing and agreeing.		DYour teacher gives you a list of things the solution must do, so you start with a clear brief.
5I made up the requirements by myself and never asked the user.		EAsk -> List -> Agree
6We wrote lots of ideas on the list but never agreed on which to keep.		FThe user was never asked, so the requirements may not match what they really need. Ask the user questions first.

Definitions

co-develop requirements

Fill in the Blanks

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

___ user "What do you need?"

requirements ← [] ADD "Show the score" TO ____________

ASK class "Do we all agree?" __ answer = "yes" THEN SAVE final_list

requirements ← ____________ ADD "Easy to read" TO requirements

ASK user "What do you need?" ADD ______ TO requirements SHOW requirements TO class

Spot the Error

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

Question 1

A GUESS what the user needs

B LIST each answer

C AGREE on the final list

Question 2

A READ the teacher's brief

B LIST only what I want

C CHECK the list with the teacher

Question 3

A ASK the user two questions

B WRITE down their answers

C SKIP agreeing on the list

Question 4

A ASK the user questions

B LIST every answer

C SHARE the list with the class

D AGREE on the first idea

Question 5

A READ the teacher's list

B ASK if anything is unclear

C AGREE on the final list

D BUILD using my own ideas

Answer Key

Co-developing requirements with a teacher or user

Section A: Quick Questions

B — Teacher-provided requirements

A — Ask the user questions like 'What do you want the app to do?'

A — What will the Year 3 students need to see on the screen?

A — Agree on a final list of requirements

B — The app must have a big Start button

Section B: Match the Pairs

Teacher-provided requirements → Your teacher gives you a list of things the solution must do, so you start with a clear brief.

Ask the user: "What do you need this app to do?" → Asking the user questions to find out what the solution must do.

After collecting ideas from the user and classmates, you check them together and agree on the final list. → Agree on a final list: 1. Big buttons 2. Show the score 3. Easy to read

Co-developing requirements means working together by asking, listing and agreeing. → Ask -> List -> Agree

I made up the requirements by myself and never asked the user. → The user was never asked, so the requirements may not match what they really need. Ask the user questions first.

We wrote lots of ideas on the list but never agreed on which to keep. → The group skipped agreeing on a final list. Talk it through and agree on the final requirements before building.

Section C: Definitions

co-develop requirements — Work with your teacher, the user and classmates to ask questions, list what the solution must do, and agree on a final list of requirements.

Section D: Fill in the Blanks

ASK user "What do you need?"

requirements ← []
ADD "Show the score" TO requirements

ASK class "Do we all agree?"
IF answer = "yes" THEN
  SAVE final_list

requirements ← teacher_list
ADD "Easy to read" TO requirements

ASK user "What do you need?"
ADD answer TO requirements
SHOW requirements TO class

Section E: Spot the Error

A — Co-developing requirements starts by asking the user. Guessing can get their needs wrong. It should be ASK the user what they need.

B — Requirements come from the teacher's brief and the user, not only from your own wishes. It should list what the app must do.

C — Co-developing means agreeing on a final list with the user and classmates. You can't skip that step. It should be AGREE on a final list.

D — The group agrees on a final list after sharing and talking about all the answers. It should not just take the first idea.

D — The solution is built from the agreed final list of requirements, not from your own ideas. It should be BUILD using the final list.