Len Bass编著的《软件构架实践(第3版影印版)》以全新的角度引入软件构架的相关概念和最佳实践，阐述软件系统是如何架构的，软件系统中的各个要素之间又是如何相互作用的。如果要参与或者负责大型软件系统的设计、开发和管理，你会发现这本书是很有价值的参考资源，可以帮助你紧跟技术潮流。

Len Bass编著的《软件构架实践(第3版影印版)》是一本荣获大奖且影响深远的经典之作，目前已经全面修订，充分体现了这一领域的最新进展。基于软件开发的真实现状，本书再次以全新的角度引入软件构架的相关概念和最佳实践，阐述软件系统是如何架构的，软件系统中的各个要素之间又是如何相互作用的。有别于实现细节、算法和数据表示，软件构架是达成高品质软件的关键，是一种可重用于后续软件系统的资产，并且对软件企业的商业策略至关重要。

作者围绕着软件构架影响周期的概念对本书前一版进行了重构。每个周期都表明了软件构架是如何产生影响的，同时它又受哪些因素的影响，软件构架在特定的背景下发挥着关键性的作用。这些背景包括技术环境、项目的生命周期、组织的业务概况和架构师的专业实践。作者还进一步延展了质量属性，仍然以构架理念为中心（用单独一章内容来专门介绍每个属性），拓宽了软件构架模式。

如果要参与或者负责大型软件系统的设计、开发和管理，你会发现这《软件构架实践(第3版影印版)》是很有价值的参考资源，可以帮助你紧跟技术潮流。

preface xv

reader’s guide xvii

acknowledgments xix

Part one: introduction 1

 Chapter 1: what is software architecture? 3

1.1 what software architecture is and what it isn’t 4

1.2 architectural structures and views 9

1.3 architectural patterns 18

1.4 what makes a “good” architecture? 19

1.5 summary 21

1.6 for further reading 22

1.7 discussion questions 23

 Chapter 2: why is software architecture important? 25

2.1 inhibiting or enabling a system’s quality attributes 26

2.2 reasoning about and managing change 27

2.3 predicting system qualities 28

2.4 enhancing communication among stakeholders 29

2.5 carrying early design decisions 31

2.6 defining constraints on an implementation 32

2.7 influencing the organizational structure 33

2.8 enabling evolutionary prototyping 33

2.9 improving cost and schedule estimates 34

2.10 supplying a transferable, reusable model 35

2.11 allowing incorporation of independently developed components 35

2.12 restricting the vocabulary of design alternatives 36

2.13 providing a basis for training 37

2.14 summary 37

2.15 for further reading 38

2.16 discussion questions 38

 Chapter 3: the many contexts of software architecture 39

3.1 architecture in a technical context 40

3.2 architecture in a project life-cycle context 44

3.3 architecture in a business context 49

3.4 architecture in a professional context 51

3.5 stakeholders 52

3.6 how is architecture influenced? 56

3.7 what do architectures influence? 57

3.8 summary 59

3.9 for further reading 59

3.10 discussion questions 60

Part two: quality attributes 61

 Chapter 4: understanding quality attributes 63

4.1 architecture and requirements 64

4.2 functionality 65

4.3 quality attribute considerations 65

4.4 specifying quality attribute requirements 68

4.5 achieving quality attributes through tactics 70

4.6 guiding quality design decisions 72

4.7 summary 76

4.8 for further reading 77

4.9 discussion questions 77

 Chapter 5: availability 79

5.1 availability general scenario 85

5.2 tactics for availability 87

5.3 a design checklist for availability 96

5.4 summary 98

5.5 for further reading 99

5.6 discussion questions 100

 Chapter 6: interoperability 103

6.1 interoperability general scenario 107

6.2 tactics for interoperability 110

6.3 a design checklist for interoperability 114

6.4 summary 115

6.5 for further reading 116

6.6 discussion questions 116

 Chapter 7: modifiability 117

7.1 modifiability general scenario 119

7.2 tactics for modifiability 121

7.3 a design checklist for modifiability 125

7.4 summary 128

7.5 for further reading 128

7.6 discussion questions 128

 Chapter 8: performance 131

8.1 performance general scenario 132

8.2 tactics for performance 135

8.3 a design checklist for performance 142

8.4 summary 145

8.5 for further reading 145

8.6 discussion questions 145

 Chapter 9: security 147

9.1 security general scenario 148

9.2 tactics for security 150

9.3 a design checklist for security 154

9.4 summary 156

9.5 for further reading 157

9.6 discussion questions 158

 Chapter 10: testability 159

10.1 testability general scenario 162

10.2 tactics for testability 164

10.3 a design checklist for testability 169

10.4 summary 172

10.5 for further reading 172

10.6 discussion questions 173

 Chapter 11: usability 175

11.1 usability general scenario 176

11.2 tactics for usability 177

11.3 a design checklist for usability 181

11.4 summary 183

11.5 for further reading 183

11.6 discussion questions 183

 Chapter 12: other quality attributes 185

12.1 other important quality attributes 185

12.2 other categories of quality attributes 189

12.3 software quality attributes and system quality attributes 190

12.4 using standard lists of quality attributes–or not 193

12.5 dealing with “x-ability”: bringing a new quality attribute into the fold 196

12.6 for further reading 200

12.7 discussion questions 201

 Chapter 13: architectural tactics and patterns 203

13.1 architectural patterns 204

13.2 overview of the patterns catalog 205

13.3 relationships between tactics and patterns 238

13.4 using tactics together 242

13.5 summary 247

13.6 for further reading 248

13.7 discussion questions 249

 Chapter 14: quality attribute modeling and analysis 251

14.1 modeling architectures to enable quality attribute analysis 252

14.2 quality attribute checklists 260

14.3 thought experiments and back-of-the-envelope analysis 262

14.4 experiments, simulations, and prototypes 264

14.5 analysis at different stages of the life cycle 265

14.6 summary 266

14.7 for further reading 267

14.8 discussion questions 269

Part three: architecture in the life cycle 271

 Chapter 15: architecture in agile projects 275

15.1 how much architecture? 277

15.2 agility and architecture methods 281

15.3 a brief example of agile architecting 283

15.4 guidelines for the agile architect 286

15.5 summary 287

15.6 for further reading 288

15.7 discussion questions 289

 Chapter 16: architecture and requirements 291

16.1 gathering asrs from requirements documents 292

16.2 gathering asrs by interviewing stakeholders 294

16.3 gathering asrs by understanding the business goals 296

16.4 capturing asrs in a utility tree 304

16.5 tying the methods together 308

16.6 summary 308

16.7 for further reading 309

16.8 discussion questions 309

 Chapter 17: designing an architecture 311

17.1 design strategy 311

17.2 the attribute-driven design method 316

17.3 the steps of add 318

17.4 summary 325

17.5 for further reading 325

17.6 discussion questions 326

 Chapter 18: documenting software architectures 327

18.1 uses and audiences for architecture documentation 328

18.2 notations for architecture documentation 329

18.3 views 331

18.4 choosing the views 341

18.5 combining views 343

18.6 building the documentation package 345

18.7 documenting behavior 351

18.8 architecture documentation and quality attributes 354

18.9 documenting architectures that change faster than you can document them 355

18.10 documenting architecture in an agile development project 356

18.11 summary 359

18.12 for further reading 360

18.13 discussion questions 360

 Chapter 19: architecture, implementation, and testing 363

19.1 architecture and implementation 363

19.2 architecture and testing 370

19.3 summary 376

19.4 for further reading 376

19.5 discussion questions 377

 Chapter 20: architecture reconstruction and conformance 379

20.1 architecture reconstruction process 381

20.2 raw view extraction 382

20.3 database construction 386

20.4 view fusion 388

20.5 architecture analysis: finding violations 389

20.6 guidelines 392

20.7 summary 393

20.8 for further reading 394

20.9 discussion questions 395

 Chapter 21: architecture evaluation 397

21.1 evaluation factors 397

21.2 the architecture tradeoff analysis method 400

21.3 lightweight architecture evaluation 415

21.4 summary 417

21.5 for further reading 417

21.6 discussion questions 418

 Chapter 22: management and governance 419

22.1 planning 420

22.2 organizing 422

22.3 implementing 427

22.4 measuring 429

22.5 governance 430

22.6 summary 432

22.7 for further reading 432

22.8 discussion questions 433

Part four: architecture and business 435

 Chapter 23: economic analysis of architectures 437

23.1 decision-making context 438

23.2 the basis for the economic analyses 439

23.3 putting theory into practice: the cbam 442

23.4 case study: the nasa ecs project 450

23.5 summary 457

23.6 for further reading 458

23.7 discussion questions 458

 Chapter 24: architecture competence 459

24.1 competence of individuals: duties, skills, and knowledge of architects 460

24.2 competence of a software architecture organization 467

24.3 summary 475

24.4 for further reading 475

24.5 discussion questions 477

 Chapter 25: architecture and software product lines 479

25.1 an example of product line variability 482

25.2 what makes a software product line work? 483

25.3 product line scope 486

25.4 the quality attribute of variability 488

25.5 the role of a product line architecture 488

25.6 variation mechanisms 490

25.7 evaluating a product line architecture 493

25.8 key software product line issues 494

25.9 summary 497

25.10 for further reading 498

25.11 discussion questions 498

Part five: the brave new world 501

 Chapter 26: architecture in the cloud 503

26.1 basic cloud definitions 504

26.2 service models and deployment options 505

26.3 economic justification 506

26.4 base mechanisms 509

26.5 sample technologies 514

26.6 architecting in a cloud environment 520

26.7 summary 524

26.8 for further reading 524

26.9 discussion questions 525

 Chapter 27: architectures for the edge 527

27.1 the ecosystem of edge-dominant systems 528

27.2 changes to the software development life cycle 530

27.3 implications for architecture 531

27.4 implications of the metropolis model 533

27.5 summary 537

27.6 for further reading 538

27.7 discussion questions 538

 Chapter 28: epilogue 541

references 547

about the authors 561

index 563