On a way to strengthen the practice of software project management model

Abstract: This article is a careful analysis of the domestic software Project Management problems, in order to improve software quality, reduce costs, enhance the controllability of the software project as the goal, in-depth study and discussion based on the combination of CMM software process. Strengthen the software presents a practical model of Project Management. The model defines the practice of CMM key process in the six domains and three working groups. And from the project's Development time and quality to do efficiency analysis, software process highlighted the importance of software Project Management.

Paper Keywords: software projects, software process, CMM, KPA
1. Introduction
Project Management (PM, projectmanagement) is the use of existing knowledge, methods and techniques, effective planning, scheduling, control and track the start of the project, implementation, until the end of the process is an effective means to achieve the project successfully. Software Project Management is the foundation in project management, combined with the actual software products, the use of Engineering concepts and methods to develop and maintain the software, cost, risk, time, quality, processes, configuration, analysis, management, control, may ultimately purpose is to allow the entire life cycle of software projects are within the control of managers to predetermined cost schedule, quality and completion of software Development and delivery to users. Currently, the software has been widely used in various fields, but many software projects The success rate was not high. While some companies under the theory of software Engineering management practices of some software Development. But did not fundamentally improve software project management issues, which led to instability and even the quality of software products, the failure of the project, but also damages the user's interests. In this paper, the characteristics of software project management and by practical application. To improve software quality, reduce costs, enhance the controllability of the software project as the goal, through Research and improvement of CMM, we give a CMM-based software project management practices to enhance model, in this model in the current CMM KPA make the appropriate cuts, the definition of the six key process areas and three working groups.

2. Software project management problems in the current
Success rate of software projects is the main factor software quality problems, and in the process of implementing software projects demand is not clear, tracking and poor supervision, lack of objective assessment of software risk management and software configuration and lack of awareness of software quality and so hinder improved.

2.1 Requirements not clear
Demand management is a critical project management software a step. Complete needs analysis or to reduce software quality, extend the project cycle, and increase costs. Because users lack of knowledge of computer systems, the demand for the system are often vague, missing or even wrong problems often arise (including management processes, business process, analysis and processing of data or statements, etc.), but these issues are often not exposed to developers, but as the project progresses gradually clear. For developers, the demand for change means that part of the software products must be re- Development, and for the entire software project management is concerned, it is bound to re-allocate resources, adjust the plan, estimated cost, etc., leading to decline in the quality of software products.

2.2 Tracking and poor supervision
Mainly for tracking and monitoring process, that is a project management aspects of the most easily overlooked. Software project process constituted by a number of tasks, most tasks have pre-and post-mission tasks, which requires project managers to strictly tracking and monitoring each task. task completion time schedule and quality, mainly from two aspects to measure, but also take full account of client side caused by a number of objective factors (change needs analysis, etc.). Although the project managers to develop a specific project progress content, but if the lack of effective tracking and monitoring mechanisms, for each stage of the evaluation of the task neglect, it will affect the quality of the next phase of software products, and sometimes even re-Development of software products, and ultimately affect the entire software projects.

2.3 The lack of objective assessment of software
The software is an objective assessment of the quality of the direct protection of software products, software review software project has been throughout the process, the assessment of software products and software should customers use industry counterparts to carry out. Customers who make the software product periodic review of software products can function to detect the deficiency of peer review available from the software industry norms and standards to find the problem. Software evaluation can reduce the cost of software development to improve software product quality. Most of the cases the project manager did not make any periodic review, usually only in software product development was basically completed the accreditation, results identified a number of problems, but to modify has been very difficult. Take a long time or even start from scratch.

2.4 Software configuration confusion
Software configuration refers to software products in various stages of the various versions of the files, programs and data collection throughout the entire software project from beginning to end. As for the software product development, due to various objective reasons, including budget, design, progress and so are likely to need large and small changes (these changes may be reasonable), the whole process of change in personnel on the software project is to be visible in order to improve software reliability and quality, which All should have the right software configuration to control if they lose the right software configuration management, then the place for software products or maintain any changes to the software project will bring chaos and even a failure.

Lack of awareness of risk management 2.5
Software project risk management is an important means to prevent failure, different stages of software project there are different risks, and risks will change as the project progresses, most of domestic software enterprises pay no attention to software project risk management. In addition to social environmental risk, business risk and other risks outside of these objective. Control of software project risk mainly refers to Technology risk. Technology risk mainly refers to the software project itself changes in technical factors related to the risks, if certain conditions are issued in less than technical conditions to achieve the goal, not only delay the project progress and will increase the cost of the project. In turn affected the entire project.

3. Process management through strengthening the practice of software project management model
Using cMM fCapabilityMaturityModeforSoftware) The core idea of ​​the software project management as a software process, and in accordance with the principles of the entire software project development and management of process monitoring, and supervision of projects in the discovery process and the key issues to be addressed. Software process refers to the software developers to develop and maintain software and related products, a code of conduct, methods, practice and transformation process, including software development and software management process. CMM to software development according to different levels of development agencies is divided into five levels. each level be broken down into several KPA (key process areas), KPA refers to a maturity level should focus on the region, reached the maturity level of this key point that must be addressed. �� the initial stage, no process of meaning. software process is disordered, random, and the lack of master plan, no foresight, most of the activities is to meet the crisis, often extended overruns, success depends on individuals. �� repeatable level, basic project management. KPA are: demand management, software project planning, software tracking and oversight, software subcontract management, software quality assurance, software configuration management, �� the defined level, the defined software process. has software management and software Engineering aspects of the process of documentation, standardization, and comprehensive into the organization's standard software process. KPA are: organizational process focus, organization process definition, training program, integrated software management, software Engineering, group coordination, peer review, �� manageable level, the process can be measured. have been collected software process and product quality measurement methods in detail, the software processes and products can be quantitatively understood and controlled. KPA are: quantitative process management, software quality management, �� optimization level, process control. quantified through the process of feedback and new technologies and new methods to promote the process of continuous improvement. KPA are: defect prevention, Technology updates prevention, process change management.

CMM is a process improvement framework. Did not give a specific implementation approach. In this mode, in the current CMM KPA to make the appropriate cuts. Defines the six key process areas: software project planning (SPP), requirements management (RM), software project tracking and oversight (SPTO), Software Quality Assurance (SQA), software configuration (SCM), peer review (PR), set three working groups: Software Project Process Group (SPPG), Software Engineering Group (SEG), software quality assurance group (SQAG). through the working Group on the operation of the key process areas to strengthen the management of software projects.

3.1 Definition KPA
3.1.1 Software Project Plan (SPP)
Software project planning software for project preparation to the implementation of software process activities, including the schedule control, cost control, quality control, risk control, but also the core of the implementation of CMM2 arrangements at this stage in the process of project design activities, while the preliminary work carried out , design and define the different stages throughout the project development, quality, tracking, assessment, risk, cost and so on. project plan to guide the project process, concrete measures to implement in a software project under the leadership of experienced personnel input a lot of time and human resources to complete. to develop the project plan should pay attention to 7 questions. �� on a scientific basis of the development process, to fully mobilize the staff motivation is reasonable assurance that the project team participants, �� the software projects the process of task decomposition, a clear project milestones and checkpoints, �� accurately estimate software project software resources, hardware resources, human resources and other costs, �� accurately estimate the risks of various factors and to develop response measures, �� develop project implementation The tracking and monitoring measures, �� determine software review and testing methods, �� detailed documentation. reposted elsewhere in the Research Papers Download http://www.hi138.com 3.1.2 Requirements Management (RM)
User-oriented requirements analysis including user needs and system requirements for developers. The first step in the entire software engineering. A link is also very critical. Needs analysis focused on the user's business processes, system functionality, performance, data analysis, a strict definition. Is to design a software application system starting with the fundamental basis, through which to judge whether the software product to solve user problems, but also the project success criteria. To the current domestic situation is concerned, the general users signed a contract software projects is in charge of information person in charge of Technology, it may be of concern to the entire system of target demand, the user side is concerned about middle management business process needs. Terminal operators will focus on the software itself is easy operability and functionality, so. For the needs of users and users of multi-party personnel must communicate, communicate. Final arguments by the parties to relevant personnel in the form of documentation finalized. Any of the requirements analysis for objective reasons, there may need to change the phenomenon, we must pay attention to this situation needs to change the controllable. To create demand and change the base version of version control documentation. Affected by changes in the demand for the product line and needs to change. But to pay attention to the needs of the changing needs of both to measure the stability, if a requirements change more frequently, meaning that the project did not really understand the user wants to solve the practical problems . can be said that the integrity of requirements analysis and change directly affect the controllability of the software process improvement, it can reduce the software quality, increase the cost of software development, and even lead to project failure. Software Engineering Group (SEG) is necessary to clear administrator to define a requirement.

3.1.3 software project tracking and oversight (SPTO)
Software project tracking and monitoring software runs through the entire course of the project, a project to control the premise and condition, is the fundamental guarantee of software quality, the aim is to increase the progress of the software process, cost, workload, quality, risk the visibility of the content, but also the core of the implementation of CMM2. remove the market, legal and other uncontrollable factors, according to the progress of the project plan the project of the situation and related factors affect the implementation of the project for timely, objective and accurate information collection, the collected to the demand, cost, schedule, risk, etc. to form a project tracking document and information platform. Project Manager software process convened regularly, developers, quality assurance personnel, the user side the officer held a regular meeting open, the main regular content is to check the project progress, data analysis, understanding of bias, with the resources, the related risks and other issues and discuss the exact solutions by tracking and monitoring of the project is always in a controlled state visualization.

3.1.4 Software Quality Assurance (SQA)
Software quality assurance is provided with the software product to meet the needs and capacity of the hidden features or characteristics of the combination. Of users mainly in terms of the effectiveness of software products, consistency, integrity, reliability and operability, etc. respect for the software product itself, embodied in the software products in terms of portability, maintainability, robustness, reusability, and so on. concrete practice. Software quality assurance should be in the software project planning, needs analysis, tracking and oversight, software configuration and software complement each other to complete the review. Software quality assurance to do to advance the prevention and tracking based, supplemented by later correction.

3.1.5 software configuration (SCM)
Software configuration is for software tracking and control activities. Software project throughout the process. Aim is to establish and maintain throughout the life cycle of software product integrity and consistency, so that the evolution of the software product under control of the state, and then improve software reliability and quality. In practical application to achieve the five main sub- �� configuration item configuration item identification. identity be unique. to facilitate tracking and management. �� version management. on the entire software process files and directories to provide an effective means of tracking. �� change control. to maintain and modify the information transfer. �� configuration audit. identify the product throughout the project cycle management in the Technology and integrity. �� system integration. the integration of different parts of the system to complete a specific set of features.

3.1.6 Peer Review (PR)
Peer review is based on predetermined norms and standards for software product evaluation. The medical assessment is the basis for measuring the quality of software products. Throughout the course of the detailed software design and software integration testing as the two key evaluation point for review, review Process of the combination of the software project to the specific requirements and standards.

3.2 The definition of
Practical application in the specific set of three groups of personnel in reducing costs while increasing capabilities of software process improvement and software quality.

Software Project Process Group (SPPG) organized the implementation of specific project activities, manage and coordinate the whole process of software projects, mainly to complete SPP and SPTO.

Software Engineering Group (SEG) is responsible for software engineering, requirements analysis, preliminary design, detailed design, coding, testing, maintenance.

Software Quality Assurance Group (SQAG) mainly to complete SPTO, SCM, PR, SQA and so on.

4. Efficiency Evaluation of Practice Model
4.1 The development time
Software development from the requirements analysis, preliminary design, detailed design, coding, software testing, project maintenance, and software integration of several component parts, demand analysis and design phases in the CMM framework of the implementation by management not to spend more time than the implementation of process management time spent. First of all do a lot of analysis of the project, demonstrate the feasibility of the project. and then make good communication and the user repeatedly made on the basis of demonstrated needs analysis, the formation of documentation. This mode takes the requirements analysis and design The total time of roughly 40% of development time, but the two stages of the data flow, algorithm description, detailed specifications, etc., for coding, software testing, software maintenance and other follow-up work to save the contents of the time, the software shorten the project development cycle. After assessment, the use of the mode of implementation of the software process practice management software project development cycle than those without the implementation of software process management software project development cycle shortened by 20%.

4.2 Development Quality
By using the standard CMM software process management to enhance the practice of software project management model to significantly improve software quality, needs careful analysis, the code error rate significantly decreased, software product integrity is good, functional decline in maintenance, software project finally smoothly.

5. Conclusion
In this paper, the adoption of software process management to enhance the practice of software project management model is very obvious advantages. Software process improvement targeted, can effectively improve software quality and save development time and reduce costs. Meanwhile, the model better reflect the team spirit, get rid of the software development of individualism, a holistic approach, emphasizing the overall importance of the process at the same time, further reducing risks in the software process, so that software projects always in the fine visual controlled state.

Links to Research Papers Download http://www.hi138.com