The analysis stage: problem and requirements

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which stage of the program development life cycle comes first?

A Design

B Analysis

2. What is the main aim of the analysis stage?

A Identify the problem and list the requirements

B Write the final program code

3. A school wants a program to record canteen orders. Which item is a requirement listed during analysis?

A The program must let staff enter an order and show the total cost

B Draw a flowchart with a decision symbol for each order

4. True or false: you should draw flowcharts and structure diagrams before the analysis stage.

A False

B True

5. Which technique helps in analysis by breaking a large problem into smaller sub-problems?

A Compilation

B Decomposition

Match the Pairs

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

Left column		Right column
1analysis		AThe first stage of the program development life cycle, where you identify the problem and list the requirements
2requirements list		BDesign is placed before analysis. Analysis must come first, so you understand the problem and requirements before designing anything.
3Analysis uses decomposition to break the problem into smaller sub-problems so each can be understood		CKeep: item, price, quantity. Ignore: colour of the till, canteen wall paint
4Analysis uses abstraction to keep only the important details and ignore the unnecessary ones		DFlowcharts and pseudocode are design work. Analysis only identifies the problem and lists the requirements.
5Stage order: Design -> Analysis -> Coding -> Testing		EA list of what the finished solution must do, written during analysis
6Analysis: draw a flowchart and write the pseudocode		FProblem: school canteen system -> sub-problems: take order, take payment, update stock

Definitions

analysis

Fill in the Blanks

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

Stage 1: ________ Stage 2: Design Stage 3: Coding

// Requirement: show the total Total ← 5 + 3 ______ Total

Order: Analysis, ______, Coding, Testing

Analysis uses ___________ and decomposition

// Requirement: read a mark _____ Mark OUTPUT Mark

Spot the Error

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

Question 1

A PROBLEM: Shop queues are long

B REQUIRE: Record each sale

C REQUIRE: Draw a flowchart

Question 2

A Analysis stage steps:

B 1 Identify the problem

C 2 Write the pseudocode

D 3 Then start the design

Question 3

A Problem: Bus timetable app

B KEEP: stop name

C KEEP: departure time

D KEEP: bus paint colour

Question 4

A Problem: Run a school quiz

B Sub-problem: ask questions

C Sub-problem: mark answers

D Sub-problem: write the code

Question 5

A PDLC order:

B Design then Analysis

C Then Coding then Testing

Answer Key

The analysis stage: problem and requirements

Section A: Quick Questions

B — Analysis

A — Identify the problem and list the requirements

A — The program must let staff enter an order and show the total cost

A — False

B — Decomposition

Section B: Match the Pairs

analysis → The first stage of the program development life cycle, where you identify the problem and list the requirements

requirements list → A list of what the finished solution must do, written during analysis

Analysis uses decomposition to break the problem into smaller sub-problems so each can be understood → Problem: school canteen system -> sub-problems: take order, take payment, update stock

Analysis uses abstraction to keep only the important details and ignore the unnecessary ones → Keep: item, price, quantity. Ignore: colour of the till, canteen wall paint

Stage order: Design -> Analysis -> Coding -> Testing → Design is placed before analysis. Analysis must come first, so you understand the problem and requirements before designing anything.

Analysis: draw a flowchart and write the pseudocode → Flowcharts and pseudocode are design work. Analysis only identifies the problem and lists the requirements.

Section C: Definitions

analysis — The first stage of the program development life cycle: identify the problem and list what the solution must do, using abstraction and decomposition, before any design starts.

Section D: Fill in the Blanks

Stage 1: Analysis
Stage 2: Design
Stage 3: Coding

// Requirement: show the total
Total ← 5 + 3
OUTPUT Total

Order: Analysis, Design, Coding, Testing

Analysis uses abstraction and decomposition

// Requirement: read a mark
INPUT Mark
OUTPUT Mark

Section E: Spot the Error

C — A requirement says what the solution must do. Drawing a flowchart is a design task, not a requirement. It should be something like 'REQUIRE: Show the total price'.

C — Analysis comes before design, so writing pseudocode is too early. The second analysis step is to list the requirements.

D — Abstraction removes details that are not needed. The paint colour does not help a timetable, so it should be ignored, not kept.

D — Decomposition in analysis splits the problem into smaller parts of the task, such as showing the score. Writing the code is a later stage, not a sub-problem of the quiz.

B — Analysis is the first stage and must come before design. The line should read 'Analysis then Design'.