A Software Architecture Evaluation Model

Abstract

Abstract:The fulfilment of quality requirements is fundamental for the success of software-intensive systems. This fact forces companies to quantify the quality requirements at the moment of their specification, and to evaluate these requirements in all the results of the design process, both the by-products and the end system. The definition of the software architecture is one of the most important and early decisions of the design process, with a strong influence on the final quality of the product; therefore its evaluation should be made as early as possible, before the design is complete. This paper presents a software architecture evaluation model considering the software architecture as a final product itself and also as an intermediate product of the design process.

A Semi-Automation of a Cost Benefit Analysis Method

“…Other methods for evaluating software architecture include: Software Architecture Analysis Method (SAAM) [5], Software Architecture Analysis Method Founded on Complex Scenarios (SAAMCS) [6], Software Architecture Analysis Method for Evolution and Reusability (SAAMER) [7], Scenario-Based Architecture Reengineering (SBAR) [8], Extending SAAM by Integration in the Domain (ESAAMI) [9], Architecture Level Prediction of Software Maintenance (ALPSM) [10] and Software Evaluation Model (SAEM) [11].…”

Evaluating reuse and program understanding in ArchMine architecture recovery approach

“…ArqCheck is a generic and simple approach for architecture evaluation as described in Section 4. Some architecture evaluation methods such as, for example, the ones based on scenarios -e.g., ATAM [19] and SAAM [17], although being systematic and already used in many contexts, may require great effort and can be more difficult to adapt, and others are specific to some architectural representations -e.g., SAEM [12]. Table 13 summarizes a comparison between ArchMine and some other meaningful architecture recovery approaches.…”

Scenario-based design and evaluation for capability

“…However, they differ significantly in their focus and the number of attributes employed. For example, while the Software Architecture Assessment Method (SAAM) [19] and its variants focus on singular quality attributes such as modifiability, flexibility, evolution and reusability other methods such as the Architecture Tradeoff Analysis Method (ATAM) [20], Scenario-Based Architecture Reengineering (SBAR) [21] and the Software Architecture Evaluation Model (SAEM) [22] include multiple attributes which contribute to a better understanding of the strengths and weaknesses of the overall architecture and its constituent parts. The selection of the most appropriate methods is dependent on the context in which the architecture is being evaluated and the quality attributes being addressed [16].…”