A paper that is cited very often and gives a good overview is the following:

L. Chung and J. C. S. do Prado Leite, “On Non-Functional Requirements in Software Engineering,” in Conceptual Modeling: Foundations and Applications, vol. 5600, A. Borgida, V. Chaudhri, P. Giorgini, and E. Yu, Eds. Springer Berlin / Heidelberg, 2009, pp. 363–379.

The URML (part of my work) supports modeling non-functional requirements.

I'd suggest adding the topic "Requirements Engineering", so that this question will gain visibility among RE researchers.

Thanks, Florain.

I think the topic "Requirements Engineering" is too broad to discuss. The following is a book chapter discussing NFRs and has a nice list of references.

http://pdf.aminer.org/000/307/302/functional_and_non_functional_application_software_requirements_early_conflict_detection.pdf

Another nice book The Quest for Software Requirements is a handbook of probing questions for eliciting nonfunctional requirements, as well as, proven techniques and tips for engaging the right stakeholders. (Roxanne Miller, MavenMark Books, 2009).

Hope this help.

Dear, from my perspective, a differentiation is needed: You surely address non-functional requirements (NFRs) at development level, not at organizational level as described by Cremers, A.B., Alda, S.: Organizational requirements engineering (chapter 9). http://www.iai.uni-bonn.de/III/lehre/vorlesungen/SWT/RE05/slides/09 Non- functional%20Requirements.pdf (2010) -- There NFRs at organizational/management level .. For development NFRs in addition to classical books by Sommerville etc. : Glinz, M.: On non-functional requirements. Volume 0., Los Alamitos, CA, USA, IEEE Computer Society (2007) 21–26 or Paech, B., Dutoit, A.H., Kerkow, D., Knethen, A.V.: Functional requirements, non-functional requirements, and architecture should not be separated -a position paper. Technical report, Proceedings of the International Workshop on Requirements Engineering: Foundations for Software Quality (2002) .. I address in my AFFINE related publications NFRs when building socio-technical systems following Scrum or Agile in general .. AFFINE is Agile Framework For Integration Nonfunctional requirements Engineering: Bourimi, M., Barth, T., Haake, J.M., Ueberscha ̈r, B., Kesdogan, D.: AFFINE for enforcing earlier consideration of NFRs and human factors when building socio- technical systems following agile methodologies. In: Proceedings of the Third in- ternational conference on Human-centred software engineering. HCSE’10, Berlin, Heidelberg, Springer-Verlag (2010) 182–189 .. Eric Yu, If you want to get insight in my last paper just contact me "Bourimi, M., Kesdogan, D.: Experiences by using AFFINE for building collabo- rative applications for online communities. In: HCI International 2013. HCII ’13 (2013) to appear."

The classical work of Eric Yu, Chung and Nixon is the NFR book http://www.utdallas.edu/~chung/BOOK/book.html .. Here one have to differentiate about the focus in my opinion, they focus on business processes and architectures and how NFRs can be handled there .. Such systems follow rigid workflows (i.e. banking, industrial safety or security software etc.) .. In my case, I address socio-technical systems such as Social Networking and Media software which is being built today following agile methodologies because of end-user focus and uncertainties in respect: which trend they will take and how to react on changes in the respective applications etc.

Have you looked at the attempts by Sommerville et al. to use ethnography to enrich the elicitation process? We are exploring the use of the Appreciative Inquiry Method (AIM) which is based upon the work of Geoffrey Vickers (appreciation and 'appreciative systems') and uses Soft Systems Methodology-type models for exploring and making explicit non-functional requirements.

You may use this taxonomy which is built on clear purposes and provides unambiguous answers.

http://caminao.wordpress.com/how-to-implement-symbolic-representations/requirements/requirements-taxonomy/

I suggest taking a look at material from the Software Engineering Institute at Carnegie Mellon, which has excellent guidance pertinent to Non Functional Requirements and the field of Software Architecture. circa 2008, though some of the original ideas are from the late 1990s. I have found it to be invaluable and effective for system design over the last few years.