Software Architecture Foundations,Theory, and Practice《软件体系结构基础、理论和实践》英文电子书

【实例简介】
Software Architecture Foundations,Theory, and Practice《软件体系结构基础、理论和实践》英文电子书
About the Cover THE ARCHITECTS DREAM, THOMAS COLE, 1840 In The Architect's Dream, Thomas Cole painted a vision of the history of Western civiliza tion as a succession of buildings through time and space. a massive egyptian pyramid and temple, Roman aqueduct, and Greek and Roman temples demonstrate his knowledge of architectural history, likely taken from architectural pattern books given to the artist as partial payment for the commission, showing the range of forms that inspired 19th,century architects. Geographical and historical contrasts separate the right and left sides of the composition. Tall trees mirror the cathedral's steeple, pointing towards Heaven, indicating the inspiration of nature in the architectural form of the church. A sacred place in harmony with nature and God, the shaded church contrasts with the towering classical structures that appear artificial and warn against fleeting power. Inspired by salisbury Cathedral and Chapter house in england, the cathedral suggests the 19th-century Gothic architectural revival in America. Symmetrical capitals frame the sides of the canvas, their forms taken from Salisbury Chapter House, creating a Gothic window. We gaze through the theatrical window to behind the cathedral spire, where the setting sun shines brilliant light through the windows, creating the impression of stained glass, and evoking divine light. Cole's youth and travels in England may have contributed to a sense of national pride that influ- enced his reference to an English Gothic cathedral, an architectural style from shared American and English history, thereby extending american history back in time. With his face turned towards the radiant light emanating through the cathedral steeple, the archi- tect reclines on gigantic pattern books, the catalyst of this vision of creative imagination By including architectural tools, books, and plans alongside the dreaming architect, the artist indicates the importance of engineering and design in growing American commerce elevating the artist and architect's roles. The extraordinary variety and enduring beauty of Thomas Cole,s painting celebrates human creativity The painting provides an apt illustration for a textbook on software architecture Many contemporary software systems have designs that draw heavily from the designs o prior applications. Others take fresh inspiration from social systems or nature. Just as Cole's architect is surrounded by past structures, books, and plans, so the skilled software architect has existing systems and, importantly, a vast store of styles, techniques, processes, and tools from which to choose when confronting a design challenge -LET E RNT Credits Figures 1-4, 1-5, 1-6, and 1-7 courtesy royal Philips n.v Figure 2-13 adapted from Figure 1 from: Weaving Together Requirements and archi- tectures, Bashar Nuseibeh. IEEE Computer 34(2): 115-117. 2001.O IEEE. Used by permission Ch 4 Sidebar: "Styling with Perry and Wolf "Text excerpt from dewayne e. Perry and Alexander L. Wolf. Foundations for the Study of Software Architecture. ACM SIGSOFT Software Engineering Notes 17(4): 40-52. 1992. o Dewayne E. Perry and Alexander L Wolf. Used by permission Figure 6-1 adapted from Maier and Rechtin, The Art of Software Architecting, 2nd. ed Copyright C CRC Press. Used with permission Figure 7-18 used by permission of ]eff Magee Figures 8-4, 12-4, and 12-5 adapted from Figures 1, 5: Bowman, R.T. et al, "Linux as a Case Study Its Extracted Software Architecture, " Proceedings of the 21st ACM/ IeeEConferenceonSoftwareenGineering(icse99),pp.555-563.Doi:http://do acm.org/10.1145/302405302691: Copyright o 1999 ACM, Inc. Reprinted by permission The ATAM Figure located at page 320 in this publication has been adapted from the aTAM diagram o 2008 by Carnegie Mellon University and is reproduced in its adapted form in this publication with special permission from the Software Engineering Institute of Carnegie Mellon University. R Architecture Tradeoff Analysis Method and ATAM are registered in the U.s. Patent and Trademark Office by Carnegie Mellon University ANY CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTI TUTE MATERIAL IS FURNISHED ON AN"AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATER INCLUDING, BUT NOT LIMITED TO, WAR- RANTY OF FITNESS FOR PURPOSE OR MERCHANTIBILITY EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNI VERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK OR COPYRIGHT INFRINGEMENT. Neither Carnegie Mellon University nor the Software Engineering Institute directly or indirectly endorse this publication. Accuracy and interpretation of figure 8-12 are the responsibility of Eric Dashofy. The Software Engineering Institute has not participated in the creation of figure 8-12 Figure 10-1 adapted from Figure 1; Figure 11-12 adapted from Figure 4; both from Reconcep- tualizing a Family of heterogeneous Embedded Systems via Explicit arch I Support Sam Malek, Chiyoung Seo, Sharmila ravula, Brad Petrus, and Nenad Medvidovic pro- ceedings of the Twenty-Ninth International Conference on Software Engineering, IEEE Computer Society, pp. 591-601. 2007. O IEEE. Used by permission CREDITS Figure 10-2 from Figure 1 of Software Architectural Support for Handheld Computing Medvidovic, N. Mikic-Rakic, M. Mehta, N.R. Malek, S. IEEE Computer, 36(9): 66-73 2003. C IEEE. Used by permission Figure 10-9 used by permission of Antonio Carzaniga Ch. 11 Sidebar: Skype on Skype"@ 2008 Skype Limited. Used by permission igure 13-1 from Table I in a Call to Action: Look beyond the Horizon. ]. M Wing, IEEE ecurity privacy, 1(6): 62-67, 2003. C IEEE Used by permission Figure 14-1 Diagram by Donald Ryan, from HOW BUILdINGS leARN by Stewart Brand, copyright o 1994 by Stewart Brand Used by permission of Viking Penguin, a division of Penguin Group (usa)Inc Figure 14-5 from Figure 2 of An Architecture- Based Approach to Self-Adaptive Software Peyman Oreizy, Michael M. Gorlick, Richard N. Taylor, Dennis Heimbigner, Greg John son, Nenad Medvidovic, Alex Quilici, David S. Rosenblum, and Alexander l Wolf. IEEE Intelligent Systems 14(3): 54-62. 1999C IEEE Used by permission Ch. 14 Sidebar: Autonomic Computing. Reprint Courtesy of International Business Machines Corporation, copyright 2001 C International Business Machines Corporation Ch. 14 Sidebar: Quiescence. Text excerpt from Kramer, J and Magee, J, "Change Management of Distributed Systems, Proceedings of the 3rd ACM SIGOPS Euro peanWorkshopAutonomyorinterdependenceindistributedsystems?(1988)http://doi acm. org/10. 1145/504092.504113: Copyright 1988 ACM, Inc. Reprinted by permission Portion of Figure 15-14 from Apollo Operations Handbook, Lunar Module LM5 and Subsequent, Volume 1 Subsystems Data(Document LMA790-3-LM5 ), 1968 Figures 16-6& 16-7 Copyright@ The Open Group. Used with permission. TOGAFIM is a Trademark of The open group Figure 16-14 Kroll/Krutchen, RATIONAL UNIFIED PROCESS MADE EASY: PRACT (figure 1.2)@ Pearson Education, Inc. Reproduced by permission of Pearson Educatio Contents 1 The Big Idea 1 The Power of Analogy: The Architecture of Buildings, 2 1.1.1 Limitations of the Analogy, 5 1.2 So, What's the big ldea?, 6 1.2 The Power and Necessity of big Ideas: The Architecture of the Web, 7 1.3 The Power of Architecture in the Small: Architecture on the Desktop, 12 1.4 The Power of Architecture in Business Productivity and Product Lines, 15 1.5 End matter. 20 1.6 Review Questions, 21 1.7 Exercises, 21 1.8 Further Reading, 21 2 Architectures in Context. The reorientation of Software Engineering 23 2. 1 Fundamental Understandings, 24 2.2 Requirements, 25 2.3 Design, 29 2.3. 1 Design Techniques, 31 2.4 Implementation, 33 2.4.1 Implementation Strategies, 35 2.5 Analysis and Testing, 38 2.6 Evolution and Maintenance, 40 2. 7 Processes, 42 2.7.1 The Turbine visualization, 43 2.7.2 Example Process DepictionS, 49 2.8 End Matter, 52 2.9 Review Questions, 53 2.10 Exercises, 54 2.11 Further Reading, 55 Basic Concepts 3.1 Terminology, 58 3.1.1 Architecture, 58 3.1.2 Component, 68 3.1.3 Connector, 70 3. 1. 4 Configuration, 72 3.1.5 Architectural Style, 72 3. 1.6 Architectural Pattern, 73 CONTENTS 3.2 Models, 75 3. 3 Processes, 75 3.4 Stakeholders, 79 3.5 End Matter, 79 3.6 Review Questions, 80 3.7 Exercises, 80 3.8 Further Reading, 8 4 Designing Architectures 83 4.1 The Design Process, 85 4.2 Architectural Conception, 87 4.2.1 Fundamental conceptual Tools, 87 4.2.2 The Grand Tool: Refined Experience, 90 4.3.1 Domain Specific Software Architectures, ural Patterns, 91 4.3 Refined Experience in Action: Styles and architectu 4.3.2 Architectural Patterns, 94 4.3.3 Introduction to Styles, 99 4.3. 4 Simple styles, 102 4.3.5 More Complex Styles, 124 4.3.6 Discussion: Patterns and Styles, 137 4.3.7 Design Recovery, 139 4.4 Architectural Conception in Absence of Experience Unprecedented Design, 144 4.5 Putting it All Together: Design Processes Revisited, 149 4.5. 1 Insights from Requirements, 150 4.5.2 Insights from Implementation, 151 4.6 End Matter, 152 4.7 Review Questions, 153 4.8 Exercises, 154 4.9 Further Reading, 154 Connectors 157 5.1 Connectors in Action: A Motivating Example, 159 5.2 Connector Foundations, 161 5. 3 Connector Roles, 163 5. 4 Connector Types and Their Variation Dimensions, 164 5.4.1 Procedure Call Connectors, 165 5.4.2 Event Connectors, 166 5.4.3 Data Access Connectors, 167 5.4.4 Linkage Connectors, 16 5.4.5 Stream Connectors, 169 5.4.6 Arbitrator Connectors, 170 5.4.7 Adaptor Connectors, 170 5.4.8 Distributor Connectors, 171 CONTENTS 5.5 Example Connectors, 172 5.5.1 Event-Based Data distribution Connectors 173 5.5.2 Grid-Based Data Distribution Connectors, 174 5.5.3 Client-Server-Based Data Distribution Connectors, 175 5.5.4 P2P-Based Data Distribution Connectors, 176 5.6 Using the Connector Framework, 176 5.6.1 Selecting Appropriate Connectors, 177 5.6.2 Detecting Mismatches, 180 5.7 End Matter, 181 5.8 Review Questions, 182 5.9 Exercises. 183 5.10 Further Reading, 183 6 Modeling 185 6.1 Modeling Concepts, 186 6.1.1 Stakeholder- Driven Modeling, 186 6.1.2 Basic architectural c 188 6.1.3 Elements of the Architectural Style 6.1.4 Static and Dynamic Aspects, 1g e, 189 6.1.5 Functional and Non-Functional Aspects, 191 6.2 Ambiguity, Accuracy, and P1 91 6. 2.1 Ambiguity, 192 6.2.2 Accuracy and Precision, 192 6.3 Complex Modeling: Mixed Content and Multiple views, 194 6.3. 1 Views and Viewpoints, 194 6.3.2 Consistency among Views, 196 6.4 Evaluating Modeling Techniques, 198 6.5 Specific Modeling Techniques, 199 6.5.1 Generic Techniques, 199 6.5.2 Early Architecture Description Languages, 209 6.5.3 Domain-and Style-Specific ADLs, 221 6.5.4 Extensible ADLs, 229 6.6 When Systems Become Too Complex to Model, 242 6.7 End Matter, 243 6.8 Review Questions, 246 6.9 Exercises, 246 6.10 Further Reading, 246 / visualization 249 7.1 Visualization Concepts, 250 7.1.1 Canonical Visualizations, 250 7.1.2 Textual Visualizations 251 7. 1.3 Graphical Visualizations, 253 7.1.4 Hybrid Visualizations, 255 7.1.5 The relationship between Visualizations and Views, 255 CONTENTS 7.2 Evaluating visualizations, 2 7.2.2 Constructing a Visualization, 261 7. 2. 3 Coordinating Visualizations, 264 7.2.4 Beyond Design: Using Visualization Dynamically, 266 7.3 Common Issues in Visualization, 268 7.3.1 Same Symbol, Different Meaning, 268 7.3.2 Differences without Meaning, 269 7.3.3 Decorations without Meaning, 269 7.4 Evaluating Visualization Techniques, 2/>ng, 270 7.3.4 Borrowed Symbol, Different Meani 7.5 Techniques, 272 7.5.1 Textual Visualizations, 272 7.5.2 Informal Graphical EditorS, 274 7.5.3 UML: The Unified Modeling Language, 276 7.5.4 Rapide, 280 7.5.5 The Labeled Transition System Analyzer(Ltsa), 282 56xADL2.0,284 7.6 End Matter, 288 7.7 Review Questions, 289 7.8 Exercises, 290 7.9 Further Reading, 290 8 Analysis 291 8. 1 Analysis Goals, 295 8.1.1 Completeness, 295 8.1.2 Consistency, 296 8.1.3 Compatibility, 302 8. 1.4 Correctness, 303 8.2 Scope of analysis, 303 8.2.1 Component-and Connector- Level Analysis, 304 8.2.2 Subsystem- and System-Level Analysis, 305 8.2.3 Data Exchanged in the System or Subsystem, 307 8.2.4 Architectures at Different Abstraction Levels, 308 8.2.5 Comparison of Two or More Architectures, 310 8.3 Architectural Concern being analyzed, 310 8. 4 Level of formality of Architectural Models, 312 8.5 Type of analysis, 313 8.6 Level of Automation, 314 8.7 System Stakeholders, 315 8.8 Analysis Techniques, 317 8.8.1 Inspections and reviews, 317 8.8.2 Model-Based Analysis, 322 8.8.3 Simulation- Based Analysis, 328 8.9 End matter, 333 8.10 Review Questions, 334 CONTENTS 8. 11 Exercises, 335 8.12 Further Reading; 336 9 Implementation 337 9.1 Concepts, 338 9.1.1 The Mapping Problem, 338 9.1.2 Architecture Implementation Frameworks, 340 9. 1.3 Evaluating Frameworks, 343 9.1.4 Middleware, Component Models, and Application Frameworks, 343 9.1.5 Building a New framework, 346 9.1.6 Concurrency 347 9.1.7 Generative Technologies, 348 9.1.8 Ensuring Architecture-to-Implementation Consistency, 349 9.2 Existing Frameworks, 350 9. 2. 1 Frameworks for the Pipe-and-Filter Architectural Style, 350 9.2.2 Frameworks for the C2 Architectural Style, 352 9.3 Examples, 360 9.3. 1 Implementing Lunar Lander in the Pipe-and-Filter Style Using the java. io Framework, 360 9.3.2 Implementing lunar lander in the c2 Style using the Lightweight C2 Framework, 366 9.4 End Matter, 377 9.5 Review questions, 378 9.6 Exercises, 378 9.7 Further reading, 379 10 Deployment and Mobility 38 10. 1 Overview of Deployment and Mobility Challenges, 385 10.2 Software Architecture and Deployment, 387 10.2.1 Basic ts,388 10.2.2 Deployment activities, 388 10.2. 3 Tool Su 402 10.3 Software Architecture and Mobility, 405 10.3.1 Basic Concepts, 405 10.3.2 Mobil Pa ity paradigms, 405 10.3.3 Challenges in Migrating Code, 406 10.4 End Matter, 408 10.5 Review Questions, 409 10.6E 40 10.7 Further Reading, 410 Applied Architectures and Styles 4B3 11.1 Distributed and Networked Architectures, 414 11.1.1 Limitations of the distributed Systems viewpoint, 415 11.2 Architectures for Network-Based Applications, 416 【实例截图】
【核心代码】