Font Size: a A A

A quantitative analysis of the Carnegie Mellon Software Engineering Institute's Capability Maturity Model: A latent variable model

Posted on:2001-07-20Degree:Ph.DType:Dissertation
University:City University of New YorkCandidate:Chang, ShaomingFull Text:PDF
GTID:1468390014956364Subject:Computer Science
Abstract/Summary:
The Capability Maturity Model developed by Carnegie Mellon University's Software Engineering Institute (SEI/CMM) was the most commonly used method for enhancing software development/maintenance processes in the 1990s. The focus of SEI/CMM's research is to build a common production function for each of the five maturity levels (I to V) by comparing the behavior of the production functions of each level and then assessing the advantages and disadvantages of each production function for advancing the organization's maturity level.; This research chose the Latent Variable Model (LVM) to fit the production function because in the world of software engineering, models must frequently be compromised or modified to reflect the sampled data. By introducing latent variables we could reproduce the most typical practical production environment. The LVM we studied is composed of the following two group of variables: (1) tangible variables, that is, sampled data (Function point, Duration, Man month, Team size); (2) intangible variables, that is, latent variables (Management effort, Production process).; We also study Dr. Frederick Brooks' Man month myth among the five maturity levels. To analyze the differences, we then used the COCOMO model with an additional Team size factor. Does the Team size overhead go away at higher maturity levels or does it tag along? One of the purposes of this study was to find an answer. To conclude the Production function, the Dynamic model was used.
Keywords/Search Tags:Model, Software engineering, Maturity, Production function, Latent, Used
Related items