The Development And Research Of Stage Process Modeling Based On CMMI And Its Supporting Platform

Software engineering practice has already been proved that only depending on traditional software engineering process and method is unable to solve problems such as project progress much exceeding the time limit, budget being out of expectation, low automatization, process being hard to control and customer satisfaction not being high. In 1993, the research institute of the American Carnegie-Mellon University Software Engineering Institute (SEI/CMU) released a Capacity Maturity Model (CMM1.1 version) for software processes, and in 2002 the institue formally released the CMMI-SE/ SW1.1 that solves problem mainly by managing software processes. First of all, it ascertains the process capability of the software organization, then bases on the capability, it chooses and uses the effective management and technical practice, such kind of practice is composed of software engineering processes which is disciplined, accurately defined and efficiently measured, its purpose is to produce high-quality software products under the costs and progresses request. Based on the model, we use the methods of modern software engineering to combines the internal drive with exterior control, which not only develops the visibility of the software engineering processes, but also emphasizes the position and effects of people having been neglected in the software engineering processes before. Thereby, the problems confronted in the software organizations can be well solved. On the basis of analyzing and researching the domestic and international current situation and existing problem, this paper focuses on the key practice of two stages in software lifecycle combining with CMM/CMMI, i.e., â‘ The process of Software requirement; â‘¡The process of change control in software configuration management. The CMM model provides a stepwise improvement frame for the process capability of the software enterprise. It is divided into 5 maturity grades in all. The requirement engineering as a key process field in the second-grade of CMM has the close contact with the others in the second-grade. The requirement engineering can not only support all the requirements, but also map the requirement changes into each activity of the project plan, and carry out tracking and controlling the requirement processes. According to this, this paper advances a CMM-Based Requirement process Model (CBRM) which bases on customers, it classifies the customers, solves various problems in the requirement engineering by them, shortens the time of the requirement development, raises the quality of the requirement management, and makes sure that the developers can get the customers' requirement. At the same time the model has joined with the existent research, and gives other requirement engineering problems happened currently with solutions. We developed a platform for requirement development and the management (SCBRM) based on that model. The target is, through the control with role definition, process definition, process-flow and file-flow management, and the role's behaviors in the activities of requirement management, to coincide the requirement processes controlled in the software life cycle with the software plan, product and activities. The whole model complies with the unification of the inner drive and the exterior control. The customers drive the inner drive and the project group exerts the exterior control, so the requirement development and the management flow can achieve the load balance. In the support activities of the software quality system, SCM plays a central role; it is one of the core concepts of CMM/CMMI quality management systems. The purpose of SCM is to guarantee that products producing from software project maintain integrality in software lifecycle; Software alternative management is in central position of SCM. Big problems has been existing in the SCM changing control for a long time, the main problem lies in being lack of reliable data quantization supports for changing decision and analyze processes. This paper analyzes present condition and shortages of current alteration management, combining with data quantifiable method of COCOMOâ…¡it proposes a changing quantification model based on COCOMOâ…¡. This model implements quantization processes through classification (e.g. developer, group, project and enterprise): the former one hands over the quantifiable data to the latter one, providing data supports for the latter's quantification. Thereby, the project managers can clearly analyze how the current change affects the activity detail, parts and whole, thus perfect the regulating mechanism of organizing process model. The model not only carries on the decision of whether to change, but also provides data supports to the implement of the alteration, tracing and the risk control. Changing quantification systems (CQS) developed by the model can support the implementation on the whole model. The system can automatically wiretap the changing of the requirements, strengthen cooperation of the internal member of CCB, checking the history record of the change of configuration and the former similar data, work out changing decision analyse record and changing track plan record. The CQS usage speeds the changing decision analysis progress. The two aspects discuss in this paper are not only two important stages of the software development lifecycle, but also two important key fields in the second grade of the model of CMM/ CMMI. The two build the core of the software quantity system. They contact and restrict each other, we can say that only after resolving the change control problem of requirement and configuration, we can assure the quality system...