![]() ![]() Humphrey based this framework on the earlier Quality Management Maturity Grid developed by Philip B. The result of the Air Force study was a model for the military to use as an objective evaluation of software subcontractors' process capability maturity. Department of Defense in evaluating the capability of software contractors as part of awarding contracts. Air Force he began formalizing his Process Maturity Framework to aid the U.S. Development at Software Engineering Institute Īctive development of the model by the US Department of Defense Software Engineering Institute (SEI) began in 1986 when Humphrey joined the Software Engineering Institute located at Carnegie Mellon University in Pittsburgh, Pennsylvania after retiring from IBM. Watts Humphrey began developing his process maturity concepts during the later stages of his 27-year career at IBM. ![]() Nolan, who, in 1973 published the stages of growth model for IT organizations. ![]() The first application of a staged maturity model to IT was not by CMU/SEI, but rather by Richard L. In an effort to determine why this was occurring, the United States Air Force funded a study at the Software Engineering Institute (SEI). In the 1980s, several US military projects involving software subcontractors ran over-budget and were completed far later than planned, if at all. Individuals such as Edward Yourdon, Larry Constantine, Gerald Weinberg, Tom DeMarco, and David Parnas began to publish articles and books with research results in an attempt to professionalize the software-development processes. Many processes for software development were in their infancy, with few standard or " best practice" approaches defined.Īs a result, the growth was accompanied by growing pains: project failure was common, the field of computer science was still in its early years, and the ambitions for project scale and complexity exceeded the market capability to deliver adequate products within a planned budget. ![]() Organizations began to adopt computerized information systems, and the demand for software development grew significantly. In the 1980s, the use of computers grew more widespread, more flexible and less costly. ( August 2016) ( Learn how and when to remove this template message) Relevant discussion may be found on the talk page. This section possibly contains synthesis of material which does not verifiably mention or relate to the main topic. Though the model comes from the field of software development, it is also used as a model to aid in business processes generally, and has also been used extensively worldwide in government offices, commerce, and industry. It was later published in a report in 1993 and as a book by the same authors in 1995. The model is based on the process maturity framework first described in IEEE Software and, later, in the 1989 book Managing the Software Process by Watts Humphrey. The Capability Maturity Model was originally developed as a tool for objectively assessing the ability of government contractors' processes to implement a contracted software project. In 2006, the Software Engineering Institute at Carnegie Mellon University developed the Capability Maturity Model Integration, which has largely superseded the CMM and addresses some of its drawbacks. The model's aim is to improve existing software development processes, but it can also be applied to other processes. The term "maturity" relates to the degree of formality and optimization of processes, from ad hoc practices, to formally defined steps, to managed result metrics, to active optimization of the processes. Department of Defense, who funded the research. The Capability Maturity Model ( CMM) is a development model created in 1986 after a study of data collected from organizations that contracted with the U.S. Assessment of software development processes ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |