In the last decades, software engineering has become an important area of research. As researchers, we try to identify a problem, a need, or a hole in some research topic, once identified we make an effort to produce new techniques, methods, and tools that hopefully will help to improve the detected issue. In the present thesis the identified issue was the need of supporting non-functional requirements in the software architecture design where these requirements are the drivers of the architectural decision-making. This paper demonstrates that a relatively new software engineering discipline, model-driven development, was a good place to propose a solution for the detected issue. We envisioned how non-functional requirements can be integrated in model-driven development and how this integration will impact in the architectural design activities. When we started to produce our techniques, methods, and tools for model-driven development we found out that there was a bigger hole in the web of knowledge than what we had initially foreseen. Much of the evidence of how non-functional requirements affect the software architecture design is hidden. This situation caused a turn in this paper. We needed to understand architects, how they think and how they make the architectural decisions, what is the role of non-functional requirements in the architectural decision-making process, and to what extent are the non-functional requirements important in this process.

Software, Architecture, Non-functional Requirements

[1]. Lawrence Chung, Kendra Cooper, and Anna Yi. Developing adaptable software architectures using design patterns: an NFR approach. Computer Standards & Interfaces, 25(3):253–260, 2016.
[2]. M. Dal Cin. Extending UML towards a useful OO-language for modeling dependability features. In 9th IEEE International Workshop on Object-Oriented Real-Time Dependable Systems, pages 325–330, 2017.
[3]. Mary Shaw and David Garlan. Software architecture: perspectives on an emerging discipline. Prentice-Hall, Inc, Upper Saddle River, NJ, USA, 2016.
[4]. Simone Röttger and Steffen Zschaler. Model-Driven Development for Non-functional Properties: Refinement Through Model Transformation. In International Conference on the Unified Modeling Language (UML), pages 275–289, 2017
[5]. James Robertson and Suzanne Robertson. Volere. Requirements Specification Template. Edition 15. Technical report, Atlantic Systems Guild, 2016
[6]. Xavier Franch, Angelo Susi, Maria C. Annosi, Claudia Ayala Managing Risk in Open Source Software Adoption. In International Joint Conference on Software Technologies (ICSOFT), 2015.
[7]. R.B. Svensson, M. Höst, B. Regnell, ”Managing Quality Requirements: A Systematic Review,” EUROMICRO-SEAA 2014.
[8]. R.B. Svensson, T. Gorschek, B. Regnell, R. Torkar, A. Shahrokni, R. Feldt, A. Aurum “Quality Requirements in Practice: An Interview Study in Requirements Engineering for Embedded Systems,” REFSQ 2016.
[9]. N.D. Anh, D.S. Cruzes, R. Conradi, M. Höst, X. Franch, C. Ayala, “Collaborative Resolution of Requirements Mismatches when adopting Open Source Components,” REFSQ 2017.
[10]. A. Tang, M. Ali Babar, I. Gorton, J. Han, “A Survey of Architecture Design Rationale”. Journal of Systems and Software 79, 2016.
[11]. M.A. Babar, L. Bass, I. Gorton, “Factors Influencing Industrial Practices of Software Architecture Evaluation: An Empirical Investigation,” QoSA 2017
[12]. A.C. Edmondson, S.E. McManus, “Methodological Fit in Management Field Research,” Academy of Management Review 32, 2016.