Early Identification of SE-Related Program Risks

Abstract : The mission of the DoD Systems Engineering Research Center (SERC) is to perform research leading to transformational SE methods, processes, and tools (MPTs) that enable DoD and Intelligence Community (IC) systems to achieve significantly improved mission successes. An elevator speech for the capabilities delivered by the Department of Defense (DoD) Systems Engineering Research Center (SERC) Systems Engineering (SE) Effectiveness Measurement (EM) task reads as follows: for the DoD, whose Major Defense Acquisition Programs (MDAPs) frequently and significantly overrun their budgets and schedules and deliver incomplete systems, the SERC SE EM framework, operational concepts, and tools will empower MDAP sponsors and performers to collaboratively determine their early SE shortfalls and enable the development of successful systems within their resource constraints. Unlike traditional schedule-based and event-based reviews, the SERC SE EM technology enables sponsors and performers to agree on the nature and use of more effective evidence-based reviews. These enable early detection of missing SE capabilities or personnel competencies with respect to a framework of Goals, Critical Success Factors (CSFs), and Questions determined by the EM task from the leading DoD early-SE CSF analyses. The EM tools enable risk-based prioritization of corrective actions, as shortfalls in evidence for each question are early uncertainties, which when combined with the relative system impact of a negative answer to the question, translates into the degree of risk that needs to be managed to avoid system overruns and incomplete deliveries.

[1]  Leonard E. Miller,et al.  NASA systems engineering handbook , 1995 .

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

[3]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[4]  Khaled El Emam,et al.  A Survey of Systems Engineering Effectiveness , 2007 .

[5]  Andraž Cej,et al.  Agile software development with Scrum , 2010 .

[6]  Barry Boehm,et al.  Detecting model clashes during software systems development , 2003 .

[7]  Khaled El Emam,et al.  A Survey of Systems Engineering Effectiveness - Initial Results (with detailed survey response data) , 2008 .

[8]  H. D. Rombach,et al.  THE EXPERIENCE FACTORY , 1999 .

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

[10]  U. Asendorf,et al.  3.a–e , 1998 .

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

[12]  Walker Royce,et al.  The Economics of Iterative Software Development: Steering Toward Better Business Results , 2009 .

[13]  Paul J. Componation,et al.  ASSESSING THE RELATIONSHIPS BETWEEN PROJECT SUCCESS , AND SYSTEM ENGINEERING PROCESSES , 2008 .

[14]  Barry Boehm,et al.  8.3.1 The Macro Risk Model: An Early Warning Tool for Software‐Intensive Systems Projects , 2008 .

[15]  John J. Marciniak,et al.  Encyclopedia of Software Engineering , 1994, Encyclopedia of Software Engineering.

[16]  U. Asendorf 2.a–c , 1998 .

[17]  Paul J. Componation,et al.  A Preliminary Assessment of the Relationships Between Project Success, System Engineering, and Team Organization , 2008 .

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

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

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

[21]  Barry Boehm,et al.  Avoiding the Software Model-Clash Spiderweb , 2000, Computer.

[22]  Paul Clements,et al.  Models for Evaluating and Improving Architecture Competence , 2008 .

[23]  V. D.,et al.  Prof , 1973 .

[24]  J.P. Elm,et al.  A Study of Systems Engineering Effectiveness - Initial Results , 2008, 2008 2nd Annual IEEE Systems Conference.

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

[26]  Barry Boehm,et al.  Adjusting Software Life-Cycle Anchorpoints: Lessons Learned in a System of Systems Context , 2009 .

[27]  Donna H. Rhodes,et al.  SYSTEMS ENGINEERING LEADING INDICATORS GUIDE , 2007 .