Research And Practice Of Software Project Process Management Based On CMMI

After learning and practicing for six years, as a software engineering student and a practice software project and quality manager, I have experiences of many successful and aborted projects. I found out that systemic project management technology, establishing thinking pattern in process, cognizing the capabilities of our organization and sharing experience of historical projects are the effective methods of solving increasingly complicated project management problem.Along with the fast development of modern software industry, software has been frequently used as a kind of powerful tools, and software technique has developed as fast as possible. The importance of software project process management has been waken up to. The most important thing is not about technique, but the management of software product process. Mature management of software process could carry out the reuse of successful software process, the analyzing and summarizing of past experience and lessons, and the system editing and saving of all software development cases. Otherwise, the success of software development can only depend on artificial subjectivism or occasional factors. This is the background of this paper.The CMM/CMMI technology of the American Carnegie Mellon Software Engineering Institute (SEI) opened a new way for the software management project. The implementation of CMM/CMMI is not only making national software enterprises moving towards the world, but also raising management level of national software enterprises and reducing enterprises'project cost. In our country, more and more software companies promote their management capability and software quality through CMMI. These companies could have more opportunities and larger development space.First this paper expatiates the concept of CMM and CMMI, carries on the contrast research to the CMM and CMMI, tallies up the soul of CMM management idea and the improvement of CMMI. CMM, developed on the basis of CMM, is the important production is current software process improvements field. CMMI has two different denotation methods, different architecture with CMM. CMMI includes the thoughts of TQM (Total Quality Management), and provides standards for the process improvements of software companies. CMMI attaches more importance to requirement management, risk management, project process, reviews and so on. Compare with CMM used as appraisal standard, CMMI is used as improving model. CMMI enumerates best practices, which benefits for improving of process.Then, this paper introduced software project process management. What software process management mentioned is not only advance technique and development methods, but also whole sets of management methods, which emphasize on is some management methods such as requirement management, project arrangement, contract criterion, project tracking, resource distribution, quality requirement and so on. The research objects of software development process management include three aspects. They are controlling and continuance improving of software development process capability, organizing and learning from software development process, and auspice of cooperating with process management system as architecture. Favorable software project process management has many benefits. It's absolutely necessarily.The risk management and the review, which are the parts of CMMI emphasizing, are occupying importance positions in software project process management. Effectual risk management and review process could increase the succeed rate of project, boost up the haleness of teams, assure achievement of project with good quality on schedule. Therefore, according to the material condition of practiced company, this paper improve on the management process to adapt the needing of fact and future development, from two sides of risk management and review.About the risk management, firstly, this paper introduced three kinds of commonly used risk management model. They respectively are the Barry Boehm model, the CRM model and the Leavitt model. Then, this paper compared these three models. The Barry Boehm model and the CRM model emphasize durative risk management with process as principal part. The Leavitt model has conducted the research from the system view to the risk management. It carries on the research with software project as a holistic system and with the duty, the structure, the role and the technology as its subsystem. The procedure risk management and the system view risk management are in fact two directions to the risk management, these are longitudinal and crosswise. In these three models, the CRM model is a kind of dynamic risk management theory. It pays great attention to close union with the software development process. It has strong feasibility.Therefore, colligating Boehm model and Leavitt model, according to CRM model of SEI, the risk management is divided to risk identifying, risk analyzing, risk planning, risk tracking and risk controlling, and intercommunion as core. First, project manager organizes the project member to determine risk control parameters such as the possible risk origin, the risk category, risk control values and so on. These risk control parameters must have the high-level manager's authorization. When identifying risk, project manager organizes the project member to distinguish the latent problems which possibly have adverse effect to the work or the work plan, recognize the risk related with the cost, the schedule and the performance, appraise the environment element which possibly affect the project. In the process of the project implementation, risk must be identified again regularly of event-driven. The way which project manager used to mark and describe the identified risk must be easy to understand. Afterward, risk analyzing is needed. According to the risk category, project manager classify the risks and ensure risk priority. In risk planning stage, risk mitigation plan is developed. Project manager organizes the project member to appraise every risk. According to the step of risk planning and decision-making flow chart, they choose some method to deal with risks. In tracking and control risk stage, project manager tracks the risks weekly. Based on the project evolving and risk tracking situation, there may be possibility to identify the risk over again.About the review, owing KPA peer review in CMM corresponds PA verification and PA validation, this paper introduced concept of the verification and the validation, and difference between them. The verification ensures that"you built it right."The validation ensures that "you built the right thing."The review is the most important way to carry on the validation and the verification. The review includes the peer review, signing off by reviewers and approval. The peer review includes walkthrough, technical review and inspection. When doing walkthrough, the author distributes the review materials to reviewers. Reviewers inspect review materials. Only when necessity, there is a discussion between reviewers. When doing technical review, project manager must work out the review plan. The reviewers inspect products independently, and record the check result. When doing inspection, project manager works out the inspection plan and prepare to organize inspection preparation meeting. Reviewers inspect products independently, and record the check result. Then, project manager organizes inspection meeting. When signing off by reviewers, correlative personnel sign their notion by the fashion of passing round for perusal. When doing approval, the author gives the approved product to the approvers. The approvers sign their names to certificate. According to the difference between different review modes, the different products corresponds their corresponding review modes.As internationally at present an most popular and the most practical software process improvement standard, CMMI can help the software companies to manage and improve the software engineering process, enhance the capability of development and improvement. Therefore these companies can develop high quality software punctually with no ultra budget. But there is a problem that many companies need to solve urgently. That is how to fuse CMMI and companies'actual situation and discover the management way to suit the companies.Overpass the research of the risk management and the review's localization and instantiation, combined with the practice company's actual situation, the software project process management methods based on CMMI, which adapt national software enterprises, are discovered. It may make slender contribution for the development of Chinese software industry. In the future, the research will be continued. There will be unceasing advancement in the way of process improvement.