The Future of Software and Systems Engineering Processes

In response to the increasing criticality of software within systems and the increasing demands being put onto software-intensive systems, software and systems 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 leg- acy systems and software integration; and computational plenty. It also identifies two "wild card" trends: in- creasing software autonomy and combinations of biology and computing. It then discusses the likely influences of these trends on software and systems engineering processes between now and 2025, and presents an emerg- ing three-team adaptive process model for coping with the resulting challenges and opportunities of developing 21 st century software-intensive systems and systems of systems.

[1]  Barry W. Boehm,et al.  Anchoring the Software Process , 1996, IEEE Softw..

[2]  Walker Royce.  Software Project Management , 1998 .

[3]  Philippe Kruchten,et al.  The Rational Unified Process Made Easy - A Practitioner's Guide to the RUP , 2003, Addison Wesley object technology series.

[4]  Bill Curtis,et al.  The People Capability Maturity Model , 2001 .

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

[6]  A. Blaxill.  The future of it , 2003 .

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

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

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

[10]  Barry W. Boehm,et al.  Improving quality through software process improvement in Thailand: initial analysis , 2005, ACM SIGSOFT Softw. Eng. Notes.

[11]  Gerard O’Regan,et al.  The Capability Maturity Model , 2002 .

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

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

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

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

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

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

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

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

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

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

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

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

[24]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .

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

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

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

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

[29]  K. Eric Drexler,et al.  Engines of Creation , 1986 .

[30]  Barry Boehm.  Balancing Discipline and Flexibility , 2001 .

[31]  James Emery.  Adaptive software development: an experience report , 2001 .

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

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

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

[35]  G. H. Anthes.  The future of IT , 2005 .

[36]  Eberhardt Rechtin,et al.  The Art of Systems Architecting, Second Edition , 2000 .

[37]  Mike Featherstone,et al.  Cosmopolis , 2002 .

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

[39]  Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[40]  George B. Dyson.  Darwin among the Machines: The Evolution of Global Intelligence , 1997 .

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

[42]  R. Kurzweil.  The age of spiritual machines: when computers exceed human intelligence , 1998 .

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

[44]  G. Hofstede.  Culture and Organizations , 1980 .

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

[46]  John D. Musa,et al.  Software Reliability Engineering , 1998 .

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

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

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

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

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

[52]  H. Dreyfus.  Mind Over Machine , 1986 .

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

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