Summary

Summary · Chapter 2

Chapter recap

• Be aware of the various architect roles — they share responsibilities but differ in focus.
• Learn whatever development methodology your org has selected; if you get to choose, know the options well enough to pick one suited to the project.
• Architects support project management with task estimates, planning, and monitoring/controlling the project through its life cycle.
• Because they communicate with more stakeholders and management, architects deal with office politics more than other roles.
• Orgs want architect involvement in risk management — identifying risks and choosing how to handle them.
• Architects work with the SCM team on builds, environments, and change management.
• Consider introducing software product lines for reuse — products built faster and with higher quality.

What’s next

Chapter 3 examines software requirements and their effect on architecture: understanding the business domain, requirements engineering, eliciting/summarizing requirements from stakeholders, and quality attributes.

Citations

• Software Architect’s Handbook (Packt, 2018), Ch.2 “Summary”, p. 136.