Issue No. 02 - March-April (2013 vol. 30)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2012.176
David Ameller , BarcelonaTech—Universitat Politècnica de Catalunya
Claudia Ayala , BarcelonaTech—Universitat Politècnica de Catalunya
Jordi Cabot , École des Mines de Nantes
Xavier Franch , BarcelonaTech—Universitat Politècnica de Catalunya
Software architects often must work with incomplete or ill-specified non-functional requirements (NFRs) and use them to make decisions. Through this process, existing NFRs are refined or modified and new ones emerge. Although much research has centered on how software architects treat NFRs, no empirical studies have investigated the state of the practice. A survey based on interviews with 13 software architects addressed two fundamental issues: how do architects face NFRs from an engineering perspective, and how do NFRs influence their decision-making? The survey revealed that architects usually elicit NFRs themselves in an iterative process; they usually don't document the NFRs and only partially validate them.
Software, Interviews, Companies, Documentation, Educational institutions, Decision making, software architecturecontent type, nonfunctional requirements, non-functional requirements, NFR, quality requirements, architectural decisions, software engineering
C. Ayala, D. Ameller, J. Cabot and X. Franch, "Non-functional Requirements in Architectural Decision Making," in IEEE Software, vol. 30, no. , pp. 61-67, 2013.