liveBook · Manning

Software architect

A software architect is a technical professional who guides high-level decisions about a software system’s structure, boundaries, and technical direction.

How 3 Manning books explain it

Grokking Software Architecture

A person responsible for guiding the structural and system-wide design of software.

How it is used
Guides everyday structural choices and helps teams make deliberate, defensible system-design decisions.
How deep it goes
Defines the role and explains tradeoffs and success metrics, while stopping short of detailing a full decision-recording process.
Examples
Uses logic placement, class structure, and database queries alongside incident and feature-delivery metrics.
What you can do after
Evaluate tradeoffs, choose acceptable downsides, and defend decisions with measurable results.

Read how Grokking Software Architecture explains software architect →

Collaborative Software Design: How to facilitate domain modeling decisions

A software architect is a person responsible for making and communicating significant structural decisions about a software system.

How it is used
Enables teams and stakeholders to make architectural decisions collaboratively without becoming a development bottleneck.
How deep it goes
Develops facilitation, collaborative modeling, and social dynamics, but does not detail specific architectural structures or implementation techniques.
Examples
Uses BigScreen’s stalled architectural disagreement and the contrast between Waterfall design and collaborative Agile architecture.
What you can do after
Apply it via collaborative modeling to facilitate supported architectural decisions with teams and stakeholders.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains software architect →

Lead Developer Career Guide

A professional who designs the high-level structure, technical direction, and integration of software systems.

How it is used
Plans technical architecture and how to build it, illustrating connections among system components.
How deep it goes
Details architecture diagrams and build planning, while distinguishing the architect’s expertise from a lead developer’s broader technical expertise.
Examples
Uses diagrams of component connections and a skills comparison between lead architects and lead developers.
What you can do after
Understand how architecture planning differs from implementation and coding responsibilities.

Read how Lead Developer Career Guide explains software architect →

Also covered in

What to know first

Related concepts

Questions about software architect

What is software architect?

A software architect is a technical professional who guides high-level decisions about a software system’s structure, boundaries, and technical direction.

Which Manning books explain software architect?

Grokking Software Architecture, Collaborative Software Design: How to facilitate domain modeling decisions and Lead Developer Career Guide.

What should I know before learning software architect?

Manning books that teach software architect usually introduce stakeholder first.

What is the difference between software architect and technical lead?

A software architect is a technical professional who guides high-level decisions about a software system’s structure, boundaries, and technical direction. A technical lead is a software engineer who provides technical ownership, direction, coordination, and guidance for a team or project.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.