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

What Are Architectural Drivers

Understanding the forces that shape architecture: functional requirements, quality attributes, and constraints.

What Are Architectural Drivers

What you'll learn: You'll discover the three fundamental forces that determine how a software system should be architected.

The Forces That Shape Your Architecture

Architectural drivers are the key inputs that guide all your architectural decisions. Think of them like the forces that shape a river's path: the terrain it must cross (constraints), the volume of water it must carry (functional requirements), and the speed at which it must flow (quality attributes).

Every architectural choice you make should trace back to one or more drivers. Without understanding them, you're building on guesswork.

The Three Types of Architectural Drivers

1. Functional Requirements

These define what the system must do—the features and capabilities users need. Examples: "users must be able to upload photos," "the system must process payments," "search results must be filterable by date."

2. Quality Attributes

These define how well the system must perform its functions. These are the "ilities": scalability, reliability, security, performance, maintainability, availability. For instance, "the system must handle 10,000 concurrent users" or "99.9% uptime" or "page load under 200ms."

3. Constraints

These are the non-negotiable boundaries within which you must work: budget limits, technology mandates, regulatory compliance, deployment environments, team skills, legacy system integration, or deadlines.

How They Work Together

Imagine building an e-commerce platform. The functional requirement is "process orders." The quality attribute might be "must scale to 1 million orders per day during peak season." The constraint could be "must run on existing AWS infrastructure with a $50K/month budget."

These three drivers together force architectural decisions: perhaps a microservices approach for scalability, event-driven processing for peak loads, and managed services to control costs.

Key Takeaway: Every significant architectural decision should directly address one or more architectural drivers—functional requirements, quality attributes, or constraints—making your architecture purposeful rather than arbitrary.