Course contentsShow
← Software Engineering
Lesson 1230 of 1,93337. Software Architecture FundamentalsFree lesson

Functional Requirements as Drivers

When and how core functionality demands specific architectural approaches and structural choices.

Functional Requirements as Drivers

What you'll learn: How a system's core functionality directly shapes its architectural structure and technical approach.

The Core Idea

Not all functional requirements are created equal. Some requirements—like "must handle 10,000 concurrent video streams" or "must process financial transactions with strict ordering"—demand specific architectural choices. These aren't suggestions; they're constraints that eliminate certain architectural options entirely and make others mandatory.

Think of it like building a bridge. "Must cross a river" is a functional requirement, but if that requirement becomes "must allow cargo ships to pass underneath," you've just eliminated low-bridge designs and possibly forced a drawbridge or suspension architecture. The core function drives the structure.

When Functionality Forces Your Hand

Certain functional requirements create unavoidable architectural pressures:

  • Real-time processing (trading systems, gaming) may require event-driven architectures with minimal latency paths
  • Complex calculations (scientific computing, rendering) might demand batch processing or specialized compute architectures
  • Multi-tenant isolation (SaaS platforms) forces database partitioning and namespace separation decisions
  • Offline capability (mobile apps) requires data synchronization architectures and conflict resolution strategies

These aren't performance concerns or stakeholder preferences—they're baked into what the system must do.

The Architectural Impact

When a functional requirement becomes a driver, it ripples through your entire system. Needing to "support pluggable payment providers" might force you toward a hexagonal architecture with well-defined ports. Requiring "full audit trails" might mandate event sourcing patterns.

The key skill is recognizing which functional requirements are architectural drivers versus which are just features that fit within any reasonable structure.

Key Takeaway: Core functional requirements often dictate architectural approaches directly—some things you must build simply cannot be built certain ways, making functionality a primary driver of structural decisions.