Quantitative process management (QPM) and causal analysis and resolution (CAR) are requirements of capability maturity model (CMM) levels 4 and 5, respectively. They indicate the necessity of process improvement based on objective evidence obtained from statistical analysis of metrics. However, it is difficult to achieve these requirements in practice, and only a few companies have done so successfully. Evidence-based 2 risk-management methods have been proposed for the control of software processes, but are not fully appreciated, compared to clinical practice in medicine. Furthermore, there is no convincing answer as to why these methods are difficult to incorporate in software processes, despite the fact that they are well established in some business enterprises and industries. In this paper, we challenge this issue, point out a problem peculiar to software processes, and develop a generally applicable method for identifying the risk of failure for a project in its early stages. The proposed method is based on statistical analyses of process measurements collected continuously throughout a project by a risk assessment and tracking system (RATS). Although this method may be directly applicable to only a limited number of process types, the fundamental idea might be useful for a broader range of applications.Keywords logistic model, risk assessment, software process, statistical analysis, yore, temodori 3
1.IntroductionThe software application field has been expanding dramatically, and the software development process has become more complex, resulting in an ever-increasing demand for reliable software. (De Lacalle et al., 2002;Maydl, 2004; Ingham et al., 2005) The environment in which software development currently takes place is more challenging than conducive to success, and the demand for skilled and experienced managers is increasing (Pfahl et al, 2003;Ellis et al, 2004). Moreover, software development technology changes every few years, thereby limiting the availability of expert managers.Consequently, it is becoming increasingly difficult to develop a product of the required quality within a specified time frame (Kang et al, 2005), which may have serious effects on software manufacturers, vendors, and users. Therefore, how to produce a high-quality system in a timely manner is one of the most critical and important themes of project management.Discussing this issue, Bieman (2004) argued: "The only hope for making informed design decisions leading to systems that remain high-quality and adaptable is to improve the ability of designers to prognosticate. Rather than use a crystal ball, comprehensive studies of how existing systems have evolved in the past can provide solid evidence into the 4 connection between early design decisions and the evolving adaptability and quality of software systems. ……We can improve our ability to perform relevant prognostication only with a much deeper understanding of how systems have evolved."This argument seems relevant to a recent software glitch that troubled the...