Final answer:
The statement is false; bottom-up programming starts with developing small components and integrating them into complex systems, as opposed to dividing tasks into modules before starting.
Step-by-step explanation:
The statement is false. Bottom-up programming does not start with subdividing tasks into modules and sub-modules. Instead, it begins with the development of small, individual components or functions which are then integrated to create more complex systems. This process focuses on creating and testing the lowest-level components first, before moving upward to higher levels of the program's architecture. A typical bottom-up approach would not involve decomposing the entire problem beforehand; this is more characteristic of top-down programming.
Decompose the Problem into Subproblems
Although decomposing the problem into subproblems is a common technique, it's often associated with top-down approaches in programming. This involves breaking down a complex problem into smaller, more manageable subproblems and then solving each subproblem one at a time, giving clear structure to the development process. However, in bottom-up programming, such a decomposition might only occur initially to understand the overall scope, with the emphasis being on building each small part of the system individually and then integrating these parts together.