Designing software architectures to achieve quality attribute requirements

Abstract

In order to have a software architecture design method that achieves quality attribute requirements several aspects of the method must be in place. First there must be some way to specify quality attribute requirements so that it can be determined whether the designed architecture can achieve them. Secondly, there must be some way for modularising the knowledge associated with quality attributes so that the design method does not need to know how to reason about all of the multiplicity of quality attributes that exist. Finally, there must be some way for managing the interactions among the quality attributes so that either the requirements can be satisfied or the ones that cannot be satisfied are identified. The authors describe a structure called a 'reasoning framework' as a modularisation of quality attribute knowledge. The requirements that the architecture must satisfy are specified as concrete quality attribute scenarios. Each reasoning framework provides mechanisms that will transform the architecture with respect to a given quality attribute theory. Within a reasoning framework, the authors distinguish between an architectural model and a quality attribute model and characterise the actions that a reasoning framework undertakes as basic architectural transformations. Finally, the process of identifying interactions among reasoning frameworks is begun so that conflicting requirements can be managed. The use of reasoning frameworks is situated inside an existing architectural design method so that a useful method exists while the open issues of designing to achieve quality attribute requirements are resolved.

Evaluation of the Software Architecture Styles from Maintainability Viewpoint

“…Therefore, the less is the amount of coupling and complexity of the components and the more their cohesion, the easier will be the analyzability, changeability, stability and testability of the software. Various researches emphasize the impact of complexity, cohesion of components and coupling among components metrics on software maintainability [15]- [18].…”

“…Therefore, in this paper, we use coupling, complexity and cohesion metrics to quantify the impact of SASs on software maintainability. These metrics are essential in evaluation of software design quality and their effects on maintainability have been extensively investigated [15]- [18].…”

Architecture consistency: State of the practice, challenges and requirements

“…Architecting software systems is an integral part of the software development lifecycle, providing a basis for achieving non-functional requirements (Bachmann et al 2005). However, even if the software architecture is well documented, designed and evaluated, the architecture must be embodied in the implementation to satisfy these requirements.…”

Exploring How the Attribute Driven Design Method Is Perceived

“…Bachman et al [1] describe steps for deriving architectural tactics. These steps include identifying candidate reasoning frameworks which include the mechanisms needed to use sound analytic theories to analyze the behavior of a system with respect to some quality attributes [2]. However, this involves that architects need to be familiar with formal specifications which are specific to quality models.…”