Matching a task to its PDLC stage

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. A developer draws a flowchart showing how the program will work. Which stage is this?

A Design

B Coding

2. A developer lists what the program must do, including its inputs, processes and outputs. Which stage is this?

A Analysis

B Design

3. A developer writes the program in a programming language and fixes errors as they go. Which stage is this?

A Testing

B Coding

4. A developer runs the finished program with normal, abnormal and extreme test data. Which stage is this?

A Testing

B Coding

5. Which task belongs to the analysis stage?

A Drawing a flowchart of the algorithm

B Writing down the requirements of the program

Match the Pairs

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

Left column		Right column
1Listing what the program must do		AFlowcharts are drawn in the design stage, not analysis. Analysis is for listing requirements.
2Running the program with test data		BTesting stage: the task of checking the program works using normal, abnormal, extreme and boundary data
3Design stage: planning how the program will work, for example by drawing a flowchart		CAnalysis stage: the task of finding and listing the requirements of the program
4Coding stage: writing the program and fixing errors as you go with iterative testing		DRunning the program with test data is the testing stage. Coding is for writing the program.
5Drawing a flowchart is part of the analysis stage		EWrite the program and fix errors as you go
6Running test data is part of the coding stage		FDraw a flowchart of the algorithm

Definitions

analysis, design, coding, testing

Fill in the Blanks

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

Finding out what users need is ________

Writing and fixing code is the ______ stage

Running test data is the _______ stage

Drawing a flowchart is the ______ stage

Listing requirements is ________ because we must understand the problem first

Spot the Error

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

Question 1

A List requirements -> Analysis

B Draw flowchart -> Design

C Write the code -> Testing

D Run test data -> Testing

Question 2

A Find the outputs -> Analysis

B Draw hierarchy chart -> Design

C Fix bugs as you go -> Coding

D Use boundary data -> Coding

Question 3

A Write pseudocode -> Coding

B Code the program -> Coding

C Run test data -> Testing

Question 4

A Task: list requirements

B Stage: Analysis

C Because it plans the layout

Question 5

A Task: run test data

B Stage: Coding

C Because it checks it works

Answer Key

Matching a task to its PDLC stage

Section A: Quick Questions

A — Design

A — Analysis

B — Coding

A — Testing

B — Writing down the requirements of the program

Section B: Match the Pairs

Listing what the program must do → Analysis stage: the task of finding and listing the requirements of the program

Running the program with test data → Testing stage: the task of checking the program works using normal, abnormal, extreme and boundary data

Design stage: planning how the program will work, for example by drawing a flowchart → Draw a flowchart of the algorithm

Coding stage: writing the program and fixing errors as you go with iterative testing → Write the program and fix errors as you go

Drawing a flowchart is part of the analysis stage → Flowcharts are drawn in the design stage, not analysis. Analysis is for listing requirements.

Running test data is part of the coding stage → Running the program with test data is the testing stage. Coding is for writing the program.

Section C: Definitions

analysis, design, coding, testing — The four PDLC stages in order; each task belongs to one: analysis lists requirements, design draws flowcharts, coding writes code, testing runs test data.

Section D: Fill in the Blanks

Finding out what users need is analysis

Writing and fixing code is the coding stage

Running test data is the testing stage

Drawing a flowchart is the design stage

Listing requirements is analysis
because we must understand the problem first

Section E: Spot the Error

C — Writing the code is the coding stage. Testing is when the finished program is run with test data. It should be: Write the code -> Coding.

D — Boundary data is a type of test data, and running the program with test data is the testing stage. It should be: Use boundary data -> Testing.

A — Pseudocode is a design method. It plans the algorithm before any real code is written. It should be: Write pseudocode -> Design.

C — The reason does not match the task. Listing requirements is analysis because it says what the program needs to do. Planning the layout belongs to design.

B — Running a program with test data to check it works is the testing stage, not coding. It should be: Stage: Testing.