Quality Of Software Architectures Models And Architectures
Download Quality Of Software Architectures Models And Architectures PDF/ePub or read online books in Mobi eBooks. Click Download or Read Online button to get Quality Of Software Architectures Models And Architectures book now. This website allows unlimited access to, at the time of writing, more than 1.5 million titles, including hundreds of thousands of titles in various foreign languages.
Quality of Software Architectures Models and Architectures
Author: Steffen Becker
language: en
Publisher: Springer Science & Business Media
Release Date: 2008-10-07
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.
Quality of Software Architectures and Software Quality
This book constitutes the joint refereed proceedings of two colocated events: the First International Conference on the Quality of Software Architectures (QoSA 2005) and the Second International Workshop on Software Quality (SOQUA 2005) held in Erfurt, Germany, in September 2005. The 18 revised full papers presented were carefully reviewed and selected from 48 submissions. For QoSA 2005 only 12 papers - of the 31 submitted - were accepted for presentation; they are concerned with research and experiences that investigate the influence a specific software architecture has on software quality aspects. The papers are organized in topical sections on software architecture evaluation, formal approaches to model-driven QoS-handling, modelling QoS in software architectures, software architectures applied, architectural design for QoS, and model-driven software reliability estimation. The 6 papers accepted for SOQUA 2005 - from 17 submissions - mainly focus on quality assurance and on software testing. They are organized in topical sections on test case selection, model-based testing, unit testing, and performance testing.
Quality of Software Architectures Models 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.