2.1.3 Thinking Procedurally

Question 1

First stage of thinking procedurally

Answer 1

Problem Decomposition. The problem defined by the user is broken down into its component parts.

Question 2

Why use problem decomposition?

Answer 2

To make complex problems easier to solve, and more manageable, by allowing tasks to be divided between a group of people according to individual skill sets.

Question 3

Benefit of thinking procedurally

Answer 3

Makes the task of writing a program simpler, by breaking it down into small simple parts which are easier to understand and design.

Question 4

Alternative name for top down design

Answer 4

Stepwise refinement

Question 5

Purpose of top down design

Answer 5

Continually break problems down into subproblems, until each subproblem can be represented as a single task and ideally a self contained subroutine.

Question 6

Once top down design has produced several subproblems which represent individual tasks, what occurs?

Answer 6

Each task can be solved and developed as a subroutine by a different person. The subroutines can be tested separately, before being brought together and integrated.

Question 7

What sort of problems is top down design suited for?

Answer 7

Large, complex problems

Question 8

Second stage of thinking procedurally

Answer 8

Identifying components of a solution

Question 9

What must software developers consider when recombining components to form a solution?

Answer 9

The order in which subroutines are executed, as well as how subroutines interact with each other, based on their role in solving the problem.

Question 10

What should a software developer do before designing a subroutine to solve a particular problem?

Answer 10

See if it is possible for an already existing subroutine or module to be used.