Can we build software faster and better and cheaper?

"Faster, Better, Cheaper" (FBC) was a development philosophy adopted by the NASA administration in the mid to late 1990s. that lead to some some dramatic successes such as Mars Pathfinder as well as a number highly publicized mission failures, such as the Mars Climate Orbiter & Polar Lander. The general consensus on FBC was "Faster, Better, Cheaper? Pick any two". According to that view, is impossibly to optimize on all three criteria without compromising the third. This paper checks that view using an AI search tool called STAR. We show that FBC is indeed feasible and produces similar or better results when compared to other methods However, for FBC to work, there must be a balanced concern and concentration on the quality aspects of a project. If not, "FBC" becomes "CF" (cheaper and faster) with the inevitable lose in project quality.

[1]  Barry W. Boehm,et al.  How to avoid drastic software process change (using stochastic stability) , 2009, 2009 IEEE 31st International Conference on Software Engineering.

[2]  R. Showstack Better, faster, cheaper , 1997 .

[3]  Karen T. Lum,et al.  The Deviance Problem in Effort Estimation , 2006 .

[4]  Tim Menzies,et al.  Simple software cost analysis: safe or unsafe? , 2005, PROMISE '05.

[5]  Ian Witten,et al.  Data Mining , 2000 .

[6]  Marcel Korte,et al.  Confidence in software cost estimation results based on MMRE and PRED , 2008, PROMISE '08.

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

[8]  Tim Menzies,et al.  Feature subset selection can improve software cost estimation accuracy , 2005, ACM SIGSOFT Softw. Eng. Notes.

[9]  Yue Jiang,et al.  Comparing design and code metrics for software quality prediction , 2008, PROMISE '08.

[10]  C. D. Gelatt,et al.  Optimization by Simulated Annealing , 1983, Science.

[11]  Daniel Ryan Baker,et al.  A Hybrid Approach to Expert and Model Based Effort Estimation , 2007 .

[12]  Barry W. Boehm,et al.  Accurate Estimates without Calibration? , 2008, ICSP.

[13]  Michael Carr,et al.  Mars Program Independent Assessment Team Report , 2000 .

[14]  N. Fenton,et al.  Project Data Incorporating Qualitative Factors for Improved Software Defect Prediction , 2007, Third International Workshop on Predictor Models in Software Engineering (PROMISE'07: ICSE Workshops 2007).

[15]  Karen T. Lum,et al.  Selecting Best Practices for Effort Estimation , 2006, IEEE Transactions on Software Engineering.

[16]  Burak Turhan,et al.  Implications of ceiling effects in defect predictors , 2008, PROMISE '08.

[17]  Barry W. Boehm,et al.  Bayesian Analysis of Empirical Software Engineering Cost Models , 1999, IEEE Trans. Software Eng..

[18]  Tim Menzies,et al.  Feature Subset Selection Can Improve Software Cost Estimation , 2005 .

[19]  Barry W. Boehm,et al.  The business case for automated software engineering , 2007, ASE.

[20]  Tim Menzies,et al.  Simple Software Cost Estimation: Safe or Unsafe? , 2005 .

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

[22]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[23]  Tim Menzies,et al.  The Strangest Thing About Software , 2007, Computer.

[24]  Barry W. Boehm Safe and Simple Software Cost Analysis , 2000, IEEE Software.

[25]  Tim Menzies,et al.  Incremental Discreatization and Bayes Classifiers Handles Concept Drift and Scaled Very Well , 2005 .