Abstract
[Context and motivation] Non-functional requirements (NFRs) play a fundamental role when software architects need to make informed decisions. Criteria like efficiency or integrity determine up to a great extent the final form that the logical, development and deployment architectural views take. [Question/problem] Continuous evidence is needed about the current industrial practices of software architects concerning NFRs: how do they consider them, and what are the most influential types in their daily work. [Principal ideas/results] We ran a web survey addressed to software architects about these issues. We got 60 responses that give some light to the questions above. [Contribution] Some empirical data has been gathered from industry. The results of this survey may serve as input for researchers in order to decide in which types of NFRs may be necessary to invest more research effort.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Ameller, D., Franch, X. (2010). How Do Software Architects Consider Non-Functional Requirements: A Survey. In: Wieringa, R., Persson, A. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2010. Lecture Notes in Computer Science, vol 6182. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-14192-8_25
Download citation
DOI: https://doi.org/10.1007/978-3-642-14192-8_25
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-14191-1
Online ISBN: 978-3-642-14192-8
eBook Packages: Computer ScienceComputer Science (R0)