Value-Based Software Engineering: Overview and Agenda

  • Barry W. Boehm


Much of current software engineering practice and research is done in a value-neutral setting, in which every requirement, use case, object, test case, and defect is equally important. However, most studies of the critical success factors distinguishing successful from failed software projects find that the primary critical success factors lie in the value domain. The value-based software engineering (VBSE) agenda discussed in this chapter and exemplified in the other chapters involves integrating value considerations into the full range of existing and emerging software engineering principles and practices. The chapter then summarizes the primary components of the agenda: value-based requirements engineering, architecting, design and development, verification and validation, planning and control, risk management, quality management, people management, and an underlying theory of VBSE. It concludes with a global road map for realizing the benefits of VBSE.


Benefits realization business case analysis cost-benefit analysis investment analysis return on investment risk management stakeholder values software economics value-based software engineering 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. (Boehm, 1981).
    Boehm, B. W.: Software Engineering Economics (Prentice Hall, 1981)Google Scholar
  2. (Boehm, 1989).
    Boehm, B. W.: Software Risk Management (IEEE-CS Press, 1989)Google Scholar
  3. (Boehm and In, 1996).
    Boehm, B. W. and In H.: Identifying Quality-Requirement Conflicts. IEEE Software (March 1996), pp 25–35Google Scholar
  4. (Boehm and Huang, 2003).
    Boehm, B. W. and Huang, L.: Value-Based Software Engineering: A Case Study. IEEE Computer (March 2003), pp 33–41Google Scholar
  5. (Boehm and Sullivan, 2000).
    Boehm, B. W., Sullivan, K., Software Economics: A Roadmap. In: The Future of Software Economics, ed by Finkelstein, A. (ACM Press, 2000), pp 319–343Google Scholar
  6. (Bullock, 2000).
    Bullock, J.: Calculating the Value of Testing. Software Testing and Quality Engineering (May/June 2000), pp 56–62Google Scholar
  7. (Butler, 2002).
    Butler, S.: Security Attribute Evaluation Method: A Cost-Benefit Approach. Proceedings ICSE 2002 (ACM/IEEE, May 2002), pp 232–240Google Scholar
  8. (Charette, 1989).
    Charette, R.: Software Engineering Risk Analysis and Management (McGraw Hill, 1989)Google Scholar
  9. (Chung et al., 1999)
    Chung, L., Nixon, B., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering (Kluwer, 1999)Google Scholar
  10. (Clements et al.,2003)
    Clements, P., Kazman, R., Klein, M.: Evaluating Software Architecture: Methods and Case Studies (Addison Wesley, 2002)Google Scholar
  11. (Cockburn, 2002).
    Cockburn, A.: Agile Software Development (Addison Wesley, 2002)Google Scholar
  12. (Collins et al., 1994)
    Collins, W., Miller, K., Spielman, B., Wherry, J.: How Good is Good Enough? Communications of the ACM (January 1994), pp 81–91Google Scholar
  13. (DeMarco and Lister, 2003).
    DeMarco, T., Lister, T.: Waltzing with Bears (Dorset House, 2003)Google Scholar
  14. (Denne and Cleland-Huang, 2003).
    Denne, M., Cleland-Huang, J.: Software by Numbers (Prentice Hall, 2003)Google Scholar
  15. (Erdogmus et al., 2004)
    Erdogmus, H., Favaro, J., Strigel, W. (eds.): Special Issue: Return on Investment. IEEE Software, (May/June 2004)Google Scholar
  16. (Erdogmus and Favaro, 2002).
    Erdogmus, H., Favaro, J.: Keep your Options Open: Extreme Programming and the Economics of Flexibility. In: Extreme Programming Perspectives, ed by G. Succi et al. (Addison Wesley, 2002), pp 503–552Google Scholar
  17. (Favaro, 1996).
    Favaro, J.: A Comparison of Approaches to Reuse Investment Analysis. Proceedings, ICSR 4, (IEEE, 1996)Google Scholar
  18. (Faulk et al., 2000)
    Faulk, S., Harmon, D., Raffo, D.: Value-Based Software Engineering (VBSE): A Value-Driven Approach to Product-Line Engineering. Proceedings, First International Conference on Software Product Line Engineering, (August 2000)Google Scholar
  19. (Gerrard and Thompson, 2002).
    Gerrard, P., Thompson, N.: Risk-Based E-Business Testing (Artech House, 2002)Google Scholar
  20. (Grünbacher et al., 2004)
    Grünbacher, P., Egyed, A. F., Medvidovic, N.: Reconciling software requirements and architectures with intermediate models. In: Software and System Modeling (SoSyM), Vol. 3, No 3, (Springer, 2004), pp 235–253zbMATHGoogle Scholar
  21. (Highsmith, 2002).
    Highsmith, J.: Agile Software Development Ecosystems (Addison Wesley, 2002)Google Scholar
  22. (Karlsson and Ryan, 1997).
    Karlsson, J., Ryan, K.: A Cost-Value Approach for Prioritizing Requirements. IEEE Software (September–October, 1997), pp 67–74Google Scholar
  23. (Kazman et al., 2001)
    Kazman, R., Asundi J., Klein, M.: Quantifying the Costs and Benefits of Architectural Decisions. Proceedings, ICSE, (ACM/IEEE, 2001), pp 297–306Google Scholar
  24. (Kleijnen 1980).
    Kleijnen, J.: Computers and Profits: Quantifying Financial Benefits of Information (Addison Wesley, 1980)Google Scholar
  25. (Marschak, 1974).
    Marschak, J.: Economic Information, Decision, and Prediction (3 volumes), 1974Google Scholar
  26. (Persson and Yilmazturk, 2004).
    Persson, C., Yilmazturk, N.: Establishment of Automated Regression Testing at ABB: Industrial Experience Report on ‘Avoiding the Pitfalls.’ Proc. ISESE 2004, IEEE, August 2004, pp 112–121Google Scholar
  27. (Phister, 1979).
    Phister, M.: Data Processing Technology and Economics (Digital Press, 1979)Google Scholar
  28. (Rawls, 1971).
    Rawls, J.: A Theory of Justice. (Belknap/Harvard U. Press, 1971, 1999)Google Scholar
  29. (Raz and Shaw, 2001).
    Raz, O., Shaw, M.: Software Risk Management and Insurance. Proceedings, EDSER-3, IEEE-CS Press, 2001Google Scholar
  30. (Reifer, 2002).
    Reifer, D.: Making the Software Business Case (Addison Wesley, 2002)Google Scholar
  31. (Schwaber and Beedle, 2002).
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum (Prentice Hall, 2002)Google Scholar
  32. (Sharpe, 1969).
    Sharpe, W.: The Economics of Computers (Columbia U. Press, 1969)Google Scholar
  33. (Sullivan et al., 2001)
    Sullivan, K., Cai, Y., Hallen B., Griswold, W.: The Structure and Value of Modularity in Software Design. Proceedings, ESEC/FSE, 2001, ACM Press, pp 99–108Google Scholar
  34. (Tockey, 2004).
    Tockey, S.: Return on Software (Addison Wesley, 2004)Google Scholar
  35. (van Solingen, 2004)_van Solingen, R.: Measuring the ROI of Software Process Improvement. IEEE Software, May/June 2004, pp 32–38Google Scholar
  36. (Webster, 2002).
    Webster’s Collegiate Dictionary, Merriam-Webster, 2002Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Barry W. Boehm
    • 1
  1. 1.Center for Software EngineeringUniversity of Southern CaliforniaLos AngelesUSA

Personalised recommendations