click below
click below
Normal Size Small Size show me how
2.1.3
| Question | Answer |
|---|---|
| Thinking procedurally steps | 1. Decomposition 2. To identify solutions, look at each component and figure out what is needed to solve it (data, on-screen elements, additional sub-tasks) 3. Work out the order the sub-procedures will be run in |
| decomposition | the process of breaking down a problem into smaller and smaller parts until each aspect of the problem can be dealt with effectively |
| Top-down modular design | uses stepwise refinement lowest sub-tasks can be given to individual programmers, or small teams to be written and tested in isolation before integrated to the main code as sub-procedures |
| Stepwise refinement | Each branch is repeatedly subdivided until the task is broken down into the lowest level |
| Subprogram order (working it out) | Many programs are event-driven and only take action in response to an event. The order of these events can be unpredictable. Some programs involve a predictable series of steps completed in order |