Telecom Audit Management System Project Demand Management Study

In this dissertation, a research has been made on the requirements management for the project of Telecom Internal Audit Management System(TIAMS).First, a brief overview of the background and the necessity of the study on the requirements management for the project TIAMS has been described, followed by some basic theories about requirements management for software project, especially about the software requirements management methods of CMMI. Then try to introduce the strategic research methods on priority taxis of enterprise businesses in order to understand the important impact on the project by the software requirements management from a strategic point of view. These methods are used as theoretical basis of the requirements management study for the project TIAMS.Second, a detailed analysis of the characteristics of the project TIAMS has been made and the requirements management policy and strategy for it has been put forward.In order to help the project team having a better implementation methods on the requirements management for the project TIAMS, a method for the requirements management, Requirements Priority Taxis (RPT), which aims at the project TIAMS was introduced.Third, use these methods described above to make a detailed study about the requirement source management, requirement scope management, requirement analysis management, requirement change management, requirement status and traceability management in the start-up phase of TIAMS.Finally, with the project practices, an analysis was made about the specific impact on the project organization, the project critical path, the cost of the project, the progress of the project by using these above-mentioned requirements management methods.In this paper the contribution is to introduce the strategic decision analysis methods on the priority taxis of enterprise businesses to software project requirements management, and conduct the project team dealing with the software project requirements management from a strategic point of view, so really cut down the negative impact of the project to a minimum which had/would been caused by the inadequate software project requirements management during project practices. These methods are fit for the projects which have participants in complex organizations, the projects which have ambiguous requirements at early stage, the projects which have larger differences of opinions within customers and the projects which have no similar systems to refer, etc. These methods can effectively narrow the differences between the views of all parties, make all parties come to an agreement quickly and determine the requirement baseline, so that the projects can progress smoothly.