This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Non-functional Requirements in Architectural Decision Making
March-April 2013 (vol. 30 no. 2)
pp. 61-67
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.
Index Terms:
Software,Interviews,Companies,Documentation,Educational institutions,Decision making,software architecturecontent type,nonfunctional requirements,non-functional requirements,NFR,quality requirements,architectural decisions,software engineering
Citation:
David Ameller, Claudia Ayala, Jordi Cabot, Xavier Franch, "Non-functional Requirements in Architectural Decision Making," IEEE Software, vol. 30, no. 2, pp. 61-67, March-April 2013, doi:10.1109/MS.2012.176
Usage of this product signifies your acceptance of the Terms of Use.