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.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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,409
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
Cited by
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
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
A Serious Game for Eliciting Social Engineering Security Requirements
Beckers, K., & Pape, S. (2016) · 2016 IEEE 24th International Requirements Engineering Conference (RE) · doi:10.1109/re.2016.39 · Cited by 98
Kumar, R., & Goyal, R. (2020) · Computers & Security · doi:10.1016/j.cose.2020.101967 · Cited by 97
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Eliciting security requirements with misuse cases. https://app.cochat.ai/papers/10.1007/s00766-004-0194-4
- The paper
- Sindre, G., & Opdahl, A. L. (2005). Eliciting security requirements with misuse cases. Requirements Engineering. https://doi.org/10.1007/s00766-004-0194-4
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.
