Using Uml Goods Accepted Information Systems Requirements Gathering

The main work of thesis is to collect and analyze the business rules of freight management information system. On the one hand the information collected is visualized using the representation of UML corresponding to requirement capturing, which is satisfied with the next software developing, on the other hand it is expected that a common framework, which is abided by the software developing team or rebounded to adapt to the project with small changes, can be found though the argument of advantage to the process standardizing of requirement capturing.It means a great deal of comprehensive and rapidly changing business rules to develop the road rapid freight information system, especially in the case of conventional businesses changed due to using computers. There exists some weakness if we use traditional ways of partitioning function models. First, it could slough in the detail of requirement collection, or be hard to partition the functions. Secondly, it could process a fuss phrase of requirement collection and enter the design phrase directly. Accordingly, the method of UML model is used to process the work of requirement collection in the text. UML owns a suit of standard representations, which provides a record tool for between developers and customers, between developers and developers, and on which based the system is understood better and is recreated.The point of researching is focus on achieving requirement capturing for freight management information system based on UML according to businesses and business reengineering and analysis on the advantage to insisting on four rules of requirement capturing process.The four rules are confirming objective of requirement capturing, keeping the trace and changeability of requirement, ensuring the necessity of requirement capturing. The argument consists of three aspects on finding actors, domain analysis, and making a use case modeling framework.The approach for requirement capturing is finding the actors, which are according to UML definition in the explicit system boundary, and choosing the key use cases, which dictates system characteristic. The support use cases are developed for the implications of key use cases. The system function is visualized using use cases and activity diagrams. In the search of use cases the process consists of initial use case modeling, expand on the use case model, and elaborated use case.The practice proved that UML can fully express system requirement capturing and adapt to the need of software developing and the changes of business model. During the process of capturing problems can be found and solved to conform a benign project recur with insisting on the rules of requirement capturing.