Sciweavers

ICSE
2009
IEEE-ACM

How to avoid drastic software process change (using stochastic stability)

14 years 6 months ago
How to avoid drastic software process change (using stochastic stability)
Before performing drastic changes to a project, it is worthwhile to thoroughly explore the available options within the current structure of a project. An alternative to drastic change are internal changes that adjust current options within a software project. In this paper, we show that the effects of numerous internal changes can out-weigh the effects of drastic changes. That is, the benefits of drastic change can often be achieved without disrupting a project. The key to our technique is SEESAW, a novel stochastic stability tool that (a) considers a very large set of minor changes using stochastic sampling; and (b) carefully selects the right combination of effective minor changes. Our results show, using SEESAW, project managers have more project improvement options than they currently realize. This result should be welcome news to managers struggling to maintain control and continuity over their project in the face of multiple demands for drastic change.
Tim Menzies, Steve Williams, Barry W. Boehm, Jairu
Added 20 May 2010
Updated 20 May 2010
Type Conference
Year 2009
Where ICSE
Authors Tim Menzies, Steve Williams, Barry W. Boehm, Jairus Hihn
Comments (0)