Requirements engineering in the year 00: a research perspective

By Axel van Lamsweerde. Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium, 2000

860 citations recorded by the source corpus.

How researchers see this paper

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

Research Directions in Requirements Engineering (2007, background): “As such, there are many more options to consider and decisions to make about requirements, such as selecting from collections of proposed requirements, prioritizing requirements, deciding on the system boundaries, negotiating resolutions to conflicts, setting objective acceptance criteria, and so on”
Elaborating security requirements by construction of intentional anti-models (2004, methodology): “Our method builds on a goal-oriented framework we developed before for generating and resolving obstacles to requirements achievement [21, 22].”
Goal-oriented requirements engineering: a guided tour (2001, methodology): “We follow the KAOS method [Dar93, Lam95, Lam00c ] in order to incrementally elaborate four complementary submodels: (1) the goal model, (2) the object model; (3) the agent responsibility model, leading to alternative system boundaries; (4) the operation model.”
Requirements Evolution from Process to Product Oriented Management (2001, background): “Despite this Requirements Evolution [1, 2, 10, 11, 18, 23] still remains one of the most critical issues for software organizations and is challenging for research and practice in Requirements Engineering [14, 25].”