Discuss software requirements Analysis process

The requirement analysis of software must have an in-depth understanding of the original business, extraction, abstraction, sublimation process, especially the management software requirements analysis.

The requirement analysis of software is to extract the business problem that the software system can help the user to solve from the user's business, and to plan our software products by analyzing the user's business problem. This step is the user's business needs of a sublimation, is a user business management process optimization, into software products, thereby enhancing management and realize the quality of the leap, this step is successful, directly related to the development of software products can be recognized by users, the smooth delivery to customers, Customers can really use our products to help him solve business or management problems.

According to the software development process description, the requirements phase can be subdivided into requirements research and demand analysis of two small stages, demand research needs to fully and carefully understand customer objectives, user business content, processes, etc., this is a demand for the process of collection, is the basis for the needs analysis. When we have understood and understood the user's business, we can begin to analyze the requirements. The requirements analysis of the software system can be completed by the product engineer or system analyst or both in a phased effort to complete the requirements analysis.

First, the extraction of the core, the main, urgent business, clear business processes

Through demand research, we will find that users have a lot of business in all aspects, from the big picture, including the user's various business projects, business processes, and then detailed to the business process of each document, each record, such as the production process of each link in the record, office of every notice, and even the document and the press to send and receive, Family Planning index statistics and so on. Where do we start with such a complex range of business? At this time we need to look back to see the software project specifications, and then warm the customer on the software project or product of the initial requirements of the target and scope, our software is mainly for users to solve what kind of problems. From a large number of business to extract the user's core, the main, much-needed business, these are our software needs are the main concern. Write an article need to focus on, prioritize, I think planning a software PRODUCT is the same.

From the users of the complex business, business processes, the extraction of those distributed in various departments of the same business extraction. such as the management of materials, related to the production department needs planning, summarized to the material Department procurement plan, the plan approval, the purchase contract, the material purchase, the material department's receiving and dispatching the service, the production department's material lead consumption and so on, we need to analyze the user's this business process which is the system can help the management, What is to be handled outside the system, fully analyze the user's existing business and business processes, we go to the next step.

Second, the use of management ideas to optimize business processes

We provide a management software product, to help users solve the problem of management, then the user is such a business process, we need to analyze such a process reasonable, there are deficiencies, how to improve efficiency, solve problems, can use more advanced management ideas? In general, we need to consider the optimization of business processes from two aspects. First, we use the network computer These new technical means, compared with the original manual, telephone and other means in the transmission of information, information sharing, data processing and other aspects will bring new ways, will change the original business process. On the other hand, we consider whether we can use advanced management ideas, such as Mrpii, ERP, SCM, CRM, JIT, EIA, e-business and so on, according to the understanding of the user's business, to reorganize or optimize the existing business processes. Of course, once involved in the business process changes must be with the customer's senior managers to communicate fully, only customer identification can be determined, because this will be in the software implementation needs corresponding management system supporting implementation.

Third, the classification of business, planning system Blueprint

All of the above are clear and we can sketch the system blueprint. The system has several subsystems, each subsystem has which module, each module handles which business, very important point also has each subsystem module the data interface relation, where the basic data enters, through which processing produces which result and so on. This process needs to organize, abstract User Services, planning software implementation, planning software system modules of the logical relationship between. Because the system's page implementation is according to the System module plan, therefore should try to adopt the user to be easy to understand, the familiar way, the word carries on the module description.

For example, ERP system in the material management subsystem, first of all, the subsystem is the ERP system in the material-related business processing system, at the same time it mainly production systems, cost management subsystem to provide production materials supply, consumption accounting and other data support. So when planning the subsystem module, according to the business process model, should include material needs planning, material procurement planning, warehousing management, inventory management and other major business modules, and then consider the software operation must be the initial data settings, to add a basic information maintenance module (including material categories, material coding and other information maintenance), Also take into account the different users of the system's different needs, such as more production personnel, management personnel needs, and then add a separate comprehensive query and analysis module. In addition to the procurement of materials related to the business, such as procurement contracts, can be put into the contract management subsystem unified consideration, here only to do inquiries. In this way, the software system to deal with the material management business, check whether the material management of all the core, the main business, then we found that there are materials such as procurement, acceptance, library and other business or need material management business personnel to complete, the system can do is to record the results. The software system is the management auxiliary system, cannot completely replace the human all work. Management software plus management system, business personnel's operation to constitute a complete set of management system.

Four, detailed description software function point

Planning the function of the software module, just the function of software framework structure, the next step needs to clearly describe the specific content of each module. What to include, what to do, what to do with each function point, the priority, the business rules, the detailed feature description, and so on. These are also the content that the software requirements specification must describe.

The performance of demand analysis, we now adopt requirements Specification documents, UML language description of Use case diagram, Class diagram, activity diagram, as well as entity Relationship diagram, interface prototype and so on, from different angles, different requirements describe the layout of the software panorama.

Quality control of demand analysis

Software requirement analysis is directly related to the direction of software products, so the quality of requirement analysis is very important. For this key point of quality control, it can be through internal review and peer review of the way, then the customer side of the review. The project team internal review or peer review is based on the company's specifications and the reviewer's own experience of the requirements analysis of the ambiguous, unreasonable, illogical, inconsistent with the norms of the place to correct. And the customer's review is mainly to describe whether the software implementation really meet their needs, can help them solve problems and other aspects of assessment.

The requirement analysis of software must have an in-depth understanding of the original business, extraction, abstraction, sublimation process, especially the management software requirements analysis.