Bottom-Up Design

Definition

Bottom-Up Design is a design approach that starts by designing and building the most basic, low-level modules/components first, then progressively combines/composes them into larger, higher-level modules, until the complete system is assembled.

How It Works

      [A1]    [A2]            [C1]    [C2]
           \   /                  \   /
         [Module A] [Module B] [Module C]
                \      │       /
                [Entire System]

• Start with basic building blocks (utility functions, reusable components)
• Combine them into intermediate modules
• Keep combining upward until the full system emerges

Characteristics

• Design proceeds from concrete to abstract
• Naturally leverages existing reusable components/libraries
• Common in systems built around available frameworks/components

Advantages

• Makes excellent use of existing reusable modules/components
• Basic modules can be tested early and thoroughly in isolation
• Good for systems where low-level utilities/components are well understood or already exist
• Encourages building a strong reusable component library

Disadvantages

• Risk of losing sight of the overall system goals — may build components that don't fit together well
• Harder to ensure the assembled system truly meets top-level requirements
• Integration issues may surface late if lower modules weren't designed with the big picture in mind

When to Use

• When reusable components/libraries already exist and should be leveraged
• Bottom-up is often combined with top-down in real projects (hybrid approach) — top-down for overall architecture, bottom-up for reusing existing components

Top-Down vs. Bottom-Up (Comparison)

Top-Down	Bottom-Up
Starts from the whole system	Starts from basic components
Decomposes into details	Composes into higher-level modules
Good for new systems	Good for leveraging existing components
Risk: hard to anticipate right decomposition	Risk: losing sight of overall goals

---

Exam tip: Many real projects use a hybrid approach — mention this as a nuanced point if asked to "discuss" rather than just "compare" Top-Down vs Bottom-Up.