New processes for new horizons: the incremental commitment model

The wide variety of software-intensive systems needed to support the new horizons of evolving technology, system and software complexity, high dependability, global interoperability, emergent requirements, and adaptability to rapid change make traditional and current one-size-fits-all process models infeasible. This tutorial presents the process framework, principles, practices, and case studies for a new model developed and being used to address these challenges. It has a series of risk-driven decision points that enable projects to converge on whatever combination of agile, plan-driven, formal, legacy-oriented, reuse-oriented, or adaptive processes that best fit a project's situation. The tutorial discusses the decision table for common special cases; exit ramps for terminating non-viable projects; support of concurrent engineering of requirements, solutions and plans; and evidence-based commitment milestones for synchronizing the concurrent engineering. The tutorial will include case studies and exercises for participants' practice and discussion.

[1]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

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

[3]  BoehmBarry,et al.  Using the WinWin Spiral Model , 1998 .

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

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

[6]  Walker Royce Software Project Management , 1998 .

[7]  Walker Royce,et al.  Software Project Management: A Unified Framework , 1998 .

[8]  Barry Boehm,et al.  System of systems lead system integrators: Where Do they spend their time and what makes them more or less efficient? , 2008 .

[9]  Barry W. Boehm,et al.  Making a Difference in the Software Century , 2008, Computer.

[10]  Philippe Kruchten,et al.  What Is the Rational Unified Process ? , 2001 .

[11]  David M. Weiss,et al.  Architecture reviews: practice and experience , 2005, IEEE Software.

[12]  Richard W. Pew,et al.  Human-system integration in the system development process : a new look , 2007 .

[13]  Barry Boehm,et al.  The ROI of systems engineering: Some quantitative results for software-intensive systems , 2008 .

[14]  Barry W. Boehm Unifying Software Engineering and Systems Engineering , 2000, Computer.

[15]  Jo Ann Lane,et al.  A Model of Systems Engineering in a System of Systems Context , 2009 .

[16]  Mikael Lindvall,et al.  Evaluating software architectures , 2004, Adv. Comput..

[17]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[18]  Barry Boehm,et al.  Modern Tools to Support DoD Software Intensive System of Systems Cost Estimation , 2007 .

[19]  Barry Boehm,et al.  Using the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering , 2007 .

[20]  Eating the IT Elephant: Moving from Greenfield Development to Brownfield , 2008 .

[21]  Barry W. Boehm,et al.  Balancing Opportunities and Risks in Component-Based Software Development , 2008, IEEE Software.

[22]  Barry Boehm,et al.  21st Century Processes for Acquiring 21st Century Software-Intensive Systems of Systems , 2006 .