The DOI matches its Crossref record.
A cost-value approach for prioritizing requirements
Abstract
Developing software systems that meet stakeholders' needs and expectations is the ultimate goal of any software provider seeking a competitive edge. To achieve this, you must effectively and accurately manage your stakeholders' system requirements: the features, functions, and attributes they need in their software system. Once you agree on these requirements, you can use them as a focal point for the development process and produce a software system that meets the expectations of both customers and users. However, in real world software development, there are usually more requirements than you can implement given stakeholders' time and resource constraints. Thus, project managers face a dilemma: how do you select a subset of the customers' requirements and still produce a system that meets their needs? The authors developed a cost-value approach for prioritizing requirements and applied it to two commercial projects.
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
Cited by
A bibliometric-based survey on AHP and TOPSIS techniques
Zyoud, S. H., & Fuchs-Hanusch, D. (2017) · Expert Systems with Applications · doi:10.1016/j.eswa.2017.02.016 · Cited by 492
A systematic literature review of software requirements prioritization research
Achimugu, P., Selamat, A., Ibrahim, R., & Mahrin, M. N. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.02.001 · Cited by 419
Security quality requirements engineering (SQUARE) methodology
Mead, N. R., & Stehney, T. (2005) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/1082983.1083214 · Cited by 317
Reasoning about partial goal satisfaction for requirements and design engineering
Letier, E., & van Lamsweerde, A. (2004) · Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering · doi:10.1145/1029894.1029905 · Cited by 265
Value-Based Software Engineering: Overview and Agenda
Boehm, B. W. (2006) · Value-Based Software Engineering · doi:10.1007/3-540-29263-2_1 · Cited by 139
Metadata
- Authors
- Karlsson, J., & Ryan, K.
- Venue
- IEEE Software
- Published
- 1997
- Volume
- 14
- Issue
- 5
- Pages
- 67-74
- ISSN
- 0740-7459 (ISSN-L)
- OpenAlex
- W2021767672
- Cited by
- 726
- References
- 0
- FWCI
- 21.01
- 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: A cost-value approach for prioritizing requirements. https://app.cochat.ai/papers/10.1109/52.605933
- The paper
- Karlsson, J., & Ryan, K. (1997). A cost-value approach for prioritizing requirements. IEEE Software. https://doi.org/10.1109/52.605933
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.