The Future of Software Processes

  • Barry Boehm
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3840)


In response to increasing demands being put onto software-intensive systems, software processes will evolve significantly over the next two decades. This paper identifies seven relatively surprise-free trends – increased emphasis on users and end value; increasing software criticality and need for dependability; increasingly rapid change; increasingly complex systems of systems; increasing needs for COTS, reuse, and legacy software integration; and computational plenty – and two “wild card” trends: increasing software autonomy and combinations of biology and computing; and discusses their likely influences on software processes between now and 2025. It also discusses limitations to software process improvement, and areas of significant software process research and education needs.


Software Process Enterprise Architecture Software Process Improvement Wild Card Life Cycle Process 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Albert, C., Brownsword, L.: Evolutionary Process for Integrating COTS-Based Systems (EPIC): An Overview. CMU/SEI-20030/TR-009. Software Engineering Institute, Pittsburgh (2002)Google Scholar
  2. 2.
    Anthes, G.: The Future of IT. Computerworld, 27–36, March 7 (2005)Google Scholar
  3. 3.
    Arthur, W.B.: Increasing Returns and the New World of Business. Harvard Business Review, 100–109 (July/August 1996)Google Scholar
  4. 4.
    Aurum, A., Biffl, S., Boehm, B., Erdogmus, H., Gruenbacher, P. (eds.): Value-Based Software Engineering. Springer, Heidelberg (2005)Google Scholar
  5. 5.
    Basili, V., Zelkowitz, M., McGarry, F., Page, J., Waligora, S., Pajerski, R.: Special Report: SEL’s Process-Improvement Program. Software, 83–87 (November 1995)Google Scholar
  6. 6.
    Boehm, B.: A Spiral Model for Software Development and Enhancement. Computer, 61–72 (May 1988)Google Scholar
  7. 7.
    Boehm, B., Brown, A.W., Basili, V., Turner, R.: Spiral Acquisition of Software-Intensive Systems of Systems. CrossTalk, 57–63 (May 2004)Google Scholar
  8. 8.
    Boehm. B., Hoare, C.A.R. (eds.): Proceedings, 1975 International Conference on Reliable Software. ACM/IEEE (April 1975)Google Scholar
  9. 9.
    Boehm, B., Jain, A.: An Initial Theory of Value-Based Software Engineering. In: Aurum, A., Biffl, S., Boehm, B., Erdogmus, H., Gruenbacher, P. (eds.) Value-Based Software Engineering. Springer, Heidelberg (2005)Google Scholar
  10. 10.
    Boehm, B., Turner, R.: Balancing Agility and Discipline. Addison-Wesley, Reading (2004)Google Scholar
  11. 11.
    Brooks, F.: The Mythical Man-Month, 2nd edn. Addison-Wesley, Reading (1995)Google Scholar
  12. 12.
    Conway, M.: How Do Committees Invent? Datamation, 28–31 (April 1968)Google Scholar
  13. 13.
    Crawford, D.: Editorial Pointers. Comm. ACM, 5 (October 2001)Google Scholar
  14. 14.
    Drexler, E.K.: Engines of Creation. Anchor Press (1986)Google Scholar
  15. 15.
    Drexler, K.E., Peterson, C., Pergamit, G.: Unbounding the Future: The Nanotechnology Revolution. William Morrow & Co. (1991)Google Scholar
  16. 16.
    Dreyfus, H., Dreyfus, S.: Mind over Machine. Macmillan, Basingstoke (1986)Google Scholar
  17. 17.
    Druffel, L., Loy, N., Rosenberg, R., Sylvester, R., Volz, R.: Information Architectures that Enhance Operational Capability in Peacetime and Warfare. USAF-SAF Study Report (February 1994)Google Scholar
  18. 18.
    Dyson, G.B.: Darwin Among the Machines: The Evolution of Global Intelligence. Helix Books/Addison Wesley (1997)Google Scholar
  19. 19.
    Ehn, P. (ed.): Work-Oriented Design of Computer Artifacts. Lawerence Earlbaum Assoc. (1990)Google Scholar
  20. 20.
    FCIO (Federal CIO Council): A Practical Guide to Federal Enterprise Architecture, Version 1.0 (February 2001)Google Scholar
  21. 21.
    Fuggetta, A.: Software Process: A Roadmap. In: Finkelstein, A. (ed.) The Future of Software Engineering. ACM Press, New York (2000)Google Scholar
  22. 22.
    Gerrard, P., Thompson, N.: Risk-Based E-Business Testing. Artech House (2002)Google Scholar
  23. 23.
    Grady, R.: Successful Software Process Improvement. Prentice-Hall, Englewood Cliffs (1997)Google Scholar
  24. 24.
    Gruenbacher, P., Koeszegi, S., Biffl, S.: Stakeholder Value Proposition Elicitation and Reconciliation. In: Aurum, A., Biffl, S., Boehm, B., Erdogmus, H., Gruenbacher, P. (eds.) Value-Based Software Engineering. Springer, Heidelberg (2005)Google Scholar
  25. 25.
    Harned, D., Lundquist, J.: What Transformation Means for the Defense Industry. The McKinsey Quarterly, 57–63, November 3 (2003)Google Scholar
  26. 26.
    Hofstede, G.: Culture and Organizations. McGraw-Hill, New York (1997)Google Scholar
  27. 27.
    Highsmith, J.: Adaptive Software Development. Dorset House (2000)Google Scholar
  28. 28.
    Huang, L.: A Value-Based Process for Achieving Software Dependability. In: Proceedings, Software Process Workshop 2005 (May 2005)Google Scholar
  29. 29.
    Humphrey, W.: Introduction to the Personal Software Process. Addison-Wesley, Reading (1997)Google Scholar
  30. 30.
    Humphrey, W.: Introduction to the Team Software Process. Addison-Wesley, Reading (2000)Google Scholar
  31. 31.
    ISO (International Standards Organization): Standard for Information Technology – Software Life Cycle Processes. ISO/IEC 12207 (1995)Google Scholar
  32. 32.
    Joy, B.: Why the Future Doesn’t Need Us: Wired (April 2000)Google Scholar
  33. 33.
    Kurzweil, R.: The Age of Spiritual Machines. Penguin Books (1999)Google Scholar
  34. 34.
    Lampson, B.: Computing Meets the Physical World, pp. 4–7. The Bridge (2003)Google Scholar
  35. 35.
    Maslow, A.: Motivation and Personality. Harper and Row (1954)Google Scholar
  36. 36.
    Moore, G.: Inside the Tornado. Harper Collins (1995)Google Scholar
  37. 37.
    Musa, J.: Software Reliability Engineering. McGraw-Hill, New York (1999)Google Scholar
  38. 38.
    Patterson, D.: 20th Century vs. 21st Century C&C: The SPUR Manifesto. ACM Comm, 15–16 (March 2005)Google Scholar
  39. 39.
    Paulk, M., Weber, C., Curtis, B., Chrissis, M.: The Capability Maturity Model. Addison-Wesley, Reading (1994)Google Scholar
  40. 40.
    Phongpaibul, M., Boehm, B.: Improving Quality Through Software Process Improvement in Thailand: Initial Analysis. In: Proceedings, ICSE 2005 Workshop on Software Quality (May 2005)Google Scholar
  41. 41.
    PITAC (President’s Information Technology Advisory Committee): Report to the President: Information Technology Research: Investing in Our Future (1999)Google Scholar
  42. 42.
    Putman, J.: Architecting with RM-ODP. Prentice-Hall, Englewood Cliffs (2001)Google Scholar
  43. 43.
    Rechtin, E.: Systems Architecting. Prentice-Hall, Englewood Cliffs (1991)Google Scholar
  44. 44.
    Standish Group: Extreme Chaos (2001),
  45. 45.
    Toulmin, S.: Cosmopolis. University of Chicago Press (1992)Google Scholar
  46. 46.
    Yang, Y., Bhuta, J., Port, D., Boehm, B.: Value-Based Processes for COTS-Based Applications. IEEE Software (2005) (to appear)Google Scholar
  47. 47.
    Yang, Y., Boehm, B.: A Contextualized Study of COTS-Based E-Service Projects. In: Proceedings, ICCBSS 2005 (February 2005)Google Scholar
  48. 48.
    Zachman, J.: A Framework for Information Systems Architecture. IBM Systems Journal (1987)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Barry Boehm
    • 1
  1. 1.University of Southern CaliforniaLos AngelesUSA

Personalised recommendations