Value-Based Software Engineering: Overview and Agenda
The DOI matches its Crossref record; 36 of the 38 references it cites were found in a registry or an index.
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
“As a result, financial and technical planning, budgeting, monitoring, and maintaining tools have been developed and used for the well-attended facets [15,78], resulting in so-called”
From Lessons learned from developing a sustainability awareness framework for software engineering using design science (2024) · cites this paper as [15]
Citations
Cites
A Theory of Justice: Original Edition
Rawls, J. (1971) · doi:10.4159/9780674042605 · Cited by 9,496
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-citationAgile Software Development with SCRUM
Schwaber, K., & Beedle, M. (2001) · Cited by 2,656
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Cockburn, A. (2001) · UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno · Cited by 1,858
Non-Functional Requirements in Software Engineering
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000) · Springer eBooks · doi:10.1007/978-1-4615-5269-7 · Cited by 1,690
Agile Software Development Ecosystems
Highsmith, J. (2002) · International Linear Collider · Cited by 1,194
Evaluating Software Architectures: Methods and Case Studies
Clements, P., Kazman, R., & Klein, M. (2001) · Medical Entomology and Zoology · Cited by 850
A cost-value approach for prioritizing requirements
Karlsson, J., & Ryan, K. (1997) · IEEE Software · doi:10.1109/52.605933 · Cited by 726
Boehm, B. W., & DeMarco, T. (1997) · IEEE Software · doi:10.1109/ms.1997.589225 · Cited by 591
Self-citationSoftware engineering risk analysis and management
(1992) · Computer Standards & Interfaces · doi:10.1016/0920-5489(92)90060-q · Cited by 416
Boehm, B. (1989) · Lecture Notes in Computer Science · doi:10.1007/3-540-51635-2_29 · Cited by 381
Self-citationIdentifying quality-requirement conflicts
BOEHM, B. W., & In, H. P. (1996) · IEEE Software · doi:10.1109/52.506460 · Cited by 346
Self-citationThe structure and value of modularity in software design
Sullivan, K. J., Griswold, W. G., Cai, Y., & Hallen, B. (2001) · Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/503209.503224 · Cited by 299
Boehm, B. W., & Sullivan, K. J. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336584 · Cited by 230
Self-citationValue-based software engineering: a case study
BOEHM, B. W., & Huang, L. (2003) · Computer · doi:10.1109/mc.2003.1185215 · Cited by 209
Self-citationSecurity attribute evaluation method: a cost-benefit approach
Butler, S. A. (2002) · Proceedings of the 24th international conference on Software engineering - ICSE '02 · doi:10.1145/581339.581370 · Cited by 201
How good is good enough?: an ethical analysis of software construction and use
Collins, W. R., Miller, K. W., Spielman, B. J., & Wherry, P. (1994) · Communications of the ACM · doi:10.1145/175222.175229 · Cited by 159
Quantifying the costs and benefits of architectural decisions
Kazman, R., Asundi, J., & Klein, M. (2005) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2001.919103 · Cited by 139
Economic Information, Decision, and Prediction
Marschak, J. (1974) · Springer eBooks · doi:10.1007/978-94-010-9276-0 · Cited by 125
Reconciling software requirements and architectures with intermediate models
Grünbacher, P., Egyed, A. F., & Medvidović, N. (2004) · Software & Systems Modeling · doi:10.1007/s10270-003-0038-6 · Cited by 122
Data processing technology and economics
Phister, J. M. (1976) · Medical Entomology and Zoology · Cited by 111
Measuring the ROI of software process improvement
van Solingen, R. (2004) · IEEE Software · doi:10.1109/ms.2004.1293070 · Cited by 106
Sharpe, W. F. (1969) · Defense Technical Information Center (DTIC) · Cited by 106
Erdogmus, H., Favaro, J., & Strigel, W. (2004) · IEEE Software · doi:10.1109/ms.2004.1293068 · Cited by 80
Gerrard, P., & Thompson, N. (2002) · Cited by 70
Computers and Profits: Quantifying Financial Benefits of Information
Kleijnen, J. P. C. (1980) · Data Archiving and Networked Services (DANS) · Cited by 60
Lightweight and agile software development
Carroll, E. (2002) · Ubiquity · doi:10.1145/512526.512514 · Cited by 47
A comparison of approaches to reuse investment analysis
Favaro, J. (2002) · International Conference on Software Reuse · doi:10.1109/icsr.1996.496121 · Cited by 46
Value-based software engineering (VBSE): a value-driven approach to product-line engineering
Faulk, S. R., Harmon, R. R., & Raffo, D. (2000) · Software Product Lines · Cited by 39
Making the Software Business Case
Reifer, D. J. (2001) · Cited by 38
Keep Your Options Open: Extreme Programming and the Economics of Flexibility
Erdogmus, H., & Favaro, J. (2002) · NPARC · Cited by 38
Persson, C., & Yilmaztürk, N. (2004) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2004.1342729 · Cited by 29
Value-Based Software Engineering (VBSE)
Faulk, S. R., Harmon, R. R., & Raffo, D. (2000) · Software Product Lines · doi:10.1007/978-1-4615-4339-8_12 · Cited by 16
Software Risk Management and Insurance
Raz, O., & Shaw, M. (2001) · KiltHub Repository · doi:10.1184/r1/6625841 · Cited by 12
Marschak, J. (1974) · Springer eBooks · doi:10.1007/978-94-010-9276-0_1 · Cited by 4
Research works printed but not linked: 2
- Denne, M., Cleland-Huang, J.: Software by Numbers (Prentice Hall, 2003)
- Tockey, S.: Return on Software (Addison Wesley, 2004)
Cited by
A framework for understanding creativity in requirements engineering
Nguyen, L., & Shanks, G. (2008) · Information and Software Technology · doi:10.1016/j.infsof.2008.09.002 · Cited by 161
A product management challenge: Creating software product value through requirements selection
Barney, S., Aurum, A., & Wohlin, C. (2008) · Journal of Systems Architecture · doi:10.1016/j.sysarc.2007.12.004 · Cited by 157
Ramler, R., & Wolfmaier, K. (2006) · International Workshop on Automation of Software Test (AST) · doi:10.1145/1138929.1138946 · Cited by 155
A cybersecurity model in cloud computing environments
Rabai, L. B. A., Jouini, M., Aissa, A. B., & Mili, A. (2012) · Journal of King Saud University - Computer and Information Sciences · doi:10.1016/j.jksuci.2012.06.002 · Cited by 119
Infusing Design Thinking into a Software Engineering Capstone Course
Palacin-Silva, M. V., Khakurel, J., Happonen, A., Hynninen, T., & Porras, J. (2017) · IEEE International Conference on Software Engineering Education and Training (CSEE&T) · doi:10.1109/cseet.2017.41 · Cited by 80
Metadata
- Authors
- Boehm, B. W.
- Affiliations
- University of Southern California (US)
- Corresponding author
- Boehm, Barry W.
- Venue
- Value-Based Software Engineering
- Publisher
- Springer Berlin Heidelberg
- Published
- 2006
- Pages
- 3-14
- OpenAlex
- W41772636
- Cited by
- 139
- References
- 38
- Citations by year
- 2026: 1 · 2025: 1 · 2024: 4 · 2023: 6 · 2022: 8 · 2021: 1 · 2020: 2 · 2019: 7 · 2018: 8 · 2017: 13 · 2016: 10 · 2015: 10 · 2014: 7 · 2013: 9 · 2012: 12
- FWCI
- 28.88
- Type
- book chapter
- Language
- en
- Open access
- closed
- Locations
- Springer eBooks (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Social Sciences › Business, Management and Accounting › Strategy and Management › Value Engineering and Management
- Keywords
- value-based software engineering, value domains, success factors, software architecture, software design and development, verification and validation, software risk management, software quality management
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
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.