برای استفاده از امکانات سیستم، گزینه جاوا اسکریپت در مرورگر شما باید فعال باشد
صفحه
از
0
Software architecture in practice
Bass, Len.
اطلاعات کتابشناختی
Software architecture in practice
پدیدآور اصلی :
Bass, Len.
ناشر :
Addison-Wesley,
سال انتشار :
2003
موضوع ها :
Software architecture. System design.
شماره راهنما :
QA 76 .754 .B37 2003
جستجو در محتوا
ترتيب
شماره صفحه
امتياز صفحه
فهرست مطالب
Main Page
(1)
Table of content
(3)
Copyright
(8)
Preface
(10)
What's New in the Second Edition
(12)
Acknowledgments
(14)
Reader's Guide
(15)
Audience
(16)
Parts and Chapters
(17)
Part One : Envisioning an Architecture
(18)
Part Two : Creating an Architecture
(19)
Part Three : Analyzing an Architecture
(21)
Part Four : Moving from One System to Many
(22)
Case Study Organization
(24)
Threads Through the Book
(25)
Sidebars
(26)
Part One: Envisioning Architecture
(27)
Chapter 1. The Architecture Business Cycle
(28)
1.1 Where Do Architectures Come From?
(31)
1.2 Software Processes and the Architecture Business Cycle
(37)
1.3 What Makes a 'Good' Architecture?
(40)
1.4 Summary
(42)
1.5 Discussion Questions
(43)
Chapter 2. What Is Software Architecture?
(44)
2.1 What Software Architecture Is and What It Isn't
(45)
2.2 Other Points of View
(48)
2.3 Architectural Patterns, Reference Models, and Reference Architectures
(50)
2.4 Why Is Software Architecture Important?
(52)
2.5 Architectural Structures and Views
(60)
2.6 Summary
(66)
2.7 For Further Reading
(67)
2.8 Discussion Questions
(70)
Chapter 3. A-7E Avionics System: A Case Study in Utilizing Architectural Structures
(71)
3.1 Relationship to the Architecture Business Cycle
(72)
3.2 Requirements and Qualities
(73)
3.3 Architecture for the A-7E Avionics System
(78)
3.4 Summary
(89)
3.5 For Further Reading
(91)
3.6 Discussion Questions
(92)
Part Two: Creating an Architecture
(93)
Chapter 4. Understanding Quality Attributes
(94)
4.1 Functionality and Architecture
(95)
4.2 Architecture and Quality Attributes
(96)
4.3 System Quality Attributes
(98)
4.4 Quality Attribute Scenarios in Practice
(102)
4.5 Other System Quality Attributes
(118)
4.6 Business Qualities
(119)
4.7 Architecture Qualities
(120)
4.8 Summary
(121)
4.9 For Further Reading
(122)
4.10 Discussion Questions
(123)
Chapter 5. Achieving Qualities
(124)
5.1 Introducing Tactics
(125)
5.2 Availability Tactics
(126)
5.3 Modifiability Tactics
(130)
5.4 Performance Tactics
(135)
5.5 Security Tactics
(140)
5.6 Testability Tactics
(143)
5.7 Usability Tactics
(145)
5.8 Relationship of Tactics to Architectural Patterns
(148)
5.9 Architectural Patterns and Styles
(149)
5.10 Summary
(151)
5.11 Discussion Questions
(152)
5.12 For Further Reading
(153)
Chapter 6. Air Traffic Control: A Case Study in Designing for High Availability
(154)
6.1 Relationship to the Architecture Business Cycle
(157)
6.2 Requirements and Qualities
(158)
6.3 Architectural Solution
(161)
6.4 Summary
(175)
6.5 For Further Reading
(176)
6.6 Discussion Questions
(177)
Chapter 7. Designing the Architecture
(178)
7.1 Architecture in the Life Cycle
(179)
7.2 Designing the Architecture
(181)
7.3 Forming the Team Structure
(192)
7.4 Creating a Skeletal System
(195)
7.5 Summary
(197)
7.6 For Further Reading
(199)
7.7 Discussion Questions
(200)
Chapter 8. Flight Simulation: A Case Study in an Architecture for Integrability
(201)
8.1 Relationship to the Architecture Business Cycle
(203)
8.2 Requirements and Qualities
(205)
8.3 Architectural Solution
(209)
8.4 Summary
(222)
8.5 For Further Reading
(224)
8.6 Discussion Questions
(225)
Chapter 9. Documenting Software Architectures
(226)
9.1 Uses of Architectural Documentation
(227)
9.2 Views
(230)
9.3 Choosing the Relevant Views
(231)
9.4 Documenting a View
(234)
9.5 Documentation across Views
(241)
9.6 Unified Modeling Language
(244)
9.7 Summary
(254)
9.8 For Further Reading
(255)
9.9 Discussion Questions
(256)
Chapter 10. Reconstructing Software Architectures
(257)
10.1 Introduction
(258)
10.2 Information Extraction
(261)
10.3 Database Construction
(264)
10.4 View Fusion
(266)
10.5 Reconstruction
(268)
10.6 Example
(274)
10.7 Summary
(283)
10.8 For Further Reading
(284)
10.9 Discussion Questions
(285)
Part Three: Analyzing Architectures
(286)
Chapter 11. The ATAM: A Comprehensive Method for Architecture Evaluation
(292)
11.1 Participants in the ATAM
(293)
11.2 Outputs of the ATAM
(295)
11.3 Phases of the ATAM
(297)
11.4 The Nightingale System: A Case Study in Applying the ATAM
(309)
11.5 Summary
(324)
11.6 For Further Reading
(325)
11.7 Discussion Questions
(326)
Chapter 12. The CBAM: A Quantitative Approach to Architecture Design Decision Making
(327)
12.1 Decision-Making Context
(328)
12.2 The Basis for the CBAM
(330)
12.3 Implementing the CBAM
(335)
12.4 Case Study: The NASA ECS Project
(337)
12.5 Results of the CBAM Exercise
(345)
12.6 Summary
(346)
12.7 For Further Reading
(347)
12.8 Discussion Questions
(348)
Chapter 13. The World Wide Web'A Case Study in Interoperability
(349)
13.1 Relationship to the Architecture Business Cycle
(350)
13.2 Requirements and Qualities
(352)
13.3 Architectural Solution
(356)
13.4 Another Cycle through the ABC: The Evolution of Web-Based E-Commerce Architectures
(362)
13.5 Achieving Quality Goals
(367)
13.6 The Architecture Business Cycle Today
(368)
13.7 Summary
(370)
13.8 For Further Reading
(372)
13.9 Discussion Questions
(373)
Part Four: Moving From One System to Many
(374)
Chapter 14. Software Product Lines: Re-using Architectural Assets
(375)
14.1 Overview
(376)
14.2 What Makes Software Product Lines Work?
(378)
14.3 Scoping
(380)
14.4 Architectures for Product Lines
(383)
14.5 What Makes Software Product Lines Difficult?
(386)
14.6 Summary
(389)
14.7 For Further Reading
(390)
14.8 Discussion Question
(391)
Chapter 15. CelsiusTech: A Case Study in Product Line Development
(392)
15.1 Relationship to the Architecture Business Cycle
(394)
15.2 Requirements and Qualities
(410)
15.3 Architectural Solution
(412)
15.4 Summary
(420)
15.5 For Further Reading
(421)
15.6 Discussion Questions
(422)
Chapter 16. J2EE/EJB: A Case Study of an Industry-Standard Computing Infrastructure
(423)
16.1 Relationship to the Architecture Business Cycle
(424)
16.2 Requirements and Qualities
(426)
16.3 Architectural Solution
(429)
16.4 System Deployment Decisions
(443)
16.5 Summary
(448)
16.6 For Further Reading
(449)
16.7 Discussion Questions
(450)
Chapter 17. The Luther Architecture: A Case Study in Mobile Applications Using J2EE
(451)
17.1 Relationship to the Architecture Business Cycle
(453)
17.3 Architectural Solution
(459)
17.4 How Luther Achieved Its Quality Goals
(473)
17.5 Summary
(474)
17.6 For Further Reading
(475)
17.7 Discussion Questions
(476)
Chapter 18. Building Systems from Off-the-Shelf Components
(477)
18.1 Impact of Components on Architecture
(479)
18.2 Architectural Mismatch
(480)
18.3 Component-Based Design as Search
(485)
18.4 ASEILM Example
(489)
18.5 Summary
(499)
18.6 Further Reading
(500)
Chapter 19. Software Architecture in the Future
(501)
19.1 The Architecture Business Cycle Revisited
(503)
19.2 Creating an Architecture
(504)
19.3 Architecture within the Life Cycle
(506)
19.4 The Impact of Commercial Components
(507)
19.5 Summary
(509)
Acronyms
(510)
References
(515)
