Architectures for Adaptive Software Systems: 5th International Conference on the Quality of Software Architectures, QoSA 2009, East Stroudsburg, PA, USA, ... Programming and Software Engineering)

This book constitutes the thoroughly refereed proceedings of the 5th International Conference on the Quality of Software Architectures, QoSA 2009, held in East Stroudsbury, PA, USA in June 2009, in conjunction with the 12th International Symposium on Component Based Software Engineering (CBSE 2009). The 13 revised full papers were carefully reviewed and selected from 33 submissions. The papers are organized in topical sections on model-driven quality analysis, architectural performance prediction, architectural knowledge, as well as case studies and experience reports. front-matter.pdf......Page 1 Introduction......Page 10 Comparison of Debugging Processes......Page 11 CALICO Autonomic Control Loop......Page 13 CALICO Metamodels to Support Autonomic Systems......Page 14 QoS Metamodel......Page 15 Link between QoS Specification and QoS Sensors......Page 16 Adaptation Metamodel......Page 17 Application Loader Tool......Page 19 Implementation Status......Page 20 Evaluation......Page 21 Related Work......Page 23 References......Page 25 Introduction......Page 27 Overview of a Real-Time Component Middleware......Page 29 Inherent and Accidental Complexities in Deployment and Configuration......Page 30 Enhancing the Quality of DRE System Software Architectures......Page 31 Representative Case Study......Page 32 Heuristics-Based Model-Transformation Algorithm......Page 33 Resolving the Challenges in Optimizing QoS Configurations......Page 36 Experimental Setup and Empirical Results......Page 37 Discussion......Page 38 Related Work......Page 39 Concluding Remarks......Page 41 References......Page 42 Introduction......Page 45 Terms and Technology......Page 46 Approach......Page 48 Analysis Graph Extraction......Page 49 Analysis Graph Completion by Clustering......Page 52 Check Consistency Rules......Page 54 Matrix Framework......Page 55 Results and Interpretation......Page 56 Related Work......Page 57 Conclusion......Page 58 References......Page 59 Introduction......Page 61 Related Work......Page 63 Software Cartography......Page 64 Software Performance Prediction and Visualization......Page 65 Chosen Visualizations in the New Approach......Page 67 Applying the Software Cartography Approach to Visualizing Performance Information......Page 69 Evaluation......Page 71 Scenarios: Performance Design Decisions......Page 72 Phase 1 Results......Page 74 Phase 2 Results......Page 75 References......Page 76 Introduction......Page 79 Model Evolution with KAMI......Page 81 Introduction to Queueing Networks......Page 83 Queueing Networks for Open Systems......Page 85 Parameter Estimation and Run-Time Update......Page 86 A Running Example......Page 87 Related Work......Page 91 Conclusion and Future Work......Page 92 References......Page 93 Introduction......Page 95 Process Control Architectures......Page 96 Formal Semantics......Page 98 Compositional Semantics......Page 100 Grey-Box Components......Page 101 Black-Box Components......Page 103 Component Deployment......Page 105 Parametrized and Compositonal Verification......Page 107 Related Work and Conclusions......Page 108 References......Page 109 Introduction......Page 110 The Production Cell - a Running Example......Page 111 The Architecture Analysis and Design Language......Page 112 The Timed Abstract State Machines......Page 113 The AADL Behavior Annex Extension......Page 114 Translation Semantics......Page 115 Tool Support......Page 118 Simulation......Page 119 Related Work......Page 121 Conclusions and Further Work......Page 122 References......Page 123 Introduction......Page 125 IT Infrastructure......Page 127 Preliminary Research and Tool Selection......Page 128 Refactoring the Architecture......Page 130 Maintaining Visibility......Page 135 Lessons Learned......Page 136 References......Page 137 Introduction......Page 139 State of AK Sharing Practice......Page 140 AK Practices in Context......Page 145 Refined Model of Causality......Page 149 Threats to Validity......Page 151 Motivation and Emotion in Architectural Knowledge Sharing......Page 152 Conclusions......Page 153 References......Page 154 Introduction......Page 155 Definition......Page 156 Related Work......Page 157 Systems under Discussion......Page 158 Grid Architecture Recovery......Page 159 MIDAS Architecture Refactoring......Page 160 Connector Envy......Page 161 Scattered Parasitic Functionality......Page 164 Ambiguous Interfaces......Page 165 Extraneous Adjacent Connector......Page 167 Conclusion......Page 169 References......Page 170 Introduction......Page 172 Related Work......Page 173 Data-Center Description......Page 174 QN Model......Page 176 Formulation and Algorithm......Page 178 Formulation of the Consolidation Problem......Page 179 Heuristic Solution......Page 180 Minor Extensions......Page 181 Experimental Results......Page 182 Conclusions......Page 184 References......Page 185 Introduction......Page 186 The Challenge: Functional Overlap......Page 187 Systems under Study......Page 189 Application Domain......Page 190 Initial Architectures......Page 191 Extra-Functional Requirements......Page 192 Architecture Reconstruction and Documentation......Page 193 Extending a Remote Interface......Page 195 Designing a Product-Line Architecture......Page 196 Lessons Learned......Page 199 Conclusions......Page 200 References......Page 201 Introduction......Page 203 Common Component Architecture and Quantum Chemistry......Page 205 CQoS Infrastructure and Its Application in High-Performance Quantum Chemistry......Page 207 Training Data Collection for Scientific Components......Page 208 Database Components and Their Usage in Data Training......Page 209 Performance Analysis......Page 210 Adaptive Application Composition and Configuration......Page 212 MPQC......Page 213 GAMESS......Page 214 Conclusion and Future Work......Page 216 References......Page 218 back-matter.pdf......Page 221 Much of a software architect's life is spent designing software systems to meet a set of quality requirements. General software quality attributes include scalability, security, performance or reliability. Quality attribute requirements are part of an application's non-functional requirements, which capture the many facets of how the functional - quirements of an application are achieved. Understanding, modeling and continually evaluating quality attributes throughout a project lifecycle are all complex engineering tasks whichcontinuetochallengethe softwareengineeringscienti ccommunity. While we search for improved approaches, methods, formalisms and tools that are usable in practice and can scale to large systems, the complexity of the applications that the so- ware industry is challenged to build is ever increasing. Thus, as a research community, there is little opportunity for us to rest on our laurels, as our innovations that address new aspects of system complexity must be deployed and validated. To this end the 5th International Conference on the Quality of Software Archit- tures (QoSA) 2009 focused on architectures for adaptive software systems. Modern software systems must often recon guretheir structure and behavior to respond to c- tinuous changes in requirements and in their execution environment. In these settings, quality models are helpful at an architectural level to guide systematic model-driven software development strategies by evaluating the impact of competing architectural choices.