Applications Strategies for Risk Analysis
Applications Strategies for Risk Analysis
Five Ways to Destroy a Development Project
IEEE Software
Contemporary Application-Domain Taxonomies
IEEE Software
Identifying Quality-Requirement Conflicts
IEEE Software
Software Requirements: Styles and Techniques
Software Requirements: Styles and Techniques
A comedy of errors: the London Ambulance Service case study
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Software Requirements
Conflict identification and resolution for software attribute requirements
Conflict identification and resolution for software attribute requirements
Software Engineering (7th Edition)
Software Engineering (7th Edition)
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
Goal-centric traceability for managing non-functional requirements
Proceedings of the 27th international conference on Software engineering
Proceedings of the 16th International Software Product Line Conference - Volume 1
Parameters for service level agreements generation in cloud computing: a client-centric vision
ER'12 Proceedings of the 2012 international conference on Advances in Conceptual Modeling
Optimal selection of operationalizations for non-functional requirements
APCCM '13 Proceedings of the Ninth Asia-Pacific Conference on Conceptual Modelling - Volume 143
A framework for prioritization of quality requirements for inclusion in a software project
Software Quality Control
Hi-index | 0.00 |
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 general consensus in the software engineering community regarding the notion of NFRs. This paper presents the result of an extensive and systematic analysis of the extant literature over three NFRs dimensions: (1) definition and terminology; (2) types; and (3) relevant NFRs in various types of systems and application domains. Two different perspectives to consider NFRs are described. A comprehensive catalogue of NFRs types as well as the top five NFRs that are frequently considered are presented. This paper also offers a novel classification of NFRs based on types of systems and application domains. This classification could assist software developers in identifying which NFRs are important in a particular application domain and for specific systems.