top-down design
The technique of breaking down a problem into major tasks, then subtasks until each is simple enough to be written as a self-contained subroutine.
How can decomposition aid the design of a program?
It will creates a more manageable problem / simpler to
understand / maintain
can tackle each sub problem independently
* Smaller problems are more manageable
* Smaller problems are easier to solve
* To see where code can be reused in the solution
* To split tasks between different programmers
secondary definition of pipelining
The result from one process/procedure feeds into the next.