The DOI matches its Crossref record; 24 of the 24 references it cites were found in a registry or an index.
Value-based software engineering
Abstract
Much of current software engineering practice and research is done in a value-neutral setting, in which every requirement, use case, object, and defect is treated as equally important; methods are presented and practiced as largely logical activities; and a "separation of concerns" is practiced, in which the responsibility of software engineers is confined to turning software requirements into verified code. In earlier times, when software decisions had relatively minor influences on a system's cost, schedule, and value, the value-neutral approach was reasonably workable. But today and increasingly in the future, software has a major influence on most systems' cost, schedule, and value; and value-neutral software decisions can seriously degrade project outcomes.This paper presents an agenda for a discipline of Value-Based Software Engineering. It accepts the challenge of integrating value considerations into all of the existing and emerging software engineering principles and practices, and of developing an overall framework in which they compatibly reinforce each other. Example elements of this agenda include value-based requirements engineering, architecting, design and development, verification and validation, planning and control, risk management, quality management, and people management. It presents seven key elements that provide candidate foundations for value-based software engineering: Benefits Realization Analysis; Stakeholder Value Proposition Elicitation and Reconciliation; Business Case Analysis; Continuous Risk and Opportunity Management; Concurrent System and Software Engineering; Value-Based Monitoring and Control; and Change as Opportunity.
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 balanced scorecard: Translating strategy into action
(1997) · Long Range Planning · doi:10.1016/s0024-6301(97)80925-9 · Cited by 8,192
Software Engineering Economics
Boehm, B. W. (2001) · Pioneers and Their Contributions to Software Engineering · doi:10.1007/978-3-642-48354-7_5 · Cited by 5,981
Self-citationDesign Rules: The Power of Modularity
Baldwin, C. Y., & Clark, K. B. (2000) · doi:10.7551/mitpress/2366.001.0001 · Cited by 3,504
The Unified Software Development Process
Jacobson, I., Booch, G., & Rumbaugh, J. E. (1999) · CERN Document Server (European Organization for Nuclear Research) · Cited by 3,389
Holland, J. H. (1998) · doi:10.1093/oso/9780198504092.001.0001 · Cited by 2,410
Software Cost Estimation With Cocomo II
BOEHM, B. W., Abts, C., Brown, A. W., Chulani, S., Clark, B., Horowitz, E., Madachy, R. J., Reifer, D. J., & Steece, B. M. (2000) · Cited by 1,774
Self-citationThe Goal Question Metric Approach
Basili, V. R., Caldiera, G., & Rombach, H. D. (1994) · Cited by 1,651
WHEELER, J. A. (1994) · CERN Document Server (European Organization for Nuclear Research) · Cited by 1,212
Get ready for agile methods, with care
Boehm, B. (2002) · Computer · doi:10.1109/2.976920 · Cited by 902
Self-citationAgile Software Development Ecosystems
Highsmith, J. (2002) · International Linear Collider · Cited by 874
Cited by
Software Testing Research: Achievements, Challenges, Dreams
Bertolino, A. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.25 · Cited by 840
A view of 20th and 21st century software engineering
Boehm, B. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134288 · Cited by 510
Self-citationManaging technical debt in software-reliant systems
Brown, N., Cai, Y., Guo, Y., Kazman, R., Kim, M., Kruchten, P., Lim, E., MacCormack, A., Nord, R., Ozkaya, I., et al. (2010) · Proceedings of the FSE/SDP workshop on Future of software engineering research · doi:10.1145/1882362.1882373 · Cited by 432
The impact of agile practices on communication in software development
Pikkarainen, M., Haikara, J., Salo, O., Abrahamsson, P., & Still, J. (2008) · Empirical Software Engineering · doi:10.1007/s10664-008-9065-9 · Cited by 335
A survey of traceability in requirements engineering and model-driven development
Winkler, S., & von Pilgrim, J. (2010) · Software & Systems Modeling · doi:10.1007/s10270-009-0145-0 · Cited by 313
Metadata
- Authors
- Boehm, B.
- Venue
- ACM SIGSOFT Software Engineering Notes
- Published
- 2003-03
- Volume
- 28
- Issue
- 2
- Pages
- 4
- ISSN
- 0163-5948 (ISSN-L)
- OpenAlex
- W1970799501
- Cited by
- 484
- References
- 24
- FWCI
- 80.21
- 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: Value-based software engineering. https://app.cochat.ai/papers/10.1145/638750.638776
- The paper
- Boehm, B. (2003). Value-based software engineering. ACM SIGSOFT Software Engineering Notes. https://doi.org/10.1145/638750.638776
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.