Value-Based Software Engineering: Seven Key Elements and Ethical Considerations | SpringerLink
Skip to main content
Springer Nature Link
Log in

Value-Based Software Engineering: Seven Key Elements and Ethical Considerations

  • Chapter
Value-Based Software Engineering

Abstract:

This chapter presents seven key elements that provide candidate foundations for value-based software engineering:

  1. 1.

    Benefits Realization Analysis

  2. 2.

    Stakeholder Value Proposition Elicitation and Reconciliation

  3. 3.

    Business Case Analysis

  4. 4.

    Continuous Risk and Opportunity Management

  5. 5.

    Concurrent System and Software Engineering

  6. 6.

    Value-Based Monitoring and Control

  7. 7.

    Change as Opportunity

Using a case study we show how some of these elements can be used to incorporate ethical considerations into daily software engineering practice.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution

Subscribe and save

Springer+ Basic
¥17,985 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
JPY 3498
Price includes VAT (Japan)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
JPY 17159
Price includes VAT (Japan)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
JPY 21449
Price includes VAT (Japan)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
JPY 21449
Price includes VAT (Japan)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

References

  1. ACM/IEEE: The Software Engineering Code of Ethics and Professional Practice. http://www.acm.org, http://www.computer.org (1998)

    Google Scholar 

  2. Ahern, D., Clouse, A., Turner, R.: CMMI Distilled (Addison Wesley, 2001)

    Google Scholar 

  3. Al-Said, M.: Identifying, Analyzing, and Avoiding Software Model Clashes PhD Dissertation (USC, 2003)

    Google Scholar 

  4. Amram, M., Kulatilaka, N.: Real Options (Harvard Business School Press, 1999)

    Google Scholar 

  5. Anderson, R., Johnson, D., Gotterbarn, D., Perolle, J.: Using the New ACM Code of Ethics in Decision Making (Comm. ACM, February 1993), pp 98–105

    Google Scholar 

  6. Baird, R., Ramsower, R., Rosenbaum, S.: Cyberethics (Prometheus Books, 2000)

    Google Scholar 

  7. Baldwin, C., Clark, K.: Design Rules: The Power of Modularity (MIT Press, 2000)

    Google Scholar 

  8. Boehm, B. W., Turner, R.: Balancing Agility and Discipline (Addison Wesley, 2004)

    Google Scholar 

  9. Boehm, B. W., Port, D., Al-Said, M.: Avoiding the Software Model-Clash Spiderweb (Computer, 2000), pp 120–122

    Google Scholar 

  10. Boehm, B. W., Port, D., Jain, A., Basili, V.: Achieving CMMI Level 5 Improvements with MBASE and the CeBASE Method (Cross Talk, 2002)

    Google Scholar 

  11. Boehm, B. W., Port, D., Huang, L., Brown, A. W.: Using the Spiral Model and MBASE to Generate New Acquisition Process Models: SAIV, CAIV, and SCQAIV (Cross Talk, 2002)

    Google Scholar 

  12. Boehm, B. W. and Huang, L.G.: Value-based Software Engineering: A Case Study, IEEE Computer, March 2003 pp 33–41

    Google Scholar 

  13. Boehm, B. W., Port, D.: Balancing Discipline and Flexibility with the Spiral Model and MBASE (Cross Talk, 2001)

    Google Scholar 

  14. Boehm, B. W., Ross, R.: Theory-W Software Project Management: Principles and Examples (IEEE Transactions on Software Engineering, 1989), pp 902–916

    Google Scholar 

  15. Carr, D.: Sweet Victory (Baseline, 2002)

    Google Scholar 

  16. Cohen, L.: Quality Function Deployment (Prentice Hall, 1995)

    Google Scholar 

  17. Collins, W., Miller, K., Spielman, B., Wherry, J.: How Good is Good Enough? (Comm. ACM, 1994), pp 81–91

    Google Scholar 

  18. Cusumano, M., Selby, R.: Microsoft Secrets, How the World’s Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People (The Free Press, 1995)

    Google Scholar 

  19. Ehn P. (ed): Work-Oriented Design of Computer Artifacts (Lawrence Erlbaum Assoc., 1990)

    Google Scholar 

  20. Ermann, M. D., Shauf, M.: Computers, Ethics, and Society 3 (Oxford U. Press, 2003)

    Google Scholar 

  21. Federal Aviation Administration (FAA): The Integrated Capability Maturity Model (1997)

    Google Scholar 

  22. 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 

  23. Highsmith, J.: Adaptive Software Development (Dorset House, 2000)

    Google Scholar 

  24. Highsmith, J.: Agile Software Development Ecosystems, (Addison Wesley, 2002)

    Google Scholar 

  25. Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process (Addison Wesley, 1999)

    Google Scholar 

  26. Johnson, D., Nissenbaum, H.: Computers, Ethics, and Social Values (Prentice Hall, 1995)

    Google Scholar 

  27. Kaplan, R., Norton, D.: The Balanced Scorecard: Translating Strategy into Action (Harvard Business School Press, 1996)

    Google Scholar 

  28. Kauffman, S.: At Home in the Universe (Oxford University Press, 1995)

    Google Scholar 

  29. Kruchten, P.: The Rational Unified Process 3 (Addison Wesley, 2001)

    Google Scholar 

  30. Paulk, M., Weber, C., Curtis, B., Chrissis, M.: The Capability Maturity Model (Addison Wesley, 1994)

    Google Scholar 

  31. Parnas, D.: Designing Software for Ease of Extension and Contraction (IEEE Transactions on Software Engineering, 1979), pp 128–137

    Google Scholar 

  32. Rawls, J.: A Theory of Justice (Belknap/Harvard U. Press, 1971)

    Google Scholar 

  33. Reifer, D.: Making the Software Business Case (Addison Wesley, 2002)

    Google Scholar 

  34. Royce, W. E.: Software Project Management (Addison-Wesley, 1998)

    Google Scholar 

  35. Morton, M. S.: The Corporation of the 1990s: Information Technology and Organization Transformation (Oxford University Press, 1991)

    Google Scholar 

  36. Software Engineering Institute (SEI): Capability Maturity Model Integration (CMMI), Version 1.1 (CMU/SEI-2002-TR-012, 2002)

    Google Scholar 

  37. Software Productivity Consortium (SPC): The Evolutionary Spiral Process. SPC Technical Report (Herndon, VA, 1992)

    Google Scholar 

  38. Sullivan, K., Cai, Y., Hallen, B., Griswold, W.: The Structure and Value of Modularity in Software Design. Proceedings, ESEC/FSE, 2001 (ACM Press, 2001), pp 99–108

    Google Scholar 

  39. Thorp, J., DMR: The Information Paradox (McGraw Hill, 1998)

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Center for Software Engineering, University of Southern California, 941 W. 37th Place, SAL Room 328, Los Angeles, CA, 90089-0781, USA

    Barry W. Boehm

Authors
  1. Barry W. Boehm
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. Institute for Software Technology, Vienna University of Technology, Karlsplatz 13, 1040, Wien, Austria

    Stefan Biffl

  2. School of Information Systems, Technology and Management, University of New South Wales, Sydney, NSW, 2052, Australia

    Aybüke Aurum

  3. Center for Software Engineering, University of Southern California, 941 W 37th Place, Los Angeles, CA, 90089-0781, USA

    Barry Boehm

  4. Software Engineering NRC Institute for Information Technology, National Research Council Canada, Building M50, 1200 Montreal Rd., Ottawa, ON, Canada, K1A 0R6

    Hakan Erdogmus

  5. Systems Engineering & Automation, Johannes Kepler University Linz, Altenbergerstr. 69, 4040, Linz, Austria

    Paul Grünbacher

Rights and permissions

Reprints and permissions

Copyright information

© 2006 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Boehm, B.W. (2006). Value-Based Software Engineering: Seven Key Elements and Ethical Considerations. In: Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., Grünbacher, P. (eds) Value-Based Software Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-29263-2_6

Download citation

  • DOI: https://doi.org/10.1007/3-540-29263-2_6

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-25993-0

  • Online ISBN: 978-3-540-29263-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation