The DOI matches its Crossref record; 17 of the 17 references it cites were found in a registry or an index.
Security quality requirements engineering (SQUARE) methodology
Open accessAbstract
Requirements engineering, a vital component in successful project development, often neglects sufficient attention to security concerns. Further, industry lacks a useful model for incorporating security requirements into project development. Studies show that upfront attention to security saves the economy billions of dollars. Industry is thus in need of a model to examine security and quality requirements in the development stages of the production lifecycle.In this paper, we examine a methodology for both eliciting and prioritizing security requirements on a development project within an organization. We present a model developed by the Software Engineering Institute's Networked Systems Survivability (NSS) Program, and then examine two case studies where the model was applied to a client system. The NSS Program continues to develop this useful model, which has proven effective in helping an organization understand its security posture.
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
The Analytic Hierarchy Process
SAATY, T. L., & KEARNS, K. P. (1985) · Analytical Planning · doi:10.1016/b978-0-08-032599-6.50008-8 · Cited by 15,357
Object Oriented Software Engineering: A Use Case Driven Approach
Jacobson, I. (1992) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,914
Schiffrin, D. (1994) · Medical Entomology and Zoology · Cited by 1,394
Stoneburner, G., Goguen, A., & Feringa, A. (2002) · doi:10.6028/nist.sp.800-30 · Cited by 1,355
The guide to the Software Engineering Body of Knowledge
Bourque, P., Dupuis, R., Abran, A., Moore, J. W., & Tripp, L. (1999) · IEEE Software · doi:10.1109/52.805471 · Cited by 1,083
A cost-value approach for prioritizing requirements
Karlsson, J., & Ryan, K. (1997) · IEEE Software · doi:10.1109/52.605933 · Cited by 726
Checkland, P., & Poulter, J. (2010) · Systems Approaches to Managing Change: A Practical Guide · doi:10.1007/978-1-84882-809-4_5 · Cited by 722
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
Proceedings 25th International Conference on Software Engineering
(2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201182 · Cited by 505
(1998) · Defense Technical Information Center (DTIC) · Cited by 419
Cited by
Security Requirements Engineering: A Framework for Representation and Analysis
Haley, C. B., Laney, R., Moffett, J. D., & Nuseibeh, B. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.70754 · Cited by 462
A comparison of security requirements engineering methods
Fabian, B., Gürses, S., Heisel, M., Santen, T., & Schmidt, H. (2010) · Requirements Engineering · doi:10.1007/s00766-009-0092-x · Cited by 239
A scenario-based framework for the security evaluation of software architecture
Alkussayer, A., & Allen, W. H. (2010) · 2010 3rd International Conference on Computer Science and Information Technology · doi:10.1109/iccsit.2010.5564015 · Cited by 22
MAR(S)2: Methodology to articulate the requirements for security In SCADA
Gopal, T., Subbaraju, M., Joshi, R. V., & Dey, S. (2014) · Fourth edition of the International Conference on the Innovative Computing Technology (INTECH 2014) · doi:10.1109/intech.2014.6927744 · Cited by 5
Metadata
- Authors
- Mead, N. R., & Stehney, T.
- Venue
- ACM SIGSOFT Software Engineering Notes
- Published
- 2005-05-15
- Volume
- 30
- Issue
- 4
- Pages
- 1-7
- ISSN
- 0163-5948 (ISSN-L)
- OpenAlex
- W2146863076
- Cited by
- 317
- References
- 17
- FWCI
- 27.08
- Type
- journal article
- Language
- en
- Open access
- green
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: Security quality requirements engineering (SQUARE) methodology. https://app.cochat.ai/papers/10.1145/1082983.1083214
- The paper
- Mead, N. R., & Stehney, T. (2005). Security quality requirements engineering (SQUARE) methodology. ACM SIGSOFT Software Engineering Notes. https://doi.org/10.1145/1082983.1083214
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.
