Interpreting a given design

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. A teacher gives you an IPO chart, an annotated mock-up and a query design. What is the best way to work out what to build?

A Read all the design parts together and check they agree

B Read only the mock-up and ignore the other parts

2. A requirement says the spreadsheet must calculate each student's average mark. The IPO chart has no process for averaging. What have you found?

A Missing detail in the design

B A design that fully meets the requirement

3. Which design tool is best for showing where buttons, headings and charts will sit on screen?

A An IPO chart

B A mock-up

4. Which design tool is best for showing what data goes in, what happens to it and what comes out?

A A mock-up

B An IPO chart

5. A mock-up has a label that says 'Total' but does not say how the total is worked out. What should you do?

A Check the IPO chart or annotations for the calculation, and ask if it is missing

B Guess the calculation and build it anyway

Match the Pairs

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

Left column		Right column
1IPO chart: Input = student marks		AThe design does not match the requirement because the mock-up has no sales or month data
2Annotation: 'Show total in red if < 50'		BA note on the design that tells the developer exactly how an output must look or behave
3Matching a design to requirements: the requirement says users must filter by suburb, so the query design must include this		CShows the data the solution must receive before any processing can start
4Choosing the right design tool: to show where fields and buttons sit on a screen, use a mock-up		DCriteria: Suburb = [Enter suburb]
5IPO chart: Process = (blank), Output = Average mark		EMock-up: layout of form with labelled fields
6Requirement: show sales by month. Mock-up: table of customer names only		FMissing detail: the Process column does not say how the average is calculated, so the developer cannot build it

Definitions

Interpreting a design

Fill in the Blanks

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

Input: Hours, Rate _______: Hours * Rate Output: Weekly pay

Requirement: show passes (50 or more) Field: Score Criteria: __50

Task: show where charts sit on the page Best tool: _______

Requirement: list names A to Z Field: Surname Sort: _________

Requirement: show total sales Input: Sales column Process: ___(Sales)

Spot the Error

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

Question 1

A Input: mark1, mark2, mark3

B Process: average the marks

C Output: average mark

D Build: =SUM(B2:B4)

Question 2

A Need: Year 11 names, A to Z

B Table: Students

C Criteria: Year = 11

D Sort: Name Z to A

Question 3

A Requirement: show total cost

B Output: average price

C Input: price, quantity

D Process: price * quantity

Question 4

A Mock-up: chart below table

B Annotation: chart beside data

C Build: place chart in column F

Question 5

A Need: show layout of a screen

B Tool: IPO chart

C Reason: shows where items go

Answer Key

Interpreting a given design

Section A: Quick Questions

A — Read all the design parts together and check they agree

A — Missing detail in the design

B — A mock-up

B — An IPO chart

A — Check the IPO chart or annotations for the calculation, and ask if it is missing

Section B: Match the Pairs

IPO chart: Input = student marks → Shows the data the solution must receive before any processing can start

Annotation: 'Show total in red if < 50' → A note on the design that tells the developer exactly how an output must look or behave

Matching a design to requirements: the requirement says users must filter by suburb, so the query design must include this → Criteria: Suburb = [Enter suburb]

Choosing the right design tool: to show where fields and buttons sit on a screen, use a mock-up → Mock-up: layout of form with labelled fields

IPO chart: Process = (blank), Output = Average mark → Missing detail: the Process column does not say how the average is calculated, so the developer cannot build it

Requirement: show sales by month. Mock-up: table of customer names only → The design does not match the requirement because the mock-up has no sales or month data

Section C: Definitions

Interpreting a design — Reading a design's IPO chart, annotations, mock-ups and query designs together to work out what must be built, and checking it matches the requirements.

Section D: Fill in the Blanks

Input: Hours, Rate
Process: Hours * Rate
Output: Weekly pay

Requirement: show passes (50 or more)
Field: Score
Criteria: >=50

Task: show where charts sit on the page
Best tool: mock-up

Requirement: list names A to Z
Field: Surname
Sort: Ascending

Requirement: show total sales
Input: Sales column
Process: SUM(Sales)

Section E: Spot the Error

D — The IPO chart says the process is to average the marks. SUM only adds them, so the build must use =AVERAGE(B2:B4).

D — The requirement asks for names from A to Z. The query design must sort Name ascending (A to Z), not Z to A.

B — The requirement is to show the total cost, so the IPO output must be total cost. An average price does not match the requirement.

A — The annotation and build step put the chart beside the data. The mock-up must show the chart to the right of the table so the design is consistent.

B — A layout is shown with a mock-up. An IPO chart lists inputs, processes and outputs. It does not show where items sit on the screen.