Cited by 239Software Engineering Techniques and PracticesSafety Systems Engineering in AutonomyAdvanced Software Engineering Methodologies

A comparison of security requirements engineering methods

Fabian, Benjamin, Gürses, Seda, Heisel, Maritta, Santen, Thomas, Schmidt, Holger·2010·Requirements Engineering

Integrity signals

Registry

Crossref · 10.1007/s00766-009-0092-x

Cites

90 of 90 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Over the last several years the MEM was actively used as a framework for the comparative evaluation of security and risk identification and analysis methods.

    “Over the last several years the MEM was actively used as a framework for the comparative evalu-ation of security and risk identification and analysis methods (Espaná et al., 2010; Fabian et al., 2010; Labunets et al., 2013, 2014).”

    From A review of cyber security risk assessment methods for SCADA systems (2016) · cites this paper as Fabian et al., 2010

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Fabian, B., Gürses, S., Heisel, M., Santen, T., & Schmidt, H.
Affiliations
  • Humboldt-Universität zu Berlin (DE)
  • KU Leuven (BE)
  • University of Duisburg-Essen (DE)
  • Microsoft (Germany) (DE)
Corresponding author
  • Fabian, Benjamin
  • Gürses, Seda
  • Heisel, Maritta
  • Santen, Thomas
  • Schmidt, Holger
Venue
Requirements Engineering
Published
2009-11-26
Volume
15
Issue
1
Pages
7-40
ISSN
  • 0947-3602 (ISSN-L)
  • 1432-010X
OpenAlex
W2111695375
Cited by
239
References
90
Citations by year
2026: 1 · 2025: 4 · 2024: 8 · 2023: 8 · 2022: 6 · 2021: 10 · 2020: 11 · 2019: 17 · 2018: 18 · 2017: 18 · 2016: 19 · 2015: 30 · 2014: 30 · 2013: 19 · 2012: 21
FWCI
35.25
Type
journal article
Language
en
Open access
closed
Locations
Requirements Engineering (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Engineering › Safety, Risk, Reliability and Quality › Safety Systems Engineering in Autonomy
  • Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
Keywords
security requirements engineering, security requirements elicitation, security requirements analysis, conceptual framework, Common Criteria, Secure Tropos, MsrA, problem frames, method comparison, method evaluation, quality assurance

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