| The requirement analysis process is an important stage of Software Engineering, asit is the base of other stages and software project management as well. It is thebridge between the end users or other users and engineers. Good requirementanalysis can provide all the stakeholders a clear picture that all the parties agreed uponand what the system/product is going to deliver. However, there have been a lot ofproblems in terms of managing software requirements. It was estimated that thereare 60% of software products/projects having the trouble with the requirementsmanagement.About 30 years before, software designers focused on the data structure and choiceof algorithms instead of from whole system point of view. This could be right for asmaller project or product. But with the size of software product becomes larger andsystem more complex in terms of workflow or business requirements, softwarearchitecture becomes more and more important because it will govern and provide theguidelines to the software quality attributes, such as product line reuse and scalabilityetc.This research introduced how to conduct requirement analysis via using use-casedriven approach, and how to describe the system architecture by using "4+1"view in apractical software project-Auditing System.First of all in this study, all the requirements were introduced. The businessmanagement process of the system was explained in details, and all stakeholdersinteracted with were identified.Secondly, focused on the actors of the system all the use-cases were briefly givenvia using UML. In the meantime, non-functional requirements such as data security,data format were discussed as well.Thirdly, detailed design of Auditing System. B/S structure was selected, and threelayer structure: client, application and database.Last, some implementation results, such as testing and deployment were discussed;conclusion and expectations were also made in the end of the work. |