Abstract
Reconsidering the relevancy of a frequently cited report on software project failures.
- Blum, B.I. Some very famous statistics. The Software Practitioner (Mar. 1991).Google Scholar
- Glass, R.L. IT failure rates---70 percent or 10--15 percent? IEEE Software 22, 3 (May--June 2005). Google ScholarDigital Library
- Jorgensen, M. and Molokken, K. How large are software cost overruns? A review of the 1994 Chaos Report. Information and Software Technology 48, 4 (Apr. 2006). Google ScholarDigital Library
- Standish Group International. The Chaos Report; www.standishgroup.com/sample_ research/PDFpages/Chaos1994.pdf.Google Scholar
Index Terms
- The Standish report: does it really describe a software crisis?
Recommendations
Report: The Second International Workshop on Software Engineering for CSE
Held during the 2009 International Conference on Software Engineering, this workshop provided a venue for software engineering researchers to interact with CSE researchers and practitioners and further strengthen the evolving dialogue between them. This ...
Technical report: the trend of author compound names and its implications for authorship identity identification
Citation analysis has become an essential tool for research and academic effectiveness evaluation of universities. However, authorship identity has long been difficult to resolve in bibliometric analyses for many scientific fields, where performance of ...
A report on software engineering education workshop
In this report, we present a summary and a few reflections of a one day workshop on Software Engineering Education held on February 22, 2012 at Indian Institute of Technology, Kanpur, India collocated with the 5th India Software Engineering Conference. ...
Comments