Non-functional Requirements in Architectural Decision Making

Ameller, David; Ayala, Claudia; Cabot, Jordi; Franch, Xavier

doi:10.1109/ms.2012.176

Cited by 60 publications

(42 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It has been recognized that there is a general mismatch between the theory on what should be practiced and the actual practice [14], [15], [16]. However, there is no consensus regarding the underlying reasons as to why such practices have not been widely adopted by the SE community 1 .…”

Section: Related Workmentioning

confidence: 99%

Sustainability design in requirements engineering

Chitchyan

Becker

Betz

et al. 2016

Proceedings of the 38th International Conference on Software Engineering Companion

View full text Add to dashboard Cite

Abstract-Sustainability is now a major concern in society, but there is little understanding of how it is perceived by software engineering professionals and how sustainability design can become an embedded part of software engineering process. This paper presents the results of a qualitative study exploring requirements engineering practitioners' perceptions and attitudes towards sustainability. It identifies obstacles and mitigation strategies regarding the application of sustainability design principles in daily work life. The results of this study reveal several factors that can prevent sustainability design from becoming a first class citizen in software engineering: software practitioners tend to have a narrow understanding of the concept of sustainability; organizations show limited awareness of its potential opportunities and benefits; and the norms in the discipline are not conducive to sustainable outcomes. These findings suggest the need for focused efforts in sustainability education, but also a need to rethink professional norms and practices.

show abstract

Section: Related Workmentioning

confidence: 99%

Sustainability design in requirements engineering

Chitchyan

Becker

Betz

et al. 2016

Proceedings of the 38th International Conference on Software Engineering Companion

View full text Add to dashboard Cite

show abstract

“…It is well accepted in the software architecture community that QAs are the most important drivers of architecture design [2]. Therefore, QAs should guide the selection of alternative software architectures from a model transformation process, considering the synergies and conflicts among them [5].…”

Section: Discussionmentioning

confidence: 99%

Exploring Quality-Aware Architectural Transformations at Run-Time: The ENIA Case

Criado

Martínez‐Fernández

Ameller

et al. 2016

Model and Data Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. Adapting software systems at run-time is a key issue, especially when these systems consist of components used as intermediary for human-computer interaction. In this sense, model transformation techniques have a widespread acceptance as a mechanism for adapting and evolving the software architecture of such systems. However, existing model transformations often focus on functional requirements, and quality attributes are only manually considered after the transformations are done. This paper aims to improve the quality of adaptations and evolutions in component-based software systems by taking into account quality attributes within the model transformation process. To this end, we present a quality-aware transformation process using software architecture metrics to select among many alternative model transformations. Such metrics evaluate the quality attributes of an architecture. We validate the presented quality-aware transformation process in ENIA, a geographic information system whose user interfaces are based on coarsegrained components and need to be adapted at run-time.

show abstract

“…Quality requirements (QRs; also known as Non-Functional Requirements) have often received little attention compared to functional requirements [1], even though empirical studies suggest otherwise (e.g., studies with software architects [2]). It has been argued that neglecting QRs is one of the top ten risks of requirements engineering [3].…”

Section: Motivationmentioning

confidence: 99%

Conflicts and Synergies among Quality Requirements

Boehm

Franch

2017

2017 IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C)

Self Cite

View full text Add to dashboard Cite

Abstract-Analyses of the interactions among quality requirements (QRs) have often found that optimizing on one QR will cause serious problems with other QRs. As just one relevant example, one large project had an Integrated Product Team optimize the system for Security. In doing so, it reduced its vulnerability profile by having a single-agent key distribution system and a single copy of the data base -only to have the Reliability engineers point on that these were system-critical single points of failure. The project's Security-optimized architecture also created conflicts with the system's Performance, Usability, and Modifiability. Of course, optimizing the system for Security had synergies with Reliability in having high levels of Confidentiality, Integrity, and Availability. This panel aims at fostering discussion on these relationships among QRs and how the use of data repositories may help discovering them.

show abstract

Non-functional Requirements in Architectural Decision Making

Cited by 60 publications

References 9 publications

Sustainability design in requirements engineering

Sustainability design in requirements engineering

Exploring Quality-Aware Architectural Transformations at Run-Time: The ENIA Case

Conflicts and Synergies among Quality Requirements

Contact Info

Product

Resources

About