Some future trends and implications for systems and software engineering processes

Systems Engineering

Volumn 9, Issue 1, 2006, Pages 1-19

  Boehm, Barry ^a,b,c,d,e,f  

^a University of Southern California ^*  (United States)

^b ACM   (United States)

^c AIAA   (United States)

^d IEEE   (United States)

^e IEEE ^*  (United States)

^f NATIONAL ACADEMY OF ENGINEERING   (United States)

Author keywords

Future trends; Human systems integration; Software engineering; Spiral model; Systems acquisition; Systems architecting; Systems engineering; Systems of systems; Value based processes

Indexed keywords

FUTURE TRENDS; HUMAN SYSTEMS INTEGRATION; SPIRAL MODEL; SYSTEMS ACQUISITION;

COMPUTER SOFTWARE; LARGE SCALE SYSTEMS; MATHEMATICAL MODELS; SYSTEMS ENGINEERING;

SOFTWARE ENGINEERING;

EID: 33644684772     PISSN: 10981241     EISSN: 15206858     Source Type: Journal    
DOI: 10.1002/sys.20044     Document Type: Review

References (83)

1. C. Albert and L. Brownsword, Evolutionary process for integrating COTS-based systems (EPIC): An overview, CMU/SEI-20030TR-009, Software Engineering Institute, Pittsburgh, PA, 2002.
2. G. Anthes, The future of IT, Computerworld (March 7, 2005), 27-36.
3. W.B. Arthur, Increasing returns and the new world of business, Harvard Bus Rev (July/August 1996), 100-109.
4. V. Basili, M. Zelkowitz, F. McGarry, J. Page, S. Waligora, and R. Pajerski, Special Report: SEL's process-improvement program, Software (November 1995), 83-87.
5. L. Bass and B.E. John, Linking usability to software architecture patterns through general scenarios, J Syst Software 66(3) (2003), 187-197.
6. K. Beck, Extreme programming explained, Addison Wesley, Reading, MA, 1999.
7. S. Biffl, A. Aurum, B. Boehm, H. Erdogmus, and P. Gruenbacher (Editors), Value-based software engineering, Springer, New York, 2005.
8. B. Boehm, Software engineering economics, Prentice Hall, Englewood Cliffs, NJ, 1981.
9. B. Boehm, A spiral model for software development and enhancement, Computer (May 1988), 61-72.
10. B. Boehm, Anchoring the software process, Software (July 1996), 73-82.
11. B. Boehm and W. Hansen, The spiral model as a tool for evolutionary acquisition, CrossTalk (May 2001), 4-11.
12. B. Boehm and C.A.R. Hoare (Editors), Proceedings, 1975 International Conference on Reliable Software, ACM/IEEE, New York, April 1975.
13. B. Boehm and A. Jain, "An initial theory of value-based software engineering," Value-based software engineering, A. Aurum, S. Biffl, B. Boehm, H. Erdogmus, and P. Gruenbacher (Editors), Springer, New York, 2005.
14. B. Boehm and D. Port, Balancing discipline and flexibility with the spiral model and MBASE, CrossTalk (December 2001), 23-28.
15. B. Boehm and R. Turner, Balancing agility and discipline, Addison Wesley, Reading, MA, 2004.
16. B. Boehm, A.W. Brown, V. Basili, and R. Turner, Spiral acquisition of software-intensive systems of systems, CrossTalk (May 2004), 4-9.
17. B. Boehm, A. Egyed, J. Kwan, D. Port, A. Shah, and R. Madachy, Using the WinWin Spiral Model: A case study, IEEE Comput (July 1998), 33-44.
18. H. Booher.(Editor), Handbook of human systems integration, Wiley, New York, 2003.
19. F. Brooks, The mythical man-month (2nd edition), Addison Wesley, Reading, MA, 1995.
20. P. Checkland, Systems thinking, systems practice (2nd edition), Wiley, New York, 1999.
21. H. Chesbrough, Open innovation, Harvard Business School Press, Cambridge, MA, 2003.
22. M.B. Chrissis, M. Konrad, and S. Shrum, CMMI, Addison Wesley, Reading, MA, 2003.
23. C. Christensen, The innovator's dilemma, Harvard Business School Press, Cambridge, MA, 1997 and Harper Collins, New York, 2000.
24. A. Cockburn, Agile software development, Addison Wesley. Reaing, MA, 2002.
25. J. Collins, Good to great, Harper Collins, New York, 2001.
26. D. Crawford, Editorial pointers, Commun ACM (October 2001), 5.
27. M. Crichton, Prey, Harper Collins, New York, 2002.
28. B. Curtis, B. Hefley, and S. Miller, The people capability maturity model, Addison Wesley, Reading, MA, 2002.
29. M. Cusumano and R. Selby, Microsoft secrets, Harper Collins, New York, 1996.
30. M. Deck, M. Strom, and K. Schwartz, The emerging model of co-development, Res Technol Management (December 2001).
31. T. DeMarco, Slack, Broadway Books, 2001.
32. E. Dijkstra, Panel remarks, Software Engineering: As It Should Be, ICSE 4 (September 1979), see also EWD 791 at http://www.cs.utexas/users/EWD.
33. E.K. Drexler, Engines of creation, Anchor Press, 1986.
34. K.E. Drexler, C. Peterson, and G. Pergamit, Unbounding the future: The nanotechnology revolution, William Morrow, 1991.
35. H. Dreyfus and S. Dreyfus, Mind over machine, Macmillan, New York, 1986.
36. L. Druffel, N. Loy, R. Rosenberg, R. Sylvester, and R. Volz, Information architectures that enhance operational capability in peacetime and warfare, USAF-SAB Study Report, U.S. Air Force, Washington, DC, February 1994.
37. G.B. Dyson, Darwin among the machines: The evolution of global intelligence, Helix Books/Addison Wesley, Reading, MA, 1997.
38. P. Ehn (Editor), Work-oriented design of computer artifacts, Earlbaum, 1990.
39. A. Elssamadisy and G. Schalliol, Recognizing and responding to "bad smells" in extreme programming, Proc Twenty-Fourth Int Conf Software Eng (ICSE2002), Orlando, FL, May 2002, pp. 617-622.
40. FCIO (Federal CIO Council), A practical guide to federal enterprise architecture, Version 1.0, FCIO, Washington, DC, February 2001.
41. A. Fuggetta, "Software process: A roadmap," The future of software engineering, A. Finkelstein (Editor), ACM Press, 2000.
42. P. Gerrard and N. Thompson, Risk-based e-business testing, Artech House, 2002.
43. R. Grady, Successful software process improvement, Prentice Hall, Englewood Cliffs, NJ, 1997.
44. P. Gruenbacher, S. Koeszegi, and S. Biffl, "Stakeholder value proposition elicitation and reconciliation," Value-Based Software Engineering, A. Aurum, S. Biffl, B. Boehm, H. Erdogmus, and P. Gruenbacher (Editors), Springer, New York, 2005.
45. D. Harned and J. Lundquist, What transformation means for the defense industry, McKinsey Quart (November 3, 2003), 57-63.
46. J. Highsmith, Adaptive software development, Dorset House, 2000.
47. D. Hock, Birth of the Chaordic Age, Berrett-Koehler, 1999.
48. G. Hofstede, Culture and organizations, McGraw Hill, New York, 1997.
49. L. Huang, A value-based process achieving software dependability, Proc Software Process, Workshop 2005, May 2005.
50. W. Humphrey, Introduction to the personal software process, Addison Wesley, Reading, MA, 1997.
51. W. Humphrey: Introduction to the team software process, Addison Wesley, Reading, MA, 2000.
52. INCOSE, Systems engineering technical vision, Draft Version 1.5, INCOSE, June 2005.
53. ISO (International Standards Organization), Standard for information technology - software life cycle processes, ISO/IEC 12207, ISO, 1995.
54. ISO (International Standards Organization), Systems engineering - system life cycle processes, ISO/IEC 15288, ISO, 2002.
55. B. Joy, Why the future doesn't need us, Wired (April 2000).
56. L. Koskela and L. Howell, The underlying theory of project management is obsolete, Proc PMI Res Conf, 2002, pp. 293-302.
57. P. Kroll and P. Kruchten, The rational unified process made easy: A practitioner's guide to the rational unified process, Addison Wesley, Reading, MA, 2003.
58. R. Kurzweil, The age of spiritual machines, Penguin, New York, 1999.
59. A. Maslow, Motivation and personality, Harper and Row, New York, 1954.
60. G. Moore, Inside the tornado, Harper Collins, New York, 1995.
61. J. Musa, Software reliability engineering, McGraw Hill, New York, 1999.
62. D. Parnas, Designing software for ease of extension and contraction, Trans Software Eng IEEE SE-5, 1979.
63. D. Patterson, 20th century vs. 21st century C&C: The SPUR manifesto, Commun ACM (March 2005), 15-16.
64. M. Paulk, C. Weber, B. Curtis, and M. Chrissis, The Capability Maturity Model, Addison Wesley, Reading, MA, 1994.
65. M. Phongpaibul and B. Boehm, Improving quality through software process improvement in Thailand: Initial analysis, Proc ICSE 2005 Workshop Software Qual, May 2005.
66. PITAC (President's Information Technology Advisory Committee), Report to the President: Information technology research: Investing in our future, PITAC, Washington, DC, 1999.
67. J. Putman, Architecting with RM-ODP, Prentice Hall, Englewood, Cliffs, NJ, 2001.
68. Rational, Inc., Driving better business with better software economics, Rational Software Corp (now part of IBM), 2001.
69. E. Rechtin, Systems architecting, Prentice Hall, Englewood Cliffs, NJ, 1991.
70. E. Rechtin and M. Maier, The art of systems architecting, CRC Press, Boca Raton, FL, 1997.
71. D. Reifer and B. Boehm, A model contract/subcontract award fee plan for large, change-intensive software acquisitions, USC Center for Software Engineering, University of Southern California, Los Angeles, April 2003.
72. A. Rosenbloom, 3D hard copy, Commun ACM (June 2005), 32-35.
73. W.E. Royce, Software project management, Addison Wesley, Reading, MA, 1998.
74. J.R. Rubey, J.A. Dana, and P.W. Biché, Quantitative aspects of software validation, IEEE Trans SW Eng (June 1975), 150-155.
75. Standish Group, Extreme chaos, http://www.standishgroup.com, 2001.
76. S. Toulmin, Cosmopolis, University of Chicago Press, Chicago, IL, 1992.
77. U.S. Department of Defense (USD), MIL-STD-1521B: Reviews and audits, USD, Washington, DC, 1985.
78. U.S. Department of Defense (USD), DOD-STD-2167A: Defense system software development, USD, Washington, DC, 1988.
79. J. Womack and D. Jones, Lean thinking: Banish waste and create wealth in your corporation, Simon & Schuster, New York, 1996.
80. J.P. Womack, D.T. Jones, and D. Roos, The machine that changed the world: The story of lean production, Harper Perennial, New York, 1990.
81. Y. Yang, J. Bhuta, D. Port, and B. Boehm, Value-based processes for COTS-based applications, IEEE Software (July/August 2005), 54-62.
82. Y. Yang, B. Boehm, and D. Port, A contextualized study of COTS-based e-service projects, Proc Software Process Workshop 2005, Springer, New York, 2005, to appear.
83. J. Zachman, A framework for information systems architecture, IBM Syst J (1987).