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

The Multiple Views of Architecture

Learn why architecture requires different perspectives: logical, physical, development, and process views.

The Multiple Views of Architecture

What you'll learn: Why a single diagram can't capture everything about a system's architecture, and how different views serve different stakeholders.

The Challenge of Communicating Architecture

Imagine trying to describe a building to different people: a resident cares about room layouts, an electrician needs wiring diagrams, a plumber wants pipe routing, and a city planner focuses on the footprint and zoning. Each needs a different view of the same structure.

Software architecture works the same way. A single perspective can't answer all questions or serve all stakeholders effectively.

The Four Classic Views

The 4+1 architectural view model recognizes that architecture must be examined from multiple angles:

Logical View

Shows the system's functional components and their relationships. What modules or services exist? How do they interact logically? This view matters to developers understanding the domain model and business logic.

Physical View (Deployment)

Describes how software maps to hardware: servers, containers, networks, load balancers. Operations teams need this to deploy and maintain the system.

Development View

Organizes the codebase: packages, modules, libraries, and dependencies. Build engineers and developers use this to understand code organization and build processes.

Process View

Captures runtime behavior: threads, processes, concurrency, and communication patterns. Performance engineers and debuggers need this to understand how the system behaves under load.

The "+1" is the scenario view (use cases) that connects these perspectives and validates architectural decisions.

Why Multiple Views Matter

Different stakeholders ask different questions. A database administrator doesn't need your class diagrams, and a front-end developer doesn't need your network topology. By separating concerns into distinct views, you communicate more effectively and make better architectural decisions.

Key Takeaway: Architecture isn't one diagram—it's a set of complementary views (logical, physical, development, process) that together tell the complete story of your system's structure and behavior.