Details

<p>Introduction xxiii</p> <p><b>Part 1 Software Architect Capability Model 1</b></p> <p><b>Chapter 1 Software Architect Capability Model 3</b></p> <p>Software Architect Capability Model: Benefits 4</p> <p>How Should Organizations Utilize the Software Architect Capability Model? 4</p> <p>Why Create a Personal Software Architect Capability Model? 5</p> <p>Rudimentary Guiding Principles 6</p> <p>Software Architect Capability Model Creation Process 6</p> <p>Requirements Drive Architecture Solutions 7</p> <p>Requirements Issued by Problem and Solution Domain Entities 7</p> <p>How Do the Problem and Solution Domains Collaborate? 7</p> <p>Important Facts to Remember 9</p> <p>Create a Software Architect Capability Model in Five Steps 9</p> <p>Step 1: Provide Requirements and Specifications 10</p> <p>Business Requirements 10</p> <p>Technical Specifications 11</p> <p>Ensure Clear Requirements 11</p> <p>Step 2: Identify Software Architecture Practices 12</p> <p>Establish Architecture Practices 12</p> <p>Step 3: Establish Software Architecture Disciplines 13</p> <p>Apply Architecture Disciplines to Architecture Practices 14</p> <p>Applying Disciplines to the Application Architecture Practice 14</p> <p>Applying Disciplines for the Data Architecture Practice 16</p> <p>Step 4: Add Software Architecture Deliverables 17</p> <p>About Software Architecture Deliverables 17</p> <p>Add the Deliverables Section 18</p> <p>Step 5: Quantify Skill Competencies 21</p> <p>Quantifying Architecture Skills 22</p> <p>Measuring the Application Architect Skill Levels 22</p> <p>Measuring Data Architect Skill Levels 24</p> <p>Skill Competency Patterns for Architects 25</p> <p>How Can Organizations Utilize the Skill Competency Pattern? 26</p> <p>How an Individual Can Utilize the Skill Competency Pattern 27</p> <p>Interview Questions 28</p> <p><b>Part 2 Software Architecture Career Planning 29</b></p> <p><b>Chapter 2 Types of Software Architects 31</b></p> <p>Business Needs for Technological Solutions 32</p> <p>Business Needs for Software Architecture: Strategic Collaboration 32</p> <p>How Does Software Architecture Respond to Business Needs? 33</p> <p>Business Needs for Software Architecture: Technological Mediation 33</p> <p>How Could Technological Mediation Efforts Be Utilized? 34</p> <p>Business Needs for Software Architecture: Technological Implementation 34</p> <p>How Does the Implementation of Software Products Meet Business Needs? 34</p> <p>Organizational Leading Software Architect Levels 35</p> <p>Ranking Leading Software Architects 35</p> <p>Collaboration Hierarchy of Leading Software Architects 36</p> <p>Level I: Enterprise Architect Responsibilities 38</p> <p>Enterprise Architect Summary of Responsibilities 38</p> <p>Enterprise Architect Responsibility Table 39</p> <p>Level II: Solution Architect Responsibilities 40</p> <p>Solution Architect Summary of Responsibilities 41</p> <p>Solution Architect Responsibility Table 42</p> <p>Level III: Application Architect Responsibilities 44</p> <p>Application Architect Summary of Responsibilities 44</p> <p>Application Architect Responsibilities Table 46</p> <p>Comparing Responsibilities of Leading Software Architects 48</p> <p>Types of Domain Software Architects 49</p> <p>Data Architect 49</p> <p>Data Architect Summary of Responsibilities 50</p> <p>Data Architect Responsibilities Table 51</p> <p>Cloud Architect 51</p> <p>Cloud Architect Summary of Responsibilities 54</p> <p>Cloud Architect Responsibilities Table 55</p> <p>Security Architect 57</p> <p>Security Architect Summary of Responsibilities 58</p> <p>Security Architect Responsibilities Table 60</p> <p>Business Architect 62</p> <p>Business Architect Summary of Responsibilities 62</p> <p>Business Architect Responsibilities Table 63</p> <p>Collaboration Between Leading Software Architects and Domain Software Architects 65</p> <p>Use Case I: Collaboration Between an Application Architect and a Data Architect 66</p> <p>Application Architect and Data Architect Collaboration Table 66</p> <p>Use Case II: Solution Architect and Security Architect 68</p> <p>Solution Architect and Security Architect Collaboration Table 68</p> <p>Use Case III: Business Architect and Enterprise Architect Collaboration 70</p> <p>Business Architect and Enterprise Architect Collaboration Table 70</p> <p><b>Chapter 3 Career Planning for Software Architects: A Winning Strategy 73</b></p> <p>Software Architecture Career Planning Process 74</p> <p>Career Planning Step 1: Conduct Self- Discovery 75</p> <p>Discovery of Technological and Social Talents 75</p> <p>Career Planning Self- Discovery Subjects 76</p> <p>Career Planning Step 2: Pursue Research 76</p> <p>Formal Education, Training, and Certification 77</p> <p>Employment Opportunities and Interviews 77</p> <p>Subjects of Research 77</p> <p>Career Planning Step 3: Devise an Approach 78</p> <p>Setting Software Architecture Career Goals 78</p> <p>Setting Software Architecture Career Milestones 80</p> <p>Decision- Making 81</p> <p>Action Planning 82</p> <p>Career Planning Step 4: Plan Career Execution 85</p> <p>Use Case I: A Software Architecture Career Execution Plan with Alternative Tasks 85</p> <p>Use Case II: Optimized Software Architecture Execution Plan 88</p> <p>Self- Discovery Process: The Six Ws 89</p> <p>The “Why” 90</p> <p>The “Who” 91</p> <p>The “What” 92</p> <p>Self- Discovery Questions for Software Architecture Candidates 93</p> <p>Self- Discovery Queries for Software Architects 93</p> <p>The “Where” 94</p> <p>The “When” 95</p> <p>The “How” 96</p> <p>“How” Self- Queries for Software Architecture Applicants 97</p> <p>“How” Self- Questions for Practicing Software Architects 97</p> <p>Carving a Software Architecture Career Path 98</p> <p>The 4D Software Architecture Career Perspectives 99</p> <p>Social- Driven Career Perspective 100</p> <p>Social- Driven Career Chart 100</p> <p>Carve Out a Social- Driven Career Chart 101</p> <p>Social- Driven Career Path 102</p> <p>Create a Social- Driven Career Path 102</p> <p>Technology- Driven Career Perspective 103</p> <p>Technology- Driven Career Chart 104</p> <p>Create a Technology- Driven Career Chart 105</p> <p>Technical- Driven Career Path 106</p> <p>Develop a Technical- Driven Career Path 106</p> <p>Leadership- Driven Career Perspective 107</p> <p>Leadership- Driven Career Chart 108</p> <p>Create a Leadership- Driven Career Chart 109</p> <p>Leadership- Driven Career Path 110</p> <p>Develop a Leadership- Driven Career Path 110</p> <p>Strategy- Driven Career Perspective 112</p> <p>Strategy- Driven Career Chart 112</p> <p>Create a Strategy- Driven Career Chart 114</p> <p>Strategy- Driven Career Path 114</p> <p>Develop a Strategy- Driven Career Path 115</p> <p><b>Chapter 4 Self- Assessment for Software Architects 117</b></p> <p>Social Intelligence 118</p> <p>Teamwork 118</p> <p>Partnership 119</p> <p>Self- consciousness 119</p> <p>Communication 120</p> <p>Networking 120</p> <p>Soft Skills 120</p> <p>Trust Building 121</p> <p>Learning from Others 121</p> <p>Negotiation 122</p> <p>Self- presentation 122</p> <p>Teleworking 123</p> <p>Fellowship 123</p> <p>Self- sufficiency 124</p> <p>Handling Customer Relationships 124</p> <p>Social Intelligence Skill Assessment 124</p> <p>Software Architecture Practice 126</p> <p>Software Architecture Strategy 126</p> <p>Software Architecture Vision 127</p> <p>Software Architecture Role 127</p> <p>System Integration 128</p> <p>Interoperability 128</p> <p>Software Reuse 129</p> <p>Distributed Architecture Model 129</p> <p>Federated Architecture Model 129</p> <p>Architecture Styles 130</p> <p>Architecture and Design Patterns 130</p> <p>Componentization 130</p> <p>Software Architecture Frameworks 131</p> <p>Software Development 131</p> <p>Software Architecture Practice Skill Assessment 132</p> <p>Leadership 133</p> <p>Managing Time 134</p> <p>Decision- Making 134</p> <p>Problem-solving 134</p> <p>Diversity, Equity, and Inclusion 135</p> <p>Responsibility and Accountability 135</p> <p>Hiring Preferences 136</p> <p>Creative Thinking 136</p> <p>Critical Thinking 136</p> <p>Being Proactive 137</p> <p>Establishment of Trust 137</p> <p>Administrative Duties 138</p> <p>Coaching and Training 138</p> <p>Team Building 139</p> <p>Resolving Conflicts 139</p> <p>Assessment of Leadership Competencies 140</p> <p>Strategy 141</p> <p>Software Architecture Strategy 142</p> <p>Strategic Thinking 142</p> <p>Problem Identification 142</p> <p>Problem-solving 143</p> <p>Abstraction 143</p> <p>Generalization 144</p> <p>Visualization 144</p> <p>Software Design Approaches 145</p> <p>Simplification 145</p> <p>Analytical Capabilities 145</p> <p>Influencing 146</p> <p>Promoting Culture 146</p> <p>Strategy Execution Plan 147</p> <p>Assessment of Strategic Competencies 147</p> <p><b>Part 3 Software Architecture Toolbox 149</b></p> <p><b>Chapter 5 Employing Innate Talents to Provide Potent Organizational Solutions 151</b></p> <p>Innate Skills Promote Software Architecture Effectiveness 152</p> <p>Remember: Survival, Survival, Survival 152</p> <p>Consequences of Failing to Invoke Innate Talents 153</p> <p>Employ Chief Innate Talents to Become an Effective Software Architect 154</p> <p>The Power of Creativity 154</p> <p>The Benefits of Unleashing Software Architecture Creativity 155</p> <p>Unleash the Power of Software Architecture Creativity 155</p> <p>The Potency of Imagination 157</p> <p>The Benefits of Harnessing Imagination 158</p> <p>Unleash the Power of Imagination 159</p> <p>Software Design Aesthetic 162</p> <p>Technical Proficiency and Aesthetic Talents Drive Software Design 162</p> <p>The Chief Contribution of Design Aesthetic Talents to Software Architecture 163</p> <p>Curiosity Attributes 167</p> <p>The Contribution of Curiosity to Software Architecture 167</p> <p>The Influencing Facets of Curiosity on Software Architecture Practices 168</p> <p><b>Chapter 6 Software Architecture Environment Construction 173</b></p> <p>Benefits of the Software Architecture Environment Construction Discipline 174</p> <p>Must Haves: Problem Statements and Requirements 174</p> <p>Never Start a Software Design Project Without Understanding the Problems 175</p> <p>Never Start a Software Design Project Without Requirements 176</p> <p>Software Architecture Structures 176</p> <p>Micro Level: Multidimensional Structures of Software Implementations 176</p> <p>Macro Level: 3D Software Architecture Environment Structure 177</p> <p>Software Architecture Environment: Driven by an Uncontrolled Quantum Landscape Behavior 178</p> <p>Software Architecture Environment: An Intelligent Topological Space 179</p> <p>Deformation Aspects of a Multidimensional Software Architecture Environment 181</p> <p>Entanglement Effects in a Software Architecture Environment 182</p> <p>Software Architecture Environment Forces Drive Software Behavior 183</p> <p>Probability Assessment of Software Operations and Behavior 184</p> <p>Software Architecture Environment Positive and Negative Forces 184</p> <p>Software Architecture Environment Gravitational Forces 185</p> <p>The Impetus for Granting Software Architecture Gravitational Powers to Software Implementations 186</p> <p>Software Architecture Gravitational Force Intensity 187</p> <p>The Cost of Unbalanced Software Architecture Environment Gravitational Forces 187</p> <p>Competing Software Architecture Environment Forces 188</p> <p>Software Architecture Environment: A Survival Game Space 188</p> <p>Maintaining a Pragmatic Balance Between Competing Software Architecture Forces 189</p> <p>Mitigating the Competing Forces Challenge 190</p> <p>Software Architecture Environment Harmonizing and Disharmonizing Forces 190</p> <p>Chief Properties of Harmonizing Forces in a Software Architecture Environment 191</p> <p>Chief Properties of Disharmonizing Forces in a Software Architecture Environment 193</p> <p>Genetic Encoding of a Software Architecture Environment 194</p> <p>Difficulties of Restructuring a Software Architecture Environment 194</p> <p>Encoding a Software Architecture Environment 195</p> <p>Influences on Social, Behavioral, and Business Goals 195</p> <p>Software Architecture Environment Construction Life Cycle 196</p> <p>Software Architecture Environment Construction Process 197</p> <p>Creating a Software Architecture Environment Construction Balance Table 197</p> <p>Software Architecture Environment Construction Design Activities 199</p> <p>Use Case I: Software Architecture Environment Composition and Decomposition Design Activities 201</p> <p>Design- Time vs. Runtime Environment Composition and Decomposition Design Activities 201</p> <p>Composition and Decomposition Design Methods 202</p> <p>Composition and Decomposition Process Outline 203</p> <p>Use Case II: Software Architecture Environment Integration and Disintegration Design Activities 204</p> <p>When to Apply Integration and Disintegration Design Activities 205</p> <p>Integration and Disintegration Design Methods 205</p> <p>Integration and Disintegration Process Outline 206</p> <p>Use Case III: Software Architecture Environment Centralization and Decentralization Design Activities 208</p> <p>When to Employ the Software Environment Centralization and Decentralization Design Activities 208</p> <p>Centralization and Decentralization Design Methods 209</p> <p>Software Architecture Environment Centralization and Decentralization Process Outline 210</p> <p>Use Case IV: Software Architecture Environment Elasticity and Inelasticity Design Activities 211</p> <p><b>Chapter 7 When to Employ Elasticity and Inelasticity Design Activities 212</b></p> <p>Elasticity and Inelasticity Design Methods 213</p> <p>Software Architecture Elasticity and Inelasticity Design Process Outline 214</p> <p>Use Case V: Software Architecture Environment Synchronization and Desynchronization Design Activities 215</p> <p>When to Employ Environment Synchronization and Desynchronization Design Activities 216</p> <p>Environment Synchronization and Desynchronization Design Methods 216</p> <p>Software Architecture Environment Synchronization and Desynchronization Design Process Outline 218</p> <p>Construction Laws of a Software Architecture Environment 219</p> <p>Best Practices for Software Architecture Environment Construction 220</p> <p>Structural Construction of Software Implementations in Multidimensional Environments 223</p> <p>Software Architecture Solids: Rudimentary Geometrical Design Structures 224</p> <p>Atomic Solid 225</p> <p>Composite Solid 227</p> <p>Monolithic Solid 228</p> <p>Interface Solid 229</p> <p>Pipe Solid 230</p> <p>Inclusive Utilization of Pipe Solids 231</p> <p>Exclusive Utilization of Pipe Solids 232</p> <p>Internal Utilization of Pipe Solids 233</p> <p>Data Solid 234</p> <p>Software Architecture Solids’ Attribute Summary 236</p> <p>Software Architecture Dimensional Model 237</p> <p>Software Architecture: Zero Dimension 238</p> <p>Software Architecture: One Dimension 239</p> <p>Software Architecture: Two Dimensions 240</p> <p>What Impacts the Length and Width Dimensions of a</p> <p>2D Software Structure? 241</p> <p>Software Architecture: Three Dimensions 242</p> <p>Volumes of 3D Software Structures 242</p> <p>Increase in Software Architecture Level of Specificity in a</p> <p>3D Computing World 243</p> <p>Software Population Sustainability in an Architecture Environment Space: A Capacity Planning Challenge 245</p> <p>Comparative Perspectives in a Software Architecture Space 246</p> <p>3D Software Structures in a Software Architecture Computing Space 247</p> <p>The Impetus for Establishing a 3D Software Architecture Space 247</p> <p>Chief Features of Software Architecture Computing Space 249</p> <p>Influences of Software Structures on Software Architecture Computing Space 250</p> <p>Relative Positions in a 3D Software Architecture Computing Space 250</p> <p>Coordinate Axes: Skeleton of a Software Architecture Computing Space 251</p> <p>Software Architecture Computing Space Logical Coordinate System 252</p> <p>Cardinal and Intercardinal Physical Directions in Software Architecture Computing Space 253</p> <p>Applying Cardinal and Intercardinal Directions to Software Architecture Computing Space 254</p> <p>Marrying a Logical Coordinate System with Cardinal and Intercardinal Physical Directions System 255</p> <p>Leveraging the Z- Axis to Create Floors in a Software Architecture Computing Space 256</p> <p>Distribution Styles of 3D Software Implementations in an Architecture Computing Space 257</p> <p>Federated Distribution Style 258</p> <p>Flooring Distribution Style 260</p> <p>Symmetrical and Asymmetrical Distribution Styles 261</p> <p>Symmetrical Distribution Style 261</p> <p>Asymmetrical Distribution Style 263</p> <p>Construction Life Cycle of Software Implementations 264</p> <p>Software Construction Process 265</p> <p>Creating a Software Construction Balance Table 265</p> <p>Software Construction Design Activities 266</p> <p>Use Case I: Thicken and Contract Design Activities 267</p> <p>When to Apply Thicken and Contract Design Activities 268</p> <p>Thicken and Contract Design Methods 269</p> <p>Software Structure Thickening and Contracting Process Outline 270</p> <p>Use Case II: Lengthen and Shorten Design Activities 272</p> <p>When to Apply the Lengthen and Shorten Design Activities 273</p> <p>Lengthen and Shorten Design Methods 273</p> <p>Software Structure Lengthening and Shortening Process Outline 275</p> <p>Use Case III: Layer and Delayer Design Activities 277</p> <p>When to Apply Layer and Delayer Design Activities 277</p> <p>Layer and Delayer Design Methods 278</p> <p>Layer and Delayer Process Outline 279</p> <p>Governing Laws for Software Construction in a 3D Computing World 281</p> <p>Best Practices for Constructing Software Implementations 282</p> <p><b>Part 4 Software Architecture Interview Preparations 285</b></p> <p><b>Chapter 8 Preparing for a Software Architecture Interview: A Winning Strategy 287</b></p> <p>Software Architecture Job Interview Strategy 288</p> <p>Preparing a Job Interview Defense Plan 288</p> <p>Preparing a Job Interview Attack Plan 289</p> <p>Software Architecture Job Interview Preparation Model 290</p> <p>Software Architecture Job Interview Defense Plan 291</p> <p>Study and Analyze the Job Description 291</p> <p>Start with Identifying the Scope of the Software Architecture Job Requirements 292</p> <p>Dive Deep into the Software Architect Job Description 293</p> <p>Start with Analyzing the Summary Portion of the Job Requirements 294</p> <p>Create a Findings Table Version I for the Job Description 295</p> <p>Next, Analyze the Responsibilities Portion of the Job Requirements 296</p> <p>Then, Update the Findings Table Version II of the Job Description 296</p> <p>Last, Analyze the Software Architect Skills Portion of the Job Requirements 297</p> <p>Do Not Forget to Update the Findings Table of the Job Description 298</p> <p>Create a Software Architect Skill Competency Model for the Job Description 299</p> <p>Skill Competency Model’s Requirements and Practices 300</p> <p>Skill Competency Model’s Disciplines 301</p> <p>Design Discipline’s Deliverables 301</p> <p>Cybersecurity Discipline Deliverables 301</p> <p>Products Selection and Evaluation Discipline’s Deliverables 302</p> <p>SDLC Discipline’s Deliverables 302</p> <p>The Competency Part of the Skill Competency Model 303</p> <p>Discover the Personal Knowledge Gap Before Attending a Job Interview 303</p> <p>Assess Whether the Next Software Architecture Job Is a Strategic Career Move 304</p> <p>Conduct a Software Architecture Mock Interview 305</p> <p>Prepare a Software Architecture Interview Cheat Sheet 306</p> <p>Prepare for Possible Software Architecture Interview Questions 307</p> <p>Software Architecture Job Interview Attack Plan 308</p> <p>Study the Hiring Organization’s Business 309</p> <p>Start by Finding Information About the Hiring Organization 309</p> <p><b>Chapter 9 Leveraging Business Knowledge During an Interview 311</b></p> <p>Understand the Business Model 312</p> <p>Get Familiar with the Hiring Company’s Culture 314</p> <p>Conduct a Quick SWOT Analysis 315</p> <p>Understand the Hiring Organization’s Technology 316</p> <p>Technological Information Sources 316</p> <p>Discover the Environment’s Technology Stack 318</p> <p>Learn About the Development Technology Stack 319</p> <p>Study the Applications 320</p> <p>Identify Specific IT Projects 321</p> <p>Demonstrate Enterprise Architecture Knowledge of the Hiring Organization 321</p> <p>Adopt Software Architecture Lingo 323</p> <p>Use Design Patterns Vocabulary 323</p> <p>Use the Software Architecture Guidelines Lingo to Communicate Solutions 324</p> <p>Remember Software Architecture Tools 328</p> <p>Classification of Software Architecture Tools 329</p> <p>Especially Prepare for Architecture Visualization Tools Questions 332</p> <p>Get Familiar with Software Architecture Analysis and Evaluation Methods 333</p> <p>Be Aware of Early Architecture Evaluation Methods 334</p> <p>Be Aware of Late Architecture Evaluation Methods 335</p> <p>Talk About Software Architecture Analysis Standards 335</p> <p>An Outline for Software Architecture Job Interview Questions 337</p> <p>Behavioral Questions 338</p> <p>Communication 339</p> <p>Interpersonal Relationships 340</p> <p>Software Architecture Leadership 340</p> <p>Skill Assessment Questions 341</p> <p>Software Architecture Attributes Questions 342</p> <p>Software Architecture LifeCycle Questions 343</p> <p>Software Architecture Concepts Questions 346</p> <p>Design Building Blocks Concepts 347</p> <p>Employ Design Building Blocks Concepts to Depict Solutions 347</p> <p>Prepare for the “How to Design” Interview Questions 348</p> <p>Software Architecture Environment Concepts 349</p> <p>Business Concepts 351</p> <p>Consumer Concepts 352</p> <p>Architecture Style, Architecture Pattern, and Design Pattern Questions 353</p> <p>Architecture Patterns vs. Design Patterns 353</p> <p>Understand Architecture Styles 355</p> <p>Remember Contextual Hierarchy of Patterns 355</p> <p>Why Interviewers Ask Architecture and Design Pattern Questions 356</p> <p>Prepare for Architecture and Design Pattern Questions 357</p> <p>Problem-solving and decision- making Questions 358</p> <p>Embrace the Software Architecture Problem- Solving and Decision- Making Process 358</p> <p>Identifying Business Problems 358</p> <p>Attend to the Problem- Solving and Decision- Making Process 359</p> <p>Prepare for Problem- Solving and Decision- Making Questions 360</p> <p>Data- Related Questions 360</p> <p>Focus on Data Aspects Related to Software Architecture 361</p> <p>More Data- Related Interview Questions 361</p> <p>Production Environment Questions 362</p> <p>Characteristics of Software Architecture Environment Hosted in Production 363</p> <p>Production Environment-Related Questions 364</p> <p>Software Architecture Framework Questions 365</p> <p>Focus on Array of Framework Contributions 365</p> <p>Software Architecture Framework Questions 367</p> <p>Index 369</p>

<p><B>MICHAEL BELL</B> 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.

<p><b>A strategic state-of-the-art software architecture manual for all skill levels</b> <p>In <i>Software Architect</i>, veteran enterprise and solution architect Michael Bell delivers a hands-on playbook of best practices for aspiring and practicing software architects, seeking to improve their software design, integration, communication, presentation, and knowledge acquisition skills. He explores the career enablement, career planning, self-training, and self-improvement topics you’ll need to increase your ability to offer powerful and effective business and technological solutions. <p>In the book, you’ll learn how to help companies promote business and technological innovation and transformation by implementing modern and first-class software design, deployment, integration, and operations. <p><i>Software Architect</i> also includes: <ul><li> A modern software architect’s toolbox that includes best practices for multi-dimensional software design and integration in an enterprise quantum computing ecosystem</li> <li> A breakdown of the various types of software architects, as well as useful self-assessments for aspiring and practicing professionals</li> <li> Skill acquisition strategies for software architects along with strategic approaches to ace software architecture interviews</li></ul> <p>An indispensable manual for aspiring-to-be architects, software architects-in-training, and practicing software architects, <i>Software Architect</i> is an essential read for anyone hoping to improve their ability to deliver robust business and technical solutions to enterprises everywhere.

US