The DOI matches its Crossref record; 26 of the 26 references it cites were found in a registry or an index.
Eliciting security requirements with misuse cases
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Object Oriented Software Engineering: A Use Case Driven Approach
Jacobson, I. (1992) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,914
The Rational Unified Process: An Introduction
Kruchten, P. B. (1998) · Cited by 2,592
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Non-Functional Requirements in Software Engineering
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000) · Springer eBooks · doi:10.1007/978-1-4615-5269-7 · Cited by 1,690
Requirements Engineering: Processes and Techniques
Kotonya, G., & Sommerville, I. (1998) · Lancaster EPrints (Lancaster University) · Cited by 1,688
Cockburn, A. (2000) · Cited by 1,531
Secrets and lies: digital security in a networked world
(2001) · Choice Reviews Online · doi:10.5860/choice.38-3941 · Cited by 1,159
Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design
Constantine, L. L. (1999) · Cited by 734
Handling obstacles in goal-oriented requirements engineering
van Lamsweerde, A., & Letier, E. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.879820 · Cited by 648
From object-oriented to goal-oriented requirements analysis
Mylopoulos, J., Chung, L., & Yu, E. (1999) · Communications of the ACM · doi:10.1145/291469.293165 · Cited by 581
Guiding goal modeling using scenarios
Rolland, C., Souveyet, C., & Achour, C. B. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.738339 · Cited by 478
Building Secure Software: How to Avoid Security Problems the Right Way
Viega, J., & McGraw, G. E. (2001) · Cited by 440
Software engineering for security: a roadmap
Devanbu, P. T., & Stubblebine, S. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336559 · Cited by 418
Using abuse case models for security requirements analysis
McDermott, J. P., & Fox, C. (2003) · Annual Computer Security Applications Conference · doi:10.1109/csac.1999.816013 · Cited by 398
New directions on agile methods: a comparative analysis
Abrahamsson, P., Warsta, J., Siponen, M. T., & Ronkainen, J. (2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201204 · Cited by 394
Security and privacy requirements analysis within a social setting
Liu, L., Yu, E., & Mylopoulos, J. (2004) · Journal of Lightwave Technology · doi:10.1109/icre.2003.1232746 · Cited by 393
Eliciting security requirements by misuse cases
Sindre, G., & Opdahl, A. L. (2002) · doi:10.1109/tools.2000.891363 · Cited by 328
Self-citationFundamentals of computer security technology
Amoroso, E. G. (1994) · Medical Entomology and Zoology · Cited by 285
Use cases: requirements in context
Kulak, D., & Guiney, E. (2000) · CERN Document Server (European Organization for Nuclear Research) · Cited by 284
The three dimensions of requirements engineering: A framework and its applications
Pohl, K. (1994) · Information Systems · doi:10.1016/0306-4379(94)90044-2 · Cited by 269
Elicitation technique selection: how do experts do it?
Hickey, A. M., & Davis, A. M. (2004) · Journal of Lightwave Technology · doi:10.1109/icre.2003.1232748 · Cited by 222
Effective Communication in Requirements Elicitation: A Comparison of Methodologies
Coughlan, J., & Macredie, R. D. (2002) · Requirements Engineering · doi:10.1007/s007660200004 · Cited by 212
Deriving Goals from a Use-Case Based Requirements Specification
Antón, A. I., Carter, R. A., Dagnino, A., et al. (2001) · Requirements Engineering · doi:10.1007/pl00010356 · Cited by 86
CREWS-SAVRE: systematic scenario generation and use
Maiden, N., Minocha, S., Manning, K., & Ryan, M. (1998) · IEEE International Requirements Engineering Conference · doi:10.1109/icre.1998.667820 · Cited by 67
Strategies for Developing Policies and Requirements for Secure Electronic Commerce Systems
Antón, A. I., & Earp, J. B. (2000) · NCSU Libraries Repository (North Carolina State University Libraries) · Cited by 66
Strategies for Developing Policies and Requirements for Secure and Private Electronic Commerce
Antón, A. I., & Earp, J. B. (2001) · Advances in information security · doi:10.1007/978-1-4615-1467-1_5 · Cited by 24
Cited by
On lightweight mobile phone application certification
Enck, W., Ongtang, M., & McDaniel, P. (2009) · Proceedings of the 16th ACM conference on Computer and communications security · doi:10.1145/1653662.1653691 · Cited by 921
A survey of approaches combining safety and security for industrial control systems
Kriaa, S., Pietre-Cambacedes, L., Bouissou, M., & Halgand, Y. (2015) · Reliability Engineering & System Safety · doi:10.1016/j.ress.2015.02.008 · Cited by 375
DAG-based attack and defense modeling: Don’t miss the forest for the attack trees
Kordy, B., Piètre-Cambacédès, L., & Schweitzer, P. (2014) · Computer Science Review · doi:10.1016/j.cosrev.2014.07.001 · Cited by 321
Addressing privacy requirements in system design: the PriS method
Kalloniatis, C., Kavakli, E., & Gritzalis, S. (2008) · Requirements Engineering · doi:10.1007/s00766-008-0067-3 · Cited by 269
Exploring software security approaches in software development lifecycle: A systematic mapping study
Mohammed, N. M., Niazi, M., Alshayeb, M., & Mahmood, S. (2017) · Computer Standards & Interfaces · doi:10.1016/j.csi.2016.10.001 · Cited by 104
Metadata
- Authors
- Sindre, G., & Opdahl, A. L.
- Venue
- Requirements Engineering
- Published
- 2004-06-24
- Volume
- 10
- Issue
- 1
- Pages
- 34-44
- ISSN
- 0947-3602 (ISSN-L)
- 1432-010X
- OpenAlex
- W3161918289
- Cited by
- 730
- References
- 26
- FWCI
- 50.15
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.