Software, system, solution, and enterprise architecture
The disciplines overlap but answer different scopes. Software architecture organizes code and runtime elements. System architecture includes software, hardware, networks, people, procedures, facilities, and external environments. Solution architecture shapes one business change. Enterprise architecture aligns portfolios, capabilities, information, technology, and governance.
Core ideas and patterns
| Idea | What it solves | Cost, limit, or warning |
|---|---|---|
| Software architecture | Structures one software-intensive system | Can optimize locally while harming the wider operating system |
| System architecture | Coordinates technical and human subsystems end to end | Requires lifecycle, physical, safety, and operational thinking |
| Solution architecture | Integrates products and systems for a bounded outcome | May become a one-off if enterprise reuse is ignored |
| Enterprise architecture | Guides capabilities, portfolios, standards, and roadmaps | Becomes bureaucracy when detached from delivery evidence |
| Platform architecture | Creates paved roads and reusable internal capabilities | A platform without product ownership becomes mandatory friction |
| Systems of systems | Coordinates independently managed systems with emergent behavior | No single team controls all change or failure |
How to apply it
Name the entity of interest and its boundary. List what is inside, outside, shared, and independently owned. Identify lifecycle authorities: who funds, builds, deploys, operates, secures, supports, and retires each part. Use capability and context views for wide scope, then zoom into containers, components, data, and deployment only where a decision requires detail.
Evidence, not opinion
Trace every high-level capability to owned services, information, controls, and operational measures. A system boundary is credible only if contracts, responsibility, budget, escalation, and failure handling match it in reality.
Small example
An airport baggage capability includes kiosks, conveyors, scanners, labels, networks, operators, physical zones, airline systems, safety procedures, and recovery teams. Designing only the tracking API misses most of the system architecture.
Feynman check
Explain the design to a new engineer without using the pattern names. State the problem, the forces that conflict, the chosen boundary or mechanism, what can fail, and the evidence that would prove the choice still works.