|
| 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
| ASCII Text | x | ||
| 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. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2012.176, author = {David Ameller and Claudia Ayala and Jordi Cabot and Xavier Franch}, title = {Non-functional Requirements in Architectural Decision Making}, journal ={IEEE Software}, volume = {30}, number = {2}, issn = {0740-7459}, year = {2013}, pages = {61-67}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2012.176}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Non-functional Requirements in Architectural Decision Making IS - 2 SN - 0740-7459 SP61 EP67 EPD - 61-67 A1 - David Ameller, A1 - Claudia Ayala, A1 - Jordi Cabot, A1 - Xavier Franch, PY - 2013 KW - Software KW - Interviews KW - Companies KW - Documentation KW - Educational institutions KW - Decision making KW - software architecturecontent type KW - nonfunctional requirements KW - non-functional requirements KW - NFR KW - quality requirements KW - architectural decisions KW - software engineering VL - 30 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2012.176
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.