The role of a technical lead or software architect is to design software that realizes the vision of the stakeholders. However, as the design evolves, conflicting requirements emerge that impact the candidate architecture. Resolving these conflicts often involves architectural trade-offs, such as granularity versus maintainability. In addition, with time-to-market pressures and having to do more with less, adopting a bloated architectural framework like TOGAF or using a time-consuming process like ATAM is not an option. Thus, it is essential to have a deep understanding of architectural trade-offs and know when to use lightweight resolution techniques. Jeremy Deane explores a number of architectural trade-offs and offers strategies for dealing with them.
Jeremy Deane is chief architect at Foundation Medicine. Jeremy has over 22 years of software engineering experience in leadership positions. His expertise includes enterprise application integration, web application architecture, and software process improvement. He is also an accomplished conference speaker and technical author.
Comments on this page are now closed.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org