Chapter 1: What does a Software Architect Do?Chapter 2: Software Architect TypesChapter 3: Career Planning: A Strategy for Achieving Professional GoalsChapter 4: Qualification Self-Assessment for Software ArchitectsChapter 5: Skill Acquisition for Application Level (Level-I) Software ArchitectsChapter 6: Skill Acquisition for Application Level (Level-II) Software ArchitectsChapter 7: Skill Acquisition for Application Level (Level-III) Software ArchitectsChapter 8: Business Skills: Prescription for Software Architecture SuccessChapter 9: Support Environment ElasticityChapter 10: Foster the "Buy over Build" Software Architecture StrategyChapter 11: Promote Vendor-Agnostic SolutionsChapter 12: Reduce Hub and Spokes Architecture PatternsChapter 13: Implement Federated ArchitectureChapter 14: Avoid Building Monolithic Software SystemsChapter 15: Focus on Incremental Software Architecture SolutionsChapter 16: Avoid the Source Code "Copy and Paste" Approach (lift and shift)Chapter 17: Don't Fix a Broken Software System by Throwing more Hardware at itChapter 18: Build Testable Software SystemsChapter 19: Reduce the Amount of Software Proxies and IntermediariesChapter 20: Minimize Thick Architecture Layers
MICHAEL BELL is an enterprise and solution architect with hands-on experience in business and software architecture modeling. He has consulted for organizations including J.P. Morgan Chase, Citibank, Bank One, UBS-Paine Webber, American Express, AIG, and the US government. He is the best-selling author of software architecture books, and he offers a variety of enterprise integration solutions for back-end and customer-facing systems.
