Accurate estimates without local data?

Abstract

Models of software projects input project details and output predictions via their internal tunings. The output predictions, therefore, are affected by variance in the project details P and variance in the internal tunings T. Local data is often used to constrain the internal tunings (reducing T).While constraining internal tunings with local data is always the preferred option, there exist some models for which constraining tuning is optional. We show empirically that, for the USC COCOMO family of models, the effects of P dominate the effects of T i.e. the output variance of these models can be controlled without using local data to constrain the tuning variance (in ten case studies, we show that the estimates generated by only constraining P are very similar to those produced by constraining T with historical data).We conclude that, if possible, models should be designed such that the effects of the project options dominate the effects of the tuning options. Such models can be used for the purposes of decision making without elaborate, tedious, and time‐consuming data collection from the local domain. Copyright © 2009 John Wiley & Sons, Ltd.

Agile risk management using software agents

“…However introducing something new in an organization is difficult and likely to be costly. Menzies et al (2009) use the term 'data drought' to describe the situation where there is an unwillingness from organizations to share their operational data due to, among other factors, business sensitivity associated with the data. Given the difficulties of obtaining industrial data coupled with the ready availability of student project data in a university setting, student group projects were used in order to demonstrate and validate the approach.…”

GALE: Geometric Active Learning for Search-Based Software Engineering

“…The XOMO model [42]- [44] combines four software process models from Boehm's group at the University of Southern California. It reports four objective scores (which we will try to minimize): project risk; development effort and defects; and total months of development.…”

A second look at Faster, Better, Cheaper

“…We have used a tool called SEESAW [26,27] to explore the maxima and minima of attributes, avoiding intermediate attribute values. Looking at Fig.…”