Some future trends and implications for systems and software engineering processes

In response to the increasing criticality of software within systems and the increasing demands being put onto 21st century systems, systems and software engineering processes will evolve significantly over the next two decades. This paper identifies eight relatively surprise-free trends—the increasing interaction of software engineering and systems engineering; increased emphasis on users and end value; increased emphasis on systems and software dependability; increasingly rapid change; increasing global connectivity and need for systems to interoperate; increasingly complex systems of systems; increasing needs for COTS, reuse, and legacy systems and software integration; and computational plenty. It also identifies two “wild card” trends: increasing software autonomy and combinations of biology and computing. It then discusses the likely influences of these trends on systems and software engineering processes between now and 2025, and presents an emerging scalable spiral process model for coping with the resulting challenges and opportunities of developing 21st century software-intensive systems and systems of systems. © 2006 Wiley Periodicals, Inc. Syst Eng 9:

[1]  David A. Patterson.  20th century vs. 21st century C&C: the SPUR manifesto , 2005, CACM.

[2]  Mark R. Wademan,et al.  The People Capability Maturity Model , 2008 .

[3]  LiGuo Huang,et al.  A Value-Based Process for Achieving Software Dependability , 2005, ISPW.

[4]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[5]  Edsger W. Dijkstra,et al.  Software Engineering : As It Should Be , 1979, International Conference on Software Engineering.

[6]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[7]  Harold R. Booher,et al.  Handbook of Human Systems Integration , 2003 .

[8]  W. Arthur,et al.  Increasing returns and the new world of business. , 1996, Harvard business review.

[9]  E. Rechtin,et al.  The art of systems architecting , 1996, IEEE Spectrum.

[10]  Alfonso Fuggetta,et al.  Software process: a roadmap , 2000, ICSE '00.

[11]  Janis R. Putman,et al.  Architecting with RM-ODP , 2000 .

[12]  Pelle Ehn,et al.  Work-oriented design of computer artifacts , 1989 .

[13]  Stefan Biffl,et al.  Stakeholder Value Proposition Elicitation and Reconciliation , 2006, Value-Based Software Engineering.

[14]  Barry Boehm,et al.  Spiral Acquisition of Software-Intensive Systems of Systems , 2004 .

[15]  Barry Boehm,et al.  The Spiral Model as a Tool for Evolutionary Acquisition , 2001 .

[16]  Barry W. Boehm,et al.  A Contextualized Study of COTS-Based E-Service Projects , 2005, ICCBSS.

[17]  Barry Boehm,et al.  Balancing agility and discipline , 2004 .

[18]  Barry W. Boehm,et al.  Improving quality through software process improvement in Thailand: initial analysis , 2005, WoSQ@ICSE.

[19]  Watts S. Humphrey,et al.  Introduction to the Personal Software Process , 1996 .

[20]  D. Thomas King,et al.  Mind over Machine. , 1978 .

[21]  Chris Peterson,et al.  Unbounding the Future: The Nanotechnology Revolution , 1991 .

[22]  Paul Pomerantz,et al.  Good to great. , 2004, Plastic and reconstructive surgery.

[23]  Judith Scott Clayton,et al.  The Future , 2001, Nature.

[24]  Diane Crawford.  Editorial pointers , 2003, CACM.

[25]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[26]  Joy Bill,et al.  Why the future doesn’t need us , 2003 .

[27]  Barry W. Boehm,et al.  Value-based software engineering: reinventing , 2003, SOEN.

[28]  Robert B. Grady,et al.  Successful Software Process Improvement , 1997 .

[29]  David Lorge Parnas,et al.  Review of David L. Parnas' "Designing Software for Ease of Extension and Contraction" , 2004 .

[30]  A. Maslow.  Motivation and Personality , 1954 .

[31]  Dee W. Hock.  Birth of the Chaordic Age , 2000 .

[32]  Watts S. Humphrey,et al.  Introduction to the Team Software Process , 1999 .

[33]  R. J. Rubey,et al.  Quantitative aspects of software validation , 1975, IEEE Transactions on Software Engineering.

[34]  J. Gray.  Information Technology Research: Investing in Our Future , 1999 .

[35]  Barry W. Boehm,et al.  An Initial Theory of Value-Based Software Engineering , 2006, Value-Based Software Engineering.

[36]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[37]  Daniel Noah Port,et al.  Balancing Discipline and Flexi-bility with The Spiral Model and MBASE , 2001 .

[38]  Lisa Brownsword,et al.  Evolutionary Process for Integrating COTS-Based Systems (EPIC): An Overview , 2002 .

[39]  Daniel Roos,et al.  The machine that changed the world : the story of lean production , 1991 .

[40]  James P. Womack,et al.  Lean Thinking: Banish Waste and Create Wealth in Your Corporation , 1996 .

[41]  Barry W. Boehm,et al.  Value-based processes for COTS-based applications , 2005, IEEE Software.

[42]  Gregory Howell,et al.  The Underlying Theory of Project Management Is Obsolete , 2008, IEEE Engineering Management Review.

[43]  Amr Elssamadisy,et al.  Recognizing and responding to "bad smells" in extreme programming , 2002, ICSE '02.

[44]  Mladen A. Vouk.  Software Reliability Engineering , 1999 .

[45]  Neil Thompson,et al.  Risk Based E-Business Testing , 2002 .

[46]  Leonard J. Bass,et al.  Linking usability to software architecture patterns through general scenarios , 2003, J. Syst. Softw..

[47]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[48]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[49]  P. Kidwell,et al.  Darwin Among the machines: The evolution of global intelligence , 1999, IEEE Annals of the History of Computing.

[50]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[51]  Vladan Devedzic,et al.  Software Project Management , 2001 .