# Software Architect

**In short:** A software architect links business goals and technical work. They decide what matters, weigh trade-offs, talk with people at every level of the organization, and stay close to the building of the system.

## Explanation

A software architect is responsible for meeting requirements and for creating the architecture design of a solution. See *Software Architecture* for what the architecture itself is.

**Bridging two worlds.** One view says the architect's main job is to ride the "elevator" between the penthouse (management) and the engine room (the technical people). Architects must engage with the upper floors of the organization, not only technical levels. That links business and technology. They also need organizational context, and getting it means visiting many levels.

**Making trade-offs visible.** An architect's job includes making the ramifications of choices transparent. It also includes involving all levels of the organization in the trade-off. A trade-off means gaining one benefit by giving up another. See *Quality Attribute Trade-off*.

**Knowing what is important.** Architecture is about the important stuff, and the architect must recognize what is important. A developer who wants to become an architect needs this same ability.

**Experience.** One recommendation is to spend several years programming and working actively in software development. That builds an instinct for design risks and uncertainties.

**Communication.** Architects deal with many stakeholder groups, meaning people with an interest in the system. The better an architect adapts to their languages and goals, the better the decisions will be. Architects communicate and document the architecture using views and patterns. See *Architecture View* and *Architectural Pattern*.

**Staying involved in building.** Architects get feedback by being directly involved in, and accountable for, delivery. They also accompany implementation and check that source code and architecture stay consistent.

## Example

A company wants a new customer portal. The manager talks about faster sign-up and lower support cost. The developers talk about databases and deadlines. The architect talks with both. They explain to the manager what each option costs in time and flexibility. They explain to the developers which goals matter most. Later, the architect joins the team during delivery and checks that the code still follows the agreed design.

## Trade-offs

Staying involved in delivery gives the architect feedback, but it also makes them accountable for the outcome. Talking with all levels of the organization takes effort, because the architect must visit many levels to find the right context. Making trade-offs transparent can also bring uncomfortable ramifications into the open.



## Checks

- The document names who acts as architect and who is responsible for meeting requirements and the architecture design.
- The architecture is communicated to stakeholders through views and patterns.
- The consequences of key trade-offs are made visible to stakeholders at several organizational levels.
- The architect takes part in implementation and checks that code and architecture are consistent.

## Related

- [Role of the Software Architect](https://arc.fuet.ch/concepts/fundamentals/architect-knowledge-and-tasks.md)
- [Software Architecture](https://arc.fuet.ch/concepts/fundamentals/software-architecture.md)
- [Stakeholder](https://arc.fuet.ch/concepts/vision-stakeholders/stakeholder.md)
- [Quality Attribute Trade-off](https://arc.fuet.ch/concepts/quality-attributes/architectural-trade-off-thinking.md)
- [Architecture View](https://arc.fuet.ch/concepts/documentation/architecture-view.md)
- [Architectural Thinking](https://arc.fuet.ch/concepts/fundamentals/architectural-thinking.md)
- [Common Architect Mistakes](https://arc.fuet.ch/concepts/fundamentals/common-architect-mistakes.md)
- [Architectural Decision](https://arc.fuet.ch/concepts/forces-decisions/architectural-decision.md)

## Sources

- [The Architect Elevator — Visiting the upper floors](https://martinfowler.com/articles/architect-elevator.html) — martinfowler.com, accessed 2026-11-09
- [Software Architecture Guide](https://martinfowler.com/architecture/) — martinfowler.com, accessed 2026-11-09
- [Curriculum forCertified Professional forSoftware Architecture (CPSA)®: Foundation Level](https://public.isaqb.org/curriculum-foundation/curriculum-foundation-en.html) — public.isaqb.org, accessed 2026-11-09
- [The Profession of “Software Architecture” - iSAQB® - Official Website](https://www.isaqb.org/blog/the-profession-of-software-architecture/) — isaqb.org, accessed 2026-11-09