CMM (Capability Maturity Model) is a 1987 Carnegie Mellon University's Software Engineering Institute (SEI) Capability Maturity Model proposed framework, through the implementation of CMM, software companies can not only improve productivity, decreased error rate of software products, also improve the credibility of the company.
With many years of experience in the implementation of CMM that small and medium software enterprises in the implementation of CMM should be based on their own conditions and specific requirements to be applied, and from the following considerations:
I. the role of primary organizations and arrangements
, if an organization to improve its performance, then senior management must actively support the change. from the bottom up reform, not high-level support and recognition of higher level, but able to complete the transformation, which is almost non- possible.
recommended the establishment of Software Engineering Process Group (SEPG), as the coordination process definition, improvement and deployment activities, not necessarily full-time SEPG staff, but should be clearly assigned to the person responsible. CMM requirement for some roles, can be flexible, do not be too rigidly stick. small projects may not require special software configuration management group, but the configuration management activities are essential; independent quality assurance team may be unnecessary, but someone to complete the verification activities. project team members play multiple roles, such as project managers can also act as the role of SCM, but testers can also assume the role of SQA.
Second, the implementation strategy
SMEs in the implementation of CMM process, organizational support is the foundation, strategy is are the steps to effective implementation of the glue, not because it is too cumbersome or affect the progress of sake.
One is the process of documentation. If enterprises do not have a documented software process, the first to sum up the experience of the past success of the project, the current work flow analysis, compilation and documentation to develop a process for the enterprise software and software projects with the guidance of the development process.
second is the process of cutting. the process needed to be cropped to the project extent, this is also small and medium enterprises to implement CMM key process improvement. cut is all the criteria be practical, to avoid too cumbersome and formal.
The third is to organize training. the organization of training for all staff to complete the company, including senior managers the most basic knowledge of software engineering and CMM training. so that all employees understand the CMM, to support the implementation of CMM.
three, steps
1. demand management
1) to obtain the original requirements from the customer, the After analyzing the formation of the software requirements specifications, customers receive written approval;
2) Software Requirements Specification review by the project team, adding configuration management, creating demand for the baseline;
3) of demand through the table to track the development status of to understand the needs of the achievement;
4) For change requests, should fill out the the basis for project tracking and monitoring, can be implemented by following these steps:
1) project manager to estimate according to demand, development of software development plans and schedules;
2) Software Development Plan project team must review and higher authorities approval, approval by, add configuration management.
3. software project tracking and monitoring
1) Project managers use as a tracking and monitoring schedule based on the actual week of the project implementation progress reports prepared and confirmed with the project team members;
2) project managers plan and control the actual implementation, identify gaps and problem report form;
3) senior managers review the project report urged the project managers plan and amendments to solve existing problems and risks.
4. software quality assurance
1) If a full-time SQA, to develop specific quality assurance program;
2) SQA process of implementation according to plan and review audit work products submitted, the problem of inconsistent record ;
3) will find the problem records to the project issues log, track and coordination problems, and to report regularly to the project manager and senior manager. If you can not be resolved by the senior managers to help solve.
5. software Configuration Management
1) If a full-time SCM, you can develop specific configuration management plan;
2) create a development domain and the baseline domain, developers in their work on the development field, SCM identifies the configuration item and include the baseline domain;
3) SCM at the end of each stage to create a baseline configuration items and baselines for the audit;
4) baseline configuration item change request field in the first project manager, proposed a unified operation from the SCM and records;
5) quality assurance personnel regularly audit the configuration management activities.
6. peer review
1) review the project manager to determine the personnel, time and place of the relevant material will be distributed to reviewers;
2 ) reviewers before the meeting carefully read these materials and record the problems identified;
3) If sufficient time, the meeting suggested ways to communicate with, or submitted by the project team members found their own problems;
4) Summary found problems, the project manager designated staff to track to solve the problem.
No comments:
Post a Comment