
Software Architecture and Decision-Making: Leveraging Leadership, Technology, and Product Management to Build Great Products, 1st edition
Published by Addison-Wesley Professional (21 November 2023) © 2024
- Srinath Perera
This product is expected to ship within 3-6 business days for US and 5-10 business days for Canadian customers.
Title overview
Leverage leadership knowledge to make better software architecture decisions. Think deeply but implement slowly.
Theoverarching goal of software systems (hence, for software architecture)is to build systems that meet quality standards and that provide thehighest return on investment (ROI) in the long run or within a definedperiod of time.
A great product requires a combinationof technology, leadership, and product management (including UX).Leadership is primarily about managing uncertainty and making the rightjudgment. To build great products, technical leaders need to combinetechnology, leadership, and product management knowledge, and make theright decisions. Many technical mistakes come from the gap betweenknowledge about these three items and judgment.
In Software Architecture and Decision-Making,Srinath Perera explains principles and concepts that softwarearchitects must understand deeply and how to employ those principles tomanage uncertainty. The questions and principles discussed in this bookhelp manage uncertainty while building software architecture and providea framework for making decisions. This book is for all technicalleaders in the software industry who make holistic judgments about thesystems they build and for future leaders learning the craft.
- Understandthe importance of strong decision making with examples from greattechnical leaders such as the Wright brothers and Kelly Johnson
- Leveragefive key questions and seven important principles to understanduncertainties during the design process and make strategic architecturaldecisions
- Approach the design systematically, first at the macro level and then the individual service level
Thisdefinitive guide explains principles and concepts--technical andnon-technical alike--that software architects, senior softwareengineers, and technical leads must understand to manage the inevitableuncertainty involved in building software systems and to drive successof the products for which they are responsible.