Software architects' experiences of quality requirements: what we know and what we do not know?
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
A persona-based approach for exploring architecturally significant requirements in agile projects
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Software quality across borders: Three case studies on company internal alignment
Information and Software Technology
| Hi-index | 0.00 |
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 that NFRs have on daily architects' practices. This paper presents some of the findings of an empirical study based on 13 interviews with software architects. It addresses questions such as: who decides the NFRs, what types of NFRs matter to architects, how are NFRs documented, and how are NFRs validated. The results are contextualized with existing previous work.