Non-Functional Requirements in Software Engineering

By Lawrence Chung, B. Nixon, E. Yu, John Mylopoulos. International Series in Software Engineering, 2000

927 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Information Systems, Management Information Systems

View Paper: https://www.semanticscholar.org/paper/5a30fd3718835c500d1833492d6cd833c959d155

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

1. Julio Cesar Sampaio do Prado Leite
2. Lawrence Chung
3. Robin C. Laney
4. Charles B. Haley
5. Jonathan D. Moffett
6. Joanne M. Atlee
7. Mark Harman
8. Bashar Nuseibeh

In Information Systems

1. Julio Cesar Sampaio do Prado Leite
2. Lawrence Chung
3. Robin C. Laney
4. Charles B. Haley
5. Jonathan D. Moffett
6. Jie M. Zhang
7. Yang Liu
8. Lei Ma

In Management Information Systems

1. Julio Cesar Sampaio do Prado Leite
2. Lawrence Chung

Citations in the corpus

• Research Directions in Requirements Engineering (2007, background): “In addition, significant advances have been made in the modeling and analysis of nonfunctional requirements [28] and in establishing objective fit criteria for how well an eventual system must achieve various nonfunctional properties [69].”
• Security Requirements Engineering: A Framework for Representation and Analysis (2008, background): “Security needs arise when stakeholders establish that some resource involved in a system, be it tangible (e.g., cash) or intangible (e.g., information or reputation), is of value to the organization.”
• On Non-Functional Requirements in Software Engineering (2009, methodology): “Another proposal is made in [15], using the concepts of the NFR Framework [3], on a classification of goals and softgoals, driven by the “non functional perspective”.”
• Evaluating goal models within the goal‐oriented requirement language (2010, background): “(5) ServiceInSCPDataInSNnotReady: The service logic is in the SCP and the data in the SN, but the vendor cannot supply new SN.”
• NoFunEval: Funny How Code LMs Falter on Requirements Beyond Functional Correctness (2024, background): “Such non-functional requirements guide the design decisions and constrain how the functionality may be realized (Landes & Studer, 1995), and play a central role in real-world software engineering (Chung et al., 2012).”
• Machine Learning Testing: Survey, Landscapes and Horizons (2019, methodology): “3 we adopt the more general understanding from software engineering community [49], [50], and regard robustness as a non-functional requirement.”