Program development life cycle

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which list shows the four stages of the program development life cycle in the correct order?

A Analysis, design, coding, testing

B Analysis, coding, design, testing

2. Which stage comes FIRST in the program development life cycle?

A Analysis

B Coding

3. What does the design stage produce?

A The finished working program

B Structure diagrams, flowcharts or pseudocode

4. Which stage is where the program is written in a programming language?

A Coding

B Design

5. What does the analysis stage produce?

A A set of test results

B A clear list of the problem and its requirements

Match the Pairs

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

Left column		Right column
1analysis		AStage 1: find out what the problem is and what the program must do (the requirements).
2design		Banalysis -> design -> coding -> testing
3Coding is the third stage: the design is turned into a program, and each part is tested as it is written.		CThe stages are in the wrong order. Coding is placed first, but the problem must be analysed and the solution designed before any code is written.
4The four stages of the program development life cycle in the correct order.		Dcoding
5coding -> analysis -> design -> testing		EStage 2: plan the solution using structure diagrams, flowcharts and pseudocode before writing any code.
6design: find out what the user needs and write the requirements		FThis describes analysis, not design. Design is where the solution is planned with structure diagrams, flowcharts or pseudocode.

Definitions

analysis, design, coding, testing

Fill in the Blanks

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

CALL Analysis() CALL ______() CALL Coding()

CALL Design() CALL Coding() CALL _______()

CALL ________() CALL Design() CALL Coding()

CALL Coding(part1) CALL _______(part1) CALL Coding(part2)

stage ← 1 // Analysis stage ← 2 // Design stage ← _ // Coding

Spot the Error

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

Question 1

A Stage 1: Analysis

B Stage 2: Coding

C Stage 3: Coding

D Stage 4: Testing

Question 2

A Analysis: requirements list

B Design: flowchart

C Coding: structure diagram

D Testing: test results

Question 3

A Analysis: write the program

B Design: plan the solution

C Coding: write the program

D Testing: check it works

Question 4

A FOR module ← 1 TO 5

B CALL TestModule(module)

C CALL TestModule(module)

D NEXT module

Question 5

A stages[1] ← "Analysis"

B stages[2] ← "Design"

C stages[3] = "Coding"

D stages[4] ← "Testing"

Answer Key

Program development life cycle

Section A: Quick Questions

A — Analysis, design, coding, testing

A — Analysis

B — Structure diagrams, flowcharts or pseudocode

A — Coding

B — A clear list of the problem and its requirements

Section B: Match the Pairs

analysis → Stage 1: find out what the problem is and what the program must do (the requirements).

design → Stage 2: plan the solution using structure diagrams, flowcharts and pseudocode before writing any code.

Coding is the third stage: the design is turned into a program, and each part is tested as it is written. → coding

The four stages of the program development life cycle in the correct order. → analysis -> design -> coding -> testing

coding -> analysis -> design -> testing → The stages are in the wrong order. Coding is placed first, but the problem must be analysed and the solution designed before any code is written.

design: find out what the user needs and write the requirements → This describes analysis, not design. Design is where the solution is planned with structure diagrams, flowcharts or pseudocode.

Section C: Definitions

analysis, design, coding, testing — The four ordered stages of building a program: analysis (what is needed), design (plan it), coding (write it) and testing (check it works).

Section D: Fill in the Blanks

CALL Analysis()
CALL Design()
CALL Coding()

CALL Design()
CALL Coding()
CALL Testing()

CALL Analysis()
CALL Design()
CALL Coding()

CALL Coding(part1)
CALL Testing(part1)
CALL Coding(part2)

stage ← 1 // Analysis
stage ← 2 // Design
stage ← 3 // Coding

Section E: Spot the Error

B — Design is stage 2 and coding is stage 3. Line 2 should read 'Stage 2: Design'. The order is analysis, design, coding, testing.

C — Coding produces the program code. A structure diagram is a design-stage output, so line 3 should be 'Coding: program code'.

A — Analysis is about finding out what the problem is and what is needed. Writing the program is coding, so line 1 should be 'Analysis: find the problem'.

B — Each module must be coded before it can be tested, so line 2 should be CALL CodeModule(module). Testing happens repeatedly as the code is written.

C — Cambridge pseudocode assigns a value with the ← arrow, not =. Line 3 should be stages[3] ← "Coding".