Using Informal Knowledge for Improving Software Quality Trade-Off Decisions

DD-KARB: Data-Driven Compliance to Quality by Rule Based Benchmarking

“…a conceptquantized de nition of qualities. Hence, a quanti cation of qualities (which is a well-known but poorlyachieved goal for rigorous software engineering [121]) helps measure and perceive the true level of qualities in each application.…”

“…This view let us create an explicitly defined conceptual construction for Qualities: a concept-quantized definition for qualities. So a quantification of qualities (which is a well-known but poorly-achieved goal for rigorous software engineering [95]) helps to measure and understand the true level of qualities in each software.…”

Quality attributes use in architecture design decision methods: research and practice

“…Software and Systems Modeling Schneider et al [36] Extension of Palladio and PerOpteryx ECSA Table 1: List of papers included in the systematic literature review. The selected papers are listed along with the publication year and venue as well as the name of the method or tool used for architecture decision making and documentation.…”

“…Calculation of trade-offs is considered as MCDM problem (use of TOPSIS techique) Schneider et al [36] Automatic Calculation of Pareto-optimal results Kishi et al [1] design decisions Case Study: on-board system for ITS systems Bachmann et al [3] > tactics Garage Door Example Chung et al [4] 3 patterns and 6 tactics Example: Home Appliance Controller Svahnberg et al [5] 3 alternative architectures Case study with Swedish company Al-Naeem et al [6] 19 design decisions Case study: Glass Box project Choi et al [7] 8 design decisions Example: House Alarm System Tibermacine et al [8] 6 design decisions Motivating example: Museum Access Control System -Tested tool with industrial project Zdun [11] Pattern language on distributed object middleware (<10 design patterns)…”

“…Example Case Study: Remoting patterns -asynchronous invocation patterns. Evaluation with 4 industrial case studies Zimmermann et al [12] 160 SOA decisions Web services projects Babar and Capilla [13] Not indicated Airborne Mission Systems Cui et al [14] 48 potential decisions Case Study: Commanding Display System Makki et al [15] Not indicated Case Study: Garage Door Example Zimmermann et al [16] 300 SOA design decisions Case Study from the finance industry de Boer et al [17] 11 design decisions Example: fictional HRM system Bode and Riebisch [18] 15 architectural patterns Case Study: Collective Ordering System Alebrahim et al [20] Not indicated Case Study: Chat application Kassab et al [21] 4 architectural styles considered Not indicated Dermeval et al [22] 2 alternatives (MVC vs Layers) for the architecture of a component Case study in service-based platform integration Sedaghatbaf and Abdollahi Azgomi [35] 9 decision points considered for the architectural model in total Case study on a building surveillance (BS) system Schneider et al [36] 22 and 9 Pareto-optimal architecture candidates for Case Study 1 and 2 respectively.…”