Cmm Capability Maturity Model

1213 Words5 Pages
List of Acronyms CMM Capability Maturity Model Intergration CMM Capability Maturity Model SEI Software Engineering Institute SEIG Software Engineering Institute Group SPI Software Process Improvement SPI Software CDC Coega Development Corporation IDZ Industrial Development Zone ABSTRACT The software Process Capability Maturity Model (CMM) deals with the capability of software organizations to consistency and predictably produces high quality products. (Watts.S.H) 1993). According to Watts.S.H the drive for improved software quality is motivated by technology, customers need at that time, regulation and composition he mentioned that although industry’s historical quality improvement focus has been on manufacturing, software…show more content…
According to (Aaen, et. 2005) Software Process Improvement way of thinking encourages software engineers and managers to look beyond the software they are developing, and to consider the way in which they work together and coordinate their efforts. Software development process requires continuous improvement in order to build successful and quality products. The more organized and quality oriented a process is, the better products companies will produce and deliver. (ZAHOOR UL ISLAM XIANZHONG ZHOU) mentioned that the complexity of the new process can make it not easy to organize and manage process efficiency that could perform all the tasks in parallel and…show more content…
The main objectives of software process improvement is to set methods in order to improve the development process including project management prompting and managing requirement, decision making, measuring performance and also plan the work.( Karl E. Wiegers ) Factors affecting Software Process Improvement Before any organization can decide on improving its processes there are many factors that must be taken in to consideration. There are factors can therefore be identified and believed that are very critical for the organizations that have started their process improvement programs in the past decade. Culture and customs (Tim Kasse) mentioned that culture ca be seem obvious to people but not knowing that it is understated and can have massive influence on the way we think in our daily lives. It does not only affect the development and improvement of software but also everyday morale of work force in the organization. . (Ngwenyama and Nielson) mentioned that failure rate for SPI initiatives are too high. They further mention that such failure is based on the following reasons or arguments by various authors (Ngwenyama and
Open Document