The DOI matches its Crossref record; 47 of the 47 references it cites were found in a registry or an index.
Exploring software security approaches in software development lifecycle: A systematic mapping study
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“So in addition to the four inductively derived categories we complemented the thematic dimensions of the developing model with a DevSecOps lifecycle framework (MacDonald and Head, 2016), based on the established concept of the SDLC (Pothukuchi et al., 2023; Mohammed et al., 2017).”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Mohammed et al., 2017
In the citing paper
“Mohammed et al. (2017) defines the main steps of the SDLC: Requirements, Design, Coding, Testing, Deployment, and Maintenance”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Mohammed et al. (2017)
Citations
Cites
Software Security: Building Security In
McGraw, G. E. (2006) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre.2006.43 · Cited by 792
SecureUML: A UML-Based Modeling Language for Model-Driven Security
Lodderstedt, T., Basin, D., & Doser, J. (2002) · Lecture notes in computer science · doi:10.1007/3-540-45800-x_33 · Cited by 763
Eliciting security requirements with misuse cases
Sindre, G., & Opdahl, A. L. (2004) · Requirements Engineering · doi:10.1007/s00766-004-0194-4 · Cited by 731
UMLsec: Extending UML for Secure Systems Development
Jürjens, J. (2002) · Lecture notes in computer science · doi:10.1007/3-540-45800-x_32 · Cited by 711
Understanding and controlling software costs
BOEHM, B. W., & Papaccio, P. N. (1988) · IEEE Transactions on Software Engineering · doi:10.1109/32.6191 · Cited by 667
McGraw, G. E. (2004) · IEEE Security & Privacy · doi:10.1109/msecp.2004.1281254 · Cited by 547
A Survey on Shari’Ah Governance Practices in Malaysia, GCC Countries and the UKPreprint
Hasan, Z. (2011) · SSRN Electronic Journal · Cited by 452
A taxonomy of computer program security flaws
Landwehr, C. E., Bull, A. R., McDermott, J. P., & Choi, W. S. (1994) · ACM Computing Surveys · doi:10.1145/185403.185412 · Cited by 451
Eliciting security requirements by misuse cases
Sindre, G., & Opdahl, A. L. (2002) · doi:10.1109/tools.2000.891363 · Cited by 328
Exploiting Software: How to Break Code
Hoglund, G., & McGraw, G. E. (2004) · Cited by 305
Research works printed but not linked: 3
- McGraw, 2006
- McGraw, 2004
- Sindre, 2004, Eliciting security requirements with misuse cases, Requir. Eng., 10, 34, 10.1007/s00766-004-0194-4 · DOI
Cited by
Sorted by citations
Identifying the primary dimensions of DevSecOps: A multi-vocal literature review
Zhao, X., Clear, T., & Lal, R. (2024) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112063 · Cited by 40
Metadata
- Authors
- Mohammed, N. M., Niazi, M., Alshayeb, M., & Mahmood, S.
- Affiliations
- King Fahd University of Petroleum and Minerals (SA)
- Corresponding author
- Niazi, Mahmood
- Venue
- Computer Standards & Interfaces
- Publisher
- Elsevier BV
- Published
- 2017-02
- Volume
- 50
- Pages
- 107-115
- ISSN
- 0920-5489 (ISSN-L)
- OpenAlex
- W2529133275
- Cited by
- 104
- References
- 47
- Citations by year
- 2026: 2 · 2025: 7 · 2024: 11 · 2023: 14 · 2022: 17 · 2021: 17 · 2020: 14 · 2019: 8 · 2018: 9 · 2017: 5
- FWCI
- 16.37
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Computer Standards & Interfaces (publishedVersion)
- Funders
- King Fahd University of Petroleum and Minerals (IN141011)
- Topics
- Physical Sciences › Computer Science › Information Systems › Web Application Security Vulnerabilities
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Hardware and Architecture › Security and Verification in Computing
- Keywords
- software security, software development lifecycle, vulnerability detection, vulnerability reduction, static analysis, dynamic analysis, security requirements engineering
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
