With the enormous improvements in the computers, software now pervades most facets of modern life. Software is now often the gating element in most branches of engineering and science. To formalize the developing of software and improving efficiency, the software engineering theory were rapidly developed in last decade's years.

Software process model is a framework, which defines a small number of activities applicable to all software projects, regardless of their size or complexity. This report describes one of software process model, Capability Maturity Model (CMM). CMM explains how to assess and improve software process maturity that based on 5-capability levels evolutionary path. It provides a framework for organizing these evolutionary steps into these maturity levels that lay successive foundations for continuous process improvement. These five maturity levels define an ordinal scale for measuring the maturity of an organization's software process and for evaluating its software process capability.

The five levels in the improvement model for software are de

How to improve software process is concerned by development organization. While there are many aspects to the advancement from one maturity level to another, the basic objective is to achieve a controlled and measured process, as the foundation for continuous. People should realize that it is a level-by-level work. According to the analysis by Watts Humphrey, first director of the SEI's Software Process Program, there are five steps to ascending the maturity of framework.

s they are faithfully followed. The project's process is under the effective control of a project management system, following realistic plans based on the performance of previous projects. The strength of the organization stems from its experience at doing similar work, but it faces major risks when presented with new challenges. The software process capability of Level 2 organizations can be summarized as disciplined because planning and tracking of the software project is stable and earlier successes can be repeated. The organization has frequent quality problems and lacks an orderly framework for improvement. If new tools and methods are introduced at this level without great care, it may do more harm than good.

Paulk, M., C. Weber, B. Curtis, and M. Chrissis, The Capability Maturity Model Guideline for Improving the software Process, Addison-Wesley, Reading, Mass., 1995

Optimising The organisation now has a foundation for continued improvement and optimization of process Improvement fed back into process Automation Productivity and QualityRisk

At different level, the organisation has different area that should be focused to improve its software process.

1. Understand the current status of their development process or processes.

At Defined Level (Level 3), there are four key steps to advance to the Level 4. First, a basic set of process measurements are needed to quantify the relative cost benefits of each major process e.g. the cost and yields of error detection and correction methods. Second, the establishment of a process database with the resources to manage and maintain it. Third, the organisation must provide sufficient funds to enable the collection and maintenance of the data. Fourth, to assess the relative quality of each product and inform management where the quality targets is being met.

The organizations at level 1 have the character of innormalized procedures. By studying management knowledge and guild by teacher, all group have build some formal project procedure, e.g. milestone, PERT chart, GANTT chart, etc. But it is just a beginning to the entrance of higher level. During the most period of project, the procedure is not strict processed according the scheduling, no mechanism are built to ensure that they are followed. Tools are not well integrated with the project process. Minutes of Meetings are often random arranged. Members just have a primary idea about project management model.

Some common words found in the essay are:
Organisation Level, Level Level, Management Unit, CMM CMM, QualityRisk Managed, Process Program, Maturity Introduction, Minutes Meetings, software process, Improve Level, project management, Result Optimising, software engineering, process capability, process improvement, level 1, level 5, maturity model, software development, level level, software process capability, process capability level, capability maturity model, software engineering practices, level 1 initial,
Approximate Word count = 2591
Approximate Pages = 10 (250 words per page double spaced)