Issue No. 02 - February (2000 vol. 33)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/2.820036
In the early 1980s, the<p> US Department of Defense suffered many monetary, schedule, and performance costs because it misjudged the ability of its contractors to develop software. Recognizing that this was less a reflection on the organizations themselves than on the general immaturity of the soft-ware industry, the DoD helped create the Software Engineering Institute with the aim of studying ways to help the software industry grow responsibly. </p> <p>In 1987, the SEI established the software capability evaluation (SCE) as a formal way to determine an organization's software process maturity framework and generally measure its software development competence. SCEs are widely used to determine an organization's Capability Maturity Model rating, but their results can be misleading. The authors reveal how certain practices distort results and waste time and money, through intentional contractor vagueness and detail, inappropriate sample projects, and staff coaching. They go on to suggest ways to improve the process. </p>
H. Saiedian and E. O'Connell, "Can You Trust Software Capability Evaluations?," in Computer, vol. 33, no. , pp. 28-35, 2000.