Agile Requirements Analysis Method And Practice In The Application Software Development

As the first step of software development process, software requirements analysis and software requirements management has become a very important activity in the process of software development. The quality of requirements analysis has too much things to do with the follow-up all stages of software development. Facing the customer requirements being increasingly complex and changeable, how to obtain requirement rapidly, and establish a completed and unambiguous requirements model has become the focus of software development. However, as the users are lack of knowledge of software, they usually cannot express their needs clearly; The developers are not proficient in customer's business, they also difficultly understand what customers really need is. This situation makes requirements analysis has become a hard work. But, at this stage, the research about requirement analysis theory and practice is very limited.In this paper, firstly, we present some traditional software requirements analysis methods. Next, we introduce the concept of the agile modeling, and then apply the agile modeling method to the all stage of requirements analysis process. By finding out the best fit point between the traditional methods of requirements analysis and the agile modeling method, we present the theory of Agile Requirements Analysis and practice of it. Finally, through the appropriate cutting applied to District Heating Management Network System needs analysis practice, we verify that requirements analysis method based on agile modeling could improve the quality of requirements analysis, lay a good foundation for follow-up software development stage, and to improve software development quality.Agile Requirements Analysis method use various modeling techniques, create a simple, adequate, variety of models, and apply the requirement reuse. It could improve the efficiency of the development of requirements, strict requirements management process, and make the analytical work in the "orderly" state always. In further, it could effectively control the spread of the demand. That means, before the baseline requirements in the definition, quickly communicate with the user, validate and modify the requirements, and ensure its accuracy;after the baseline requirements in the definition, any requirements changes will need to follow the change control process strictly.