Software capability maturity model

See Software Capability Maturity Model (CMM) for additional related information. 

SSE-CMM—System Security Engineering Capability Maturity Model, June 15, 2003, in line with ISO 15504-2 (SPICE) and CMM-I (following the processes and maturity level concept, but for security engineering instead of software development) (not safety application-specific)... 

PauUt, M.C. (1995), The Evolution of SETs Capability Maturity Model for Software, Software Processes — Improvement and Practice, 3-15. 

The Capability Maturity Model (CMM) was originally developed as a tool for objectively assessing the ability of government contractors processes to perform a contracted software project. The CMM is based on the Process Maturity Framework first described in Managing the Software Process by Watts Humphrey and later published in its full form as a book named The Capability Maturity Model Guidelines for Improving the Software Process in 1994 by Mark Paulk, Charles Weber, Bill Curtis, and Mary Beth Chrissis. 

Paulk M, Weber C, Curtis B, Chrissis M (1994) The Capability Maturity Model Guidelines for Improving the Software Process. Addison-Wesley Professional Saaty T, Vargas L (2006) Decision making with the analytic network process economic, political, social and technological applications with benefits, opportunities, costs and risks, 1st edn. Springer, New York... 

Examples of good software practices include following lEC 61508-3 or Capability Maturity Model (CMM) and ensuring the software processes are controlled under the manufacturer quality management system (example ISO 9001 2008). 

NOTE 2 Capability Maturity Model (CMM) was developed by the Software Engineering Institute (SEI) at Carnegie Mellon University in Pittsburg, PA, USA. The SEI developed a set of best practices and an assessment method for the development, verification, and validation of complex software models. 

Software Engineering Inst. 1991. Capability Maturity Model. Carnegie-Mellon University Pittsburgh, PA. 

Models have been developed to characterize the quality of software development processes in industries. The capability maturity model (Paulk et al, 1993) is one such model. The CMM has five different levels, each of which distinguishes an organization s software process capability ... 

Capability Maturity Model Integration (CMMI) project was formed to sort out the problem of using multiple models for software development processes thus, the CMMI has superseded the CMM, though the CMM continues to be a general theoretical process capability model used in the public domain. 

Although CMM houses the best practices of the industry, it does not address the human part of the industry which is of paramount importance in human capital industry like that of IT and allied sectors. To enable this, a People Capability Maturity Model (P-CMM) [5] has also been proposed. The P-CMM can be used as a framework for improving the way in which an organization manages its human assets. The P-CMM also shares the same five levels of maturity as that of CMM although the KPAs that constitute these levels (20 KPAs) are focussed on the human counterpart rather than the software quality. 

Hunter R, Thayer R, Paulk M. The capability maturity model for software, software process improvement. Hoboken WUey-IEEE Press 2001. p. 49-88. 

In 1999 A joint Health and Safety Executive (HSE) and oil industry-funded project to address some of these concerns led to the development of a Safety Culture Maturity Model (SCMM) (see for example Lardner, Fleming and Joyner (2001). The SCMM is based on the capability maturity model concept, initially developed by the Software Engineering Institute of CarnegieMellon University (Paulk et al, 1993), as a mechanism to improve the way software is built and maintained. The SCMM aims to assist organisations in (a) establishing their current level of safety culture maturity and (b) identifying the actions required to improve their safety culture. 

According to Wikipedia, The United States Air Force funded a study at the Camegie-Mellon Software Engineering Institute to create a model for the military to use as an objective evaluation of software subcontractors. The result was the Capability Maturity Model (CMM) which has been superseded by the more comprehensive Capabihty Maturity Model Integration (CMMI). 

Capability Maturity Model Integration (CMMI) It is a process improvement approach that provides organizations with the essential elements of effective processes. It was developed by the SEI (Software Engineering Institute) at Carnegie Mellon University in Pittsburgh. 

Software CMM is the application of the CMM to the development of software. There are five CMM levels, as shown in Figure 2.78, and at each higher level, the organization is able to develop better software on a cost-effective basis. See Capability Maturity Model (CMM) for additional related information. 

The competitiveness of the chemistry software market also shows up in the recent mergers and consolidations of vendors as they try to achieve a critical mass and market share. Accretion is one way the software companies struggle to stay competitive in a maturing market. In addition, we see several vendors repositioning their products from narrow applications to become general molecular modeling tools. Programs that started out to do only quantum chemistry now find it necessary to have molecular mechanics and other capabilities to be competitive. 

CAPE OPEN standards have been developed to the state of maturity where standards are finding application in industrial and academic applications. The need for further standards has been identified as well as sustaining existing standards. To be successful standards also need to be maintained and supported. Developments in applying, extending and maintaining software interoperability standards to expand Process Modelling Capability will be presented. 

---