An empirical approach to characterizing risky software projects based on logistic regression analysis

Empirical Software Engineering

Volumn 10, Issue 4, 2005, Pages 495-515

  Takagi, Yasunari ^a,b   Mizuno, Osamu ^b,c,d   Kikuno, Tohru ^b,c,d,e  

^a OMRON CORPORATION   (Japan)

^b OSAKA UNIVERSITY   (Japan)

^c IEEE   (Japan)

^d ACM   (Japan)

^e IPSJ   (Japan)

Author keywords

Logistic regression; Questionnaire; Risky project; Software risk management

Indexed keywords

LOGISTIC REGRESSION; QUESTIONNAIRE; RISKY PROJECTS; SOFTWARE RISK MANAGEMENT;

COMPUTER SIMULATION; DATA REDUCTION; KNOWLEDGE ACQUISITION; MATHEMATICAL MODELS; MATRIX ALGEBRA; REGRESSION ANALYSIS; RISK ASSESSMENT;

SOFTWARE ENGINEERING;

EID: 26044464061     PISSN: 13823256     EISSN: 15737616     Source Type: Journal    
DOI: 10.1007/s10664-005-3864-z     Document Type: Conference Paper

References (20)

1. Basili, V. R., Briand, L. C., and Melo, W. L. 1996. A validation of object oriented metrics as quality indicators. IEEE Transactions on Software Engineering 22(10): 751-761.
2. Boehm, B. W. 1987. Industrial software metrics top 10 list. IEEE Software 4(5): 84-85.
3. Briand, L. C., Basili, V. R., and Hetmanski, C. 1993. Developing interpretable models with optimized set reduction for identifying high risk software components. IEEE Transactions on Software Engineering 19(11): 1028-1044.
4. Conrow, E. H., and Shishido, P. S. 1997. Implementing risk management on software intensive projects. IEEE Software 14(3): 83-89.
5. Fairley, R., and Rook, P. 1997. Risk management for software development. In Software Engineering. Los Alamitos, CA: IEEE CS Press, pp. 387-400.
6. Fenton, N. E., and Pfleeger, S. L. 1997. Software Metrics : A Rigorous & Practical Approach, PWS Publishing.
7. Humphrey, W. S. 1995. A Discipline for Software Engineering, Maryland: Addison Wesley.
8. Humphrey, W. S. 2001. Winning with Software: An Executive Strategy. Maryland: Addison-Wesley.
9. Jiang, J., and Klein, G. 2000. Software development risks to project effectiveness. Journal of Systems and Software 52: 3-10.
10. Jones, C. 1993. Assessment and Control of Software Risks. Englewood Cliffs, NJ: Prentice Hall, Inc.
11. Karolak, D. W. 1996. Software Engineering Risk Management. California: IEEE CS Press.
12. Kasser, J., and Williams, V. R. 1998. What do you mean you can't tell me if my project is in trouble? DoD Software Tech News 2(2). http://www.dacs.dtic. mil/awareness/newsletter/technews2-2/trouble.html
13. Mizuno, O., Kikuno, T., Inagaki, K., Takagi, Y., and Sakamoto, K. 1998. Analyzing effects of cost estimation accuracy on quality and productivity. In Proceedings of 20th International Conference on Software Engineering, pp. 410-419.
14. Mizuno, O., Kikuno, T., Inagaki, K., Takagi, Y., and Sakamoto, K. 2000a. Statistical analysis of deviation of actual cost from estimated cost using actual project data. Information and Software Technology 42: 465-473.
15. Mizuno, O., Kikuno, T., Takagi, Y., and Sakamoto, K. 2000b. 'Characterization of risky projects based on project managers' evaluation. In Proceedings of 22nd International Conference on Software Engineering. pp. 387-395.
16. Munson, J., and Khoshgoftaar, T. 1992. The detection of faultprone programs. IEEE Transactions on Software Engineering 18(5): 423-433.
17. Ropponen, J., and Lyytinen, K. 2000. Components of software development risk: How to address them? A project manager survey. IEEE Transactions on Software Engineering 26(2): 98-112.
18. Sisti, F. J., and Joseph, S. 1994. Software risk evaluation method version 1.0. Technical Report CMU/SEI94TR19, Software Engineering Institute.
19. Williams, R. C., Pandelios, G. J., and Behrens, S. G. 1999. Software risk evaluation (SRE) Method Description (Version 2.0). Technical Report CMU/SEI99TR029, Software Engineering Institute.
20. Yourdon, E. 1997. Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects. Englewood Cliffs, NJ: Prentice-Hall Computer Books.