基本信息

书名：软件构架实践( 3版 影 版)

定价：79.00元

作者：(美)巴斯,等

出版社： 华大学出版社

出版日期：2013-02-01

ISBN：9787302312932

字数：

页码：

版次：1

装帧： 装

开本：大16开

商品重量：0.822kg

编辑

内容提要

书籍
计算机书籍
　　十年间，敏捷 软件工程，冰与火之歌
　　《软件构架实践》是一本荣获大奖且影响 远的经典之作，目前已经全面修订，充分体现了这一领域的*进展。基于软件开发的 实现状，本书再次以全新的角度 入软件构架的相关概念和*实践，阐述软件是如何架构的，软件中的各个要素之间又是如何相互作用的。有别于实现细节、算法和数据表示，软件构架是达成高品质软件的关键，是一种可重用于后续软件的 产，并且对软件企业的商业策略至关重要。
　　作者围绕着软件构架影响周期的概念对本书前一版进 了重构。每个周期都表 了软件构架是如何产生影响的，同时它又受 些因素的影响，软件构架在 定的背景下发挥着关键性的作用。这些背景包括技*环境、项目的生命周期、组织的业务概况和架构师的实践。作者还进一步 展了质量属性，仍然以构架理念为中心（用单独一章内容来专 介绍每个属性），拓宽了软件构架模式。 target='_blank'书籍
target='_blank'计算机书籍
　　十年间，敏捷 & 软件工程，冰与火之歌
　　《软件构架实践》是一本荣获大奖且影响 远的经典之作，目前已经全面修订，充分体现了这一领域的*进展。基于软件开发的 实现状，本书再次以全新的角度 入软件构架的相关概念和*实践，阐述软件是如何架构的，软件中的各个要素之间又是如何相互作用的。有别于实现细节、算法和数据表示，软件构架是达成高品质软件的关键，是一种可重用于后续软件的 产，并且对软件企业的商业策略至关重要。
　　作者围绕着软件构架影响周期的概念对本书前一版进 了重构。每个周期都表 了软件构架是如何产生影响的，同时它又受 些因素的影响，软件构架在 定的背景下发挥着关键性的作用。这些背景包括技*环境、项目的生命周期、组织的业务概况和架构师的实践。作者还进一步 展了质量属性，仍然以构架理念为中心（用单独一章内容来专 介绍每个属性），拓宽了软件构架模式。
　　如果要参与或者 责大型软件的设计、开发和管理，你会发现这本书是很有价值的参考 源，可以帮助你紧跟技*潮流。
　　《软件构架实践( 3版 影 版)》 *主题
　　软件构架的背景：技*角度、项目角度、业务角度和职业角度
　　软件构架的竞争力：对于个人和组织的意义
　　业务目标的依据及其如何影响软件构架
　　软件构架层面的重要需求及其确定方式
　　软件生命周期中的构架，包括以设计思维为前提的生成-；实现期间的软件构架一致性；构架与；构架与敏捷开发
　　构架与当前技*潮流， 如云计算，社交网络和终端用 设备

目录

preface xv
reader’s guide xvii
acknowledgments x
part one: introdu*ion
chapter 1: wh* is software archite*ure
1.1 wh* software archite*ure is and wh* it isn’t
1.2 archite*ural stru*ures and views
1.3 archite*ural p*terns
1.4 wh* *kes a “good” archite*ure
1.5 sum*ry
1.6 for further reading
1.7 discussion questions
chapter 2: why is software archite*ure important
2.1 inhibiting or enabling a system’s quality *tributes
2.2 reasoning about and *naging change
2.3 predi*ing system qualities
2.4 enhancing *nic*ion among stakeholde*
2.5 carrying early design decisions
2.6 defining constraints on an implement*ion

.2.7 influencing the organiz*ional stru*ure
2.8 enabling evolutionary prototyping
2.9 improving cost and schedule esti*tes
2.10 supplying a transferable, reusable model
2.11 allowing incorpor*ion of independently developedponents
2.12 restri*ing the vocabulary of design altern*ives
2.13 providing a basis for training
2.14 sum*ry
2.15 for further reading
2.16 discussion questions
chapter 3: the *ny contexts of software archite*ure
3.1 archite*ure in a technical context
3.2 archite*ure in a pro*e* life-cycle context
3.3 archite*ure in a business context
3.4 archite*ure in a professional context
3.5 stakeholde*
3.6 how is archite*ure influenced
3.7 wh* do archite*ures influence
3.8 sum*ry
3.9 for further reading
3.10 discussion questions
part two: quality *tributes
chapter 4: unde*tanding quality *tributes
4.1 archite*ure and requirements
4.2 fun*ionality
4.3 quality *tribute consider*ions
4.4 specifying quality *tribute requirements
4.5 achieving quality *tributes through ta*ics
4.6 guiding quality design decisions
4.7 sum*ry
4.8 for further reading
4.9 discussion questions
chapter 5: availability
5.1 availability general scenario
5.2 ta*ics for availability
5.3 a design checklist for availability
5.4 sum*ry
5.5 for further reading
5.6 discussion questions
chapter 6: interoperability
6.1 interoperability general scenario
6.2 ta*ics for interoperability
6.3 a design checklist for interoperability
6.4 sum*ry
6.5 for further reading
6.6 discussion questions
chapter 7: modifiability
7.1 modifiability general scenario
7.2 ta*ics for modifiability
7.3 a design checklist for modifiability
7.4 sum*ry
7.5 for further reading
7.6 discussion questions
chapter 8: perfor*nce
8.1 perfor*nce general scenario
8.2 ta*ics for perfor*nce
8.3 a design checklist for perfor*nce
8.4 sum*ry
8.5 for further reading
8.6 discussion questions
chapter 9: security
9.1 security general scenario
9.2 ta*ics for security
9.3 a design checklist for security
9.4 sum*ry
9.5 for further reading
9.6 discussion questions
chapter 10: testability
10.1 testability general scenario
10.2 ta*ics for testability
10.3 a design checklist for testability
10.4 sum*ry
10.5 for further reading
10.6 discussion questions
chapter 11: usability
11.1 usability general scenario
11.2 ta*ics for usability
11.3 a design checklist for usability
11.4 sum*ry
11.5 for further reading
11.6 discussion questions
chapter 12: other quality *tributes
12.1 other important quality *tributes
12.2 other c*egories of quality *tributes
12.3 software quality *tributes and system quality*tributes
12.4 using standard lists of quality *tributes–or not
12.5 dealing with “x-ability”: bringing a new quality *tributeinto the fold
12.6 for further reading
12.7 discussion questions
chapter 13: archite*ural ta*ics and p*terns
13.1 archite*ural p*terns
13.2 overview of the p*terns c*alog
13.3 rel*ionships between ta*ics and p*terns
13.4 using ta*ics together
13.5 sum*ry
13.6 for further reading
13.7 discussion questions
chapter 14: quality *tribute modeling and analysis
14.1 modeling archite*ures to enable quality *tributeanalysis
14.2 quality *tribute checklists
14.3 thought experiments and back-of-the-envelope analysis
14.4 experiments, si*l*ions, and prototypes
14.5 analysis * different stages of the life cycle
14.6 sum*ry
14.7 for further reading
14.8 discussion questions
part three: archite*ure in the life cycle
chapter 15: archite*ure in agile pro*e*s
15.1 how *ch archite*ure
15.2 agility and archite*ure methods
15.3 a brief example of agile archite*ing
15.4 guidelines for the agile archite*
15.5 sum*ry
15.6 for further reading
15.7 discussion questions
chapter 16: archite*ure and requirements
16.1 g*hering as* from requirements documents
16.2 g*hering as* by interviewing stakeholde*
16.3 g*hering as* by unde*tanding the business goals
16.4 capturing as* in a utility tree
16.5 tying the methods together
16.6 sum*ry
16.7 for further reading
16.8 discussion questions
chapter 17: designing an archite*ure
17.1 design str*egy
17.2 the *tribute-driven design method
17.3 the steps of add
17.4 sum*ry
17.5 for further reading
17.6 discussion questions
chapter 18: documenting software archite*ures
18.1 uses and audiences for archite*ure document*ion
18.2 not*ions for archite*ure document*ion
18.3 views
18.4 choosing the views
18.5 bining views
18.6 building the document*ion package
18.7 documenting behavior
18.8 archite*ure document*ion and quality *tributes
18.9 documenting archite*ures th* change faster than you candocument them
18.10 documenting archite*ure in an agile developmentpro*e*
18.11 sum*ry
18.12 for further reading
18.13 discussion questions
chapter 19: archite*ure, implement*ion, and testing
19.1 archite*ure and implement*ion
19.2 archite*ure and testing
19.3 sum*ry
19.4 for further reading
19.5 discussion questions
chapter 20: archite*ure reconstru*ion and confor*nce
20.1 archite*ure reconstru*ion process
20.2 raw view extra*ion
20.3 d*abase constru*ion
20.4 view fusion
20.5 archite*ure analysis: finding viol*ions
20.6 guidelines
20.7 sum*ry
20.8 for further reading
20.9 discussion questions
chapter 21: archite*ure evalu*ion
21.1 evalu*ion fa*o*
21.2 the archite*ure tradeoff analysis method
21.3 lightweight archite*ure evalu*ion
21.4 sum*ry
21.5 for further reading
21.6 discussion questions
chapter 22: *nagement and governance
22.1 planning
22.2 organizing
22.3 implementing
22.4 measuring
22.5 governance
22.6 sum*ry
22.7 for further reading
22.8 discussion questions
part four: archite*ure and business
chapter 23: economic analysis of archite*ures
23.1 decision-*king context
23.2 the basis for the economic analyses
23.3 putting theory into pra*ice: the cbam
23.4 case study: the nasa ecs pro*e*
23.5 sum*ry
23.6 for further reading
23.7 discussion questions
chapter 24: archite*ure petence
24.1 petence of individuals: duties, skills, and knowledge ofarchite*s
24.2 petence of a software archite*ure organiz*ion
24.3 sum*ry
24.4 for further reading
24.5 discussion questions
chapter 25: archite*ure and software produ* lines
25.1 an example of produ* line variability
25.2 wh* *kes a software produ* line work
25.3 produ* line scope
25.4 the quality *tribute of variability
25.5 the role of a produ* line archite*ure
25.6 vari*ion mechanisms
25.7 evalu*ing a produ* line archite*ure
25.8 key software produ* line issues
25.9 sum*ry
25.10 for further reading
25.11 discussion questions
part five: the brave new world
chapter 26: archite*ure in the cloud
26.1 basic cloud definitions
26.2 service models and deployment options
26.3 economic *ustific*ion
26.4 base mechanisms
26.5 sample technologies
26.6 archite*ing in a cloud environment
26.7 sum*ry
26.8 for further reading
26.9 discussion questions
chapter 27: archite*ures for the edge
27.1 the ecosystem of edge-dominant systems
27.2 changes to the software development life cycle
27.3 implic*ions for archite*ure
27.4 implic*ions of the metropolis model
27.5 sum*ry
27.6 for further reading
27.7 discussion questions
chapter 28: epilogue
references
about the autho*
index

作者介绍

文摘

序言