Loading...
Loading...

Go to the content (press return)

How do software architects consider non-functional requirements: an exploratory study

Author
Ameller, D.; Ayala, C.P.; Jordi, C.; Franch, X.
Type of activity
Presentation of work at congresses
Name of edition
20th IEEE International Requirements Engineering Conference
Date of publication
2012
Presentation's date
2012-10-27
Book of congress proceedings
2012 20th IEEE Internationa Requirements Engineering Conference (RE)
First page
41
Last page
50
DOI
https://doi.org/10.1109/RE.2012.6345838 Open in new window
Repository
http://hdl.handle.net/2117/17830 Open in new window
Abstract
Dealing with non-functional requirements (NFRs) has posed a challenge onto software engineers for many years. Over the years, many methods and techniques have been proposed to improve their elicitation, documentation, and validation. Knowing more about the state of the practice on these topics may benefit both practitioners' and researchers' daily work. A few empirical studies have been conducted in the past, but none under the perspective of software architects, in spite of the great influence ...
Citation
Ameller, D. [et al.]. How do software architects consider non-functional requirements: an exploratory study. A: IEEE International Requirements Engineering Conference. "2012 20th IEEE Internationa Requirements Engineering Conference (RE)". Chicago: 2012, p. 41-50.
Group of research
GESSI - Group of Software and Service Engineering
inSSIDE - integrated Software, Service, Information and Data Engineering

Participants