Essentially a software system's utility is determined by both its functionality and its non-
functional characteristics, such as usability, flexibility, performance, interoperability and …

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 commonly distinguished from functional
requirements by differentiating how the system shall do something in contrast to what the …

Non-Functional Requirements in Software Engineering presents a systematic and pragmatic
approach tobuilding quality into'software systems. Systems must exhibit software quality …

The purpose of this paper is to review the state-of-the-art in the engineering of NFR, and to
define an agenda for future NFR research. Therefore we define the requirements on a NFR …

Requirements standards and textbooks typically classify requirements into functional
requirements on the one hand and attributes or non-functional requirements on the other …

Software developers are constantly under pressure to deliver code on time and on budget.
As a result, many projects focus on delivering functionalities at the expense of meeting non …

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 …

Nonfunctional requirements (NFRs) have been frequently neglected or forgotten in software
design. They have been presented as a second or even third class type of requirement …

The way requirements should drive the rest of the software development process has been a
subject of many research projects in the past. Unfortunately, all of them focus primarily, when …