Software architect
A software architect is a technical professional who guides high-level decisions about a software system’s structure, boundaries, and technical direction.
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.
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 →
Related concepts
- technical leadcontrasts with · A technical lead is a software engineer who provides technical ownership, direction, coordination, and guidance for a team or project.
- feedbackuses · Feedback is information about an action, system, or outcome that can inform evaluation, decisions, or subsequent behavior.
- tradeoffuses · A tradeoff is a situation in which improving one objective or property requires accepting a cost, limitation, or reduction in another.
- collaborative discovery and modelinguses · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
- designconfigures · Design is the process of planning and specifying an artifact’s structure, behavior, or presentation, and the resulting arrangement, to meet intended purposes and constraints.
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.