Eliciting security requirements by misuse cases

@article{Sindre2000ElicitingSR,
  title={Eliciting security requirements by misuse cases},
  author={G. Sindre and A. Opdahl},
  journal={Proceedings 37th International Conference on Technology of Object-Oriented Languages and Systems. TOOLS-Pacific 2000},
  year={2000},
  pages={120-131}
}
  • G. Sindre, A. Opdahl
  • Published 2000
  • Computer Science
  • Proceedings 37th International Conference on Technology of Object-Oriented Languages and Systems. TOOLS-Pacific 2000
  • Use case diagrams (L. Jacobson et al., 1992) have proven quite helpful in requirements engineering, both for eliciting requirements and getting a better overview of requirements already stated. However, not all kinds of requirements are equally well supported by use case diagrams. They are good for functional requirements, but poorer at e.g., security requirements, which often concentrate on what should not happen in the system. With the advent of e- and m-commerce applications, security… CONTINUE READING
    179 Citations

    Figures and Topics from this paper.

    Templates for Misuse Case Description
    • 182
    Eliciting security requirements with misuse cases
    • 925
    • PDF
    Capturing Security Requirements through Misuse Cases
    • 77
    • PDF
    Quality Misuse
    • 16
    • Highly Influenced
    Misuse Cases and Abuse Cases in Eliciting Security Requirements
    • 5
    • Highly Influenced
    • PDF
    Integrating functional and security requirements with use case decomposition
    • Joshua J. Pauli, D. Xu
    • Computer Science
    • 11th IEEE International Conference on Engineering of Complex Computer Systems (ICECCS'06)
    • 2006
    • 9
    Core Security Requirements Artefacts
    • 62
    • PDF
    Misuse Cases + Assets + Security Goals
    • 21
    • PDF
    Security Requirements Elicitation Using View Points for Online System
    • A. Agarwal, D. Gupta
    • Computer Science
    • 2008 First International Conference on Emerging Trends in Engineering and Technology
    • 2008
    • 20

    References

    SHOWING 1-5 OF 5 REFERENCES
    Use cases, UML visual modelling and the trivialisation of business requirements
    • J. Arlow
    • Computer Science
    • Requirements Engineering
    • 2008
    • 9
    Seven myths of formal methods
    • A. Hall
    • Computer Science
    • IEEE Software
    • 1990
    • 716
    • PDF
    Deriving Goals h m a Use Case Based Requirements Specification for an Electronic Commerce System ”
    • Scenario Usage in System Development : A Report on Current Practice “ , IEEE Software
    Getting Started: Using Use Cases to Capture Requirements
    • J. Rumbaugh
    • Computer Science
    • J. Object Oriented Program.
    • 1994
    • 163
    Guiding Goal Models Using Scenarios ”
    • IEEE Transactions on Software Engineering
    • 1996