A new, quantitative architecture simulation approach to software design that circumvents costly testing cycles by modeling quality of service in early design states.

Too often, software designers lack an understanding of the effect of design decisions on such quality attributes as performance and reliability. This necessitates costly trial-and-error testing cycles, delaying or complicating rollout. This book presents a new, quantitative architecture simulation approach to software design, which allows software engineers to model quality of service in early design stages. It presents the first simulator for software architectures, Palladio, and shows students and professionals how to model reusable, parametrized components and configured, deployed systems in order to analyze service attributes.

The text details the key concepts of Palladio's domain-specific modeling language for software architecture quality and presents the corresponding development stage. It describes how quality information can be used to calibrate architecture models from which detailed simulation models are automatically derived for quality predictions. Readers will learn how to approach systematically questions about scalability, hardware resources, and efficiency. The text features a running example to illustrate tasks and methods as well as three case studies from industry. Each chapter ends with exercises, suggestions for further reading, and “takeaways” that summarize the key points of the chapter. The simulator can be downloaded from a companion website, which offers additional material. The book can be used in graduate courses on software architecture, quality engineering, or performance engineering. It will also be an essential resource for software architects and software engineers and for practitioners who want to apply Palladio in industrial settings.

The 2010 Symposium on Component-Based Software Engineering (CBSE 2010) was the 13th in a series of successful events that have grown into the main forum for industrial and academic experts to discuss component technology. CBSE is concerned with the development of software-intensive systems from - dependently developed software-building blocks (components), the development of components, and system maintenance and improvement by means of com- nent replacement and customization. The aim of the conference is to promote a science and technology foundation for achieving predictable quality in software systems through the use of software component technology and its associated software engineering practices. In line with a broad interest, CBSE 2010 received 48 submissions. From these submissions, 14 were accepted after a careful peer-review process followed by an online program committee discussion. This resulted in an acceptance rate of 29%. The selected technical papers are published in this volume. For the fourth time, CBSE 2010 was held as part of the conference series: Fed- ated Events on Component-Based Software Engineering and Software Archit- ture (COMPARCH). The federated events were: the 13th International S- posium on Component-Based Software Engineering (CBSE 2010), the 6th - ternational Conference on the Quality of Software Architectures (QoSA 2010), andthe1stInternationalSymposium onArchitecting CriticalSystems(ISARCS 2010). Together with COMPARCH’s Industrial Experience Report Track and the co-located Workshop on Component-Oriented Programming (WCOP 2010), COMPARCH provided a broad spectrum of events related to components and architectures.
Models are used in all kinds of engineering disciplines to abstract from the various details of the modelled entity in order to focus on a speci?c aspect. Like a blueprint in civil engineering, a software architecture providesan abstraction from the full software system’s complexity. It allows software designers to get an overview on the system underdevelopmentandtoanalyzeitsproperties.Inthissense,modelsarethefoundation needed for software development to become a true engineering discipline. Especially when reasoning on a software system’s extra-functional properties, its software architecture carries the necessary information for early, design-time analyses. These analyses take the software architecture as input and can be used to direct the design process by allowing a systematic evaluation of different design alternatives. For example, they can be used to cancel out decisions which would lead to architecture - signs whose implementation would not comply with extra-functionalrequirements like performance or reliability constraints. Besides such quality attributes directly visible to the end user, internal quality attributes, e.g., maintainability, also highly depend on the system’s architecture. In addition to the above-mentioned technical aspects of software architecture m- els, non-technical aspects, especially project management-related activities, require an explicit software architecture model. The models are used as input for cost esti- tions, time-, deadline-, and resource planning for the development teams. They serve the project management activities of planning, executing, and controlling, which are necessary to deliver high-quality software systems in time and within the budget.
©2019 GoogleSite Terms of ServicePrivacyDevelopersArtistsAbout Google|Location: United StatesLanguage: English (United States)
By purchasing this item, you are transacting with Google Payments and agreeing to the Google Payments Terms of Service and Privacy Notice.