China
Africa
Explore chapters and articles related to this topic
Systematic Derivation and Evaluation of Domain-Specific and Implementation-Independent Software Architectures
Published in Roger H.L. Chiang, Keng Siau, Bill C. Hardgrave, Systems Analysis and Design, 2017
K. Suzanne Barber, Thomas Graser
The most prevalent overall architecture evaluation approaches are rooted in scenario-based methods such as the Software Architecture Analysis Method (SAAM) (Kazman et al., 1994) and the Architectural Tradeoff Analysis Method (ATAM) (Kazman et al., 1998; Lougee, 2005). The success of scenario-based approaches has led to the development of a number of related evaluation methods (Asundi, Kazman, and Klein, 2001; Bengtsson, 2002; Dobrica and Niemela, 2002; Tekinerdogan, 2004) as well as supporting tools (Benarif et al., 2004; Kazman, 1996). As evident by the name, ATAM considers multiple quality attributes and the tradeoffs between those attributes. The assumption is that attribute-specific analyses are interdependent, since attributes connect to other attributes through specific architectural elements (e.g., a property of a component), leading to tradeoffs (Kazman et al., 1998). RARE recognizes such inherent conflicts among quality goals (manifested through a given DRA structure, which promotes some attributes while inhibiting others), and the RARE approach allows the architect to establish goal priorities, so RARE can make sensible tradeoffs when conflicts arise.
GearWheels: A Software Tool to Support User Experiments on Gesture Input with Wearable Devices
Published in International Journal of Human–Computer Interaction, 2022
Ovidiu-Andrei Schipor, Radu-Daniel Vatavu
Designing software architecture is a process that often starts with the identification of the quality attributes that the final system must meet (Evesti, 2007). Some approaches consider quality attributes subsumed to concrete usage scenarios (Folmer et al., 2005), such as the Software Architecture Analysis Method (Kazman et al., 1994), or to external constraints, such as the Architecture-Based Component composition/Decision-oriented Design (Cui et al., 2009). In this work, we employ the Software Product Quality Model from SQuaRE, the Systems and Software Quality Requirements and Evaluation ISO/IEC standard (International Organization for Standardization, 2005), from which we select nine quality properties directly relevant for GearWheels; see Figure 1 for a visual illustration. In the following, we group these properties into three categories according to the interactions that they enable among software modules, components, and between users and GearWheels.