Elaborating security requirements by construction of intentional anti-models

By Axel van Lamsweerde. Proceedings. 26th International Conference on Software Engineering, 2004

477 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.

Security Requirements Engineering: A Framework for Representation and Analysis (2008, background): “Van Lamsweerde [48] describes a process by which security goals are made precise and refined until reaching security requirements.”
DAG-based attack and defense modeling: Don't miss the forest for the attack trees (2013, methodology): “Possible resolutions tactics, inspired by solutions proposed for analysis of non-functional requirements in software engineering, are described in [295] and [293].”
Analyzing Regulatory Rules for Privacy and Security Requirements (2008, background): “In requirements and software engineering, researchers have investigated methods for analyzing security requirements by using aspects [41], goals [22], [32], problem frames [34], [27], trust assumptions [26], and structured argumentation [28].”
Research Directions in Requirements Engineering (2007, background): “Several recent research projects evaluate how well requirements technologies apply to, or can be adapted to, domain-specific problems, such as security [174], semantic webs [52], and user interfaces [17].”