Goal-oriented requirements engineering: a guided tour

By Axel van Lamsweerde. Proceedings Fifth IEEE International Symposium on Requirements Engineering, 2001

2,090 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/4699649d2d099f4a082ec8903a9a80ca6a73648b

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

In Information Systems

In Software

Citations in the corpus

Early aspects: a model for aspect-oriented requirements engineering (2002, methodology): “We can use: goal-oriented requirements which cover functional and non-functional concerns [10]; use cases or scenario-based approaches, by specifying which use cases/scenarios are crosscut by a concern; problem frames which can be viewed as concerns [8].”
A survey of traceability in requirements engineering and model-driven development (2010, background): “This development is twofold: On the one hand, there are semantic models such as goal models [185] or business object models which are used to express and relate domain concepts and which can—at least partially—replace natural language descriptions.”
Reasoning about partial goal satisfaction for requirements and design engineering (2004, background): “A goal is a prescriptive statement of intent whose satisfaction in general requires the cooperation of some of the agents forming the system [18].”
Security Requirements Engineering: A Framework for Representation and Analysis (2008, methodology): “6.3 Constructing Inner Arguments One question that arises is “how does the analyst find rebuttals, grounds, and warrants?” We cannot propose a recipe, but did find useful a method inspired by the how/ why questions used in goal-oriented requirements engineering methods (e.g., KAOS [ 47 ]).”
Nonfunctional requirements: from elicitation to conceptual models (2004, background): “Only recently, research results are showing ways of dealing with NFRs [10], [14], [40] at the software definition level.”
Elaborating security requirements by construction of intentional anti-models (2004, methodology): “Our approach extends the KAOS framework for goaloriented requirements engineering [11, 22, 23 ] in several ways:”
Self-Managed Systems: an Architectural Challenge (2007, background): “It is likely that the refinement of very high-level goals to precisely specified goals that can be processed by machines will require human assistance as is current practice in goal oriented requirements engineering [38].”
On Non-Functional Requirements in Software Engineering (2009, background): “Thanks to their formal nature, representations in KAOS are amenable to automatic verification and reasoning.”
Internet of Things (IoT) Cybersecurity Research: A Review of Current Research Topics (2019, background): “Many mechanisms have been proposed to address data privacy issues in IoT cybersecurity, such as Kaos [95], Tropos [96], NFR [97], GBRAM [98], and PRIS [99].”
Research Directions in Requirements Engineering (2007, background): “Notations Goals [18, 150] Policies [17] Scenarios [2, 31, 41] Enterprise models [45] Logics [47] Model checking [19, 48]”
Model-based development of dynamically adaptive software (2006, background): “Assume we are given a problem in terms of a set of highlevel goals [21, 22 ] and a set of execution domains D .W e are required to develop an adaptive program to solve the problem, i.e., to achieve the high-level goals, when the inputs of the program change their domains in D at run time.”