# Architecture Disciplines

**In short:** Architecture work happens at different scopes. A common picture compares enterprise architecture to city planning and solution architecture to a building design. Several specialist disciplines, such as network architecture, help shape one solution.

## Explanation

Architecture work does not have one single scope. A popular way to explain the scopes is a city analogy.

**Enterprise architecture** is like city planning. Its scope is the business as a whole, aligned with technical activity. It helps decide how areas relate to each other. It also helps decide how utilities such as water and electricity fit into the bigger picture. It does not decide who builds what. Utilities are the analogue of infrastructure.

**Solution architecture** is like the design of a building on a plot of land. It works inside that plot. Software architecture is likened to this kind of building design. (See *Software Architecture* and *Enterprise Architecture* for each topic in depth.)

**Several disciplines work together.** A solution draws on whatever disciplines the problem requires, so several disciplines jointly shape one solution. Specialist roles exist beside the enterprise role. A network architect, for example, applies network technology to the design of large systems.

**The boundaries are blurry.** Solution architecture and enterprise architecture are often seen as overlapping. Many IT architects do not see the boundary between them. One proposal is to let solution architecture own the "architecture within the land" and let enterprise architecture own the "architecture within the city."

## Example

A company plans a new online ordering system. At the city level, planners decide how the ordering area relates to other business areas and how shared services fit in. They do not decide who builds the system. At the plot level, the solution team designs the ordering system itself. Because the system is large, they ask a network specialist to help with the network design.

## Trade-offs

Because the boundary between solution and enterprise architecture is blurry, the two can overlap. Teams may duplicate work or leave gaps unless they agree who covers what. Drawing on several disciplines also means more people take part in shaping one solution.



## Checks

- The document states whether a piece of work belongs to solution scope or enterprise scope, and does not leave the boundary implicit.
- Specialist disciplines used for the solution, such as network design, are named.

## Related

- [Enterprise Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-management.md)
- [Software Architecture](https://arc.fuet.ch/concepts/fundamentals/software-architecture.md)
- [Relationship between Enterprise Architecture and Application Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/relationship-between-enterprise-architecture-and-application-architecture.md)
- [Application Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/application-architecture.md)
- [Architecture Level](https://arc.fuet.ch/concepts/fundamentals/architecture-levels.md)
- [Software Architect](https://arc.fuet.ch/concepts/fundamentals/software-architect-role.md)
- [Data Architecture](https://arc.fuet.ch/concepts/data-architecture/data-architecture.md)
- [Technology Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/technology-architecture.md)

## Sources

- [Enterprise Architecture and City Planning](https://www.windley.com/archives/2003/09/enterprise_arch_4.shtml) — windley.com, accessed 2026-11-09
- [Solution Architecture Vs Enterprise Architecture](https://www.leanix.net/en/blog/solution-vs-enterprise-architecture) — leanix.net, accessed 2026-11-09
- [What type of IT architect are you?](https://www.redhat.com/en/blog/what-type-it-architect-are-you) — redhat.com, accessed 2026-11-09
- [Solution Architect vs Enterprise Architect: Central Planning | Microsoft Learn](https://learn.microsoft.com/en-us/archive/blogs/kaevans/solution-architect-vs-enterprise-architect-central-planning) — learn.microsoft.com, accessed 2026-11-09