Research And Application Of Requirement Management Based On The Priority

Information industry has developed rapidly over ten years, the complexity of software projects is increasing and the scale is also growing, which result in unsuccessful project increasing, how to improve the success rate of software projects has become a problem to be solved. The success of the project depends on many factors, requirement is a very important part in software development, effective management for it will produce a very direct impact on project.This paper studies the current process of software project management, puts forward a method based on priority to manage the requirement. Requirement management as the core of the priority, which try to go deep into the software project management process, improve the efficiency of management and promote the success of the project.This paper first introduces the background of ship maintenance management system, upon learning requirement management may be the difficulty of the project. In order to improve the success rate of the project, to avoid possible risks during the project, the paper studies on the traditional requirement management project, then summarize good experiences and methods,meanwhile review Analytic Hierarchy Process, apply it to the requirement of the priority ranking, establish priority requirement evaluation model. Specifically for the requirement of priority-based ranking algorithm, it improves requirement management methods, formulates treatment program when requirement changed. In project, after comprehension and analysis the requirement of the ship maintenance management system, it applies the evaluation model and requirement management methods, uses the AHP to calculate various requirements of the weights,according to this weight to schedule and adjust the time and speed of the project. The ship maintenance management system gets the user’s praise after the on-line, success of the project verified correctness and feasibility of this method.In this paper, using quantitative results to guide leadership, to solve the drawbacks of traditional software project management process determined by experience, to ensure the reasonableness of each decision. to minimize the possible impact. Under the complexity of the project, disagreement of the key users and the lack of requirement management experience of the team, it can effectively reduce the divergence, determine development baseline, ensure the project’s development and success.