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 …

Abstract [Context and motivation] Non-functional requirements (NFRs) play a fundamental
role when software architects need to make informed decisions. Criteria like efficiency or …

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 …

This paper presents the analysis and key findings of a survey about dealing with non-
functional requirements (NFRs) among architects. We find that, as long as the architect is …

Even though non-functional requirements (NFRs) are critical in order to provide software of
good quality, the literature of NFRs is relatively sparse. We describe how NFRs are treated …

Although Non-Functional Requirements (NFRs) are recognized as very important
contributors to the success of software projects, studies to date indicate that there is still no …

Non-Functional Requirements (NFRs) are rarely treated as “first-class” elements in software
development as Functional Requirements (FRs) are. Often NFRs are stated informally and …

Abstract Non-Functional Requirements (NFRs) are recognized as a critical factor to the
success of software projects because they address the essential issue of software quality …

Non-functional requirements (NFRs) are determinant for the success of software projects.
However, they are characterized as hard to define, and in agile software development …

Abstractâ Non-functional requirements (NFRs) tend to interfere, conflict, and contradict with
one other. Unlike functional requirements, this inevitable conflict arises as a result of …