The demand analysis of the software must have an in-depth understanding, extraction, abstraction, and sublimation process for the original business, and management software demand analysis is especially true.
The demand analysis of software is to extract software systems from the user's business to help users solve business problems. Through the analysis of user business problems, our software products are planned. This step is a sublimation of the user's business needs, is an optimized leap that optimizes the user business management process, converting to software products, thereby promoting the quality of management, which is successful, whether the software product that is directly related to the development of software products can be Get the user's approval, delivery to the customer, whether the customer can truly use our products to help him solve business or management issues.
According to the software engineering description, we can subdivilize the needs of demand research and demand analysis, demand research needs to understand customer goals, user business content, process, etc., which is a need for demand. The acquisition process is based on the basis for demanding analysis. When we have already understood, understand the user's business, so you can start analytical needs. The demand analysis of the software system can work all demand analysis by product engineers or system analysts or two phases.
First, extract the core, the main, urgent business, clear business processes
Through demand research, we will find a lot of business in all aspects of users. From the big view, including users of various business projects, business processes, and then detail each document of the business process, each record, such as each of the production process Records of the link, every notice in the office, even including document newspapers, family planning indicators, and more. Why are we started with such a complicated business? At this time, we need to look back to view the software project specification, once again warm the customer's initial demand objectives and scope of the software project or product, our software is mainly to solve the user. Extract the user's core, the main, urgently needed business from many business, which is the main concern of our software. Writing an article requires a focus on highlighting, the main second is clear, I think that it is also the same as planning a software product.
From the complicated business, the extraction of business processes is extracted, and the distribution of the same business is extracted in various departments. For example, the management of materials involves the need to use the production department, summarize the procurement plan of the material department, the approval of the plan, the procurement contract, the procurement of the materials department, the delivery of the materials, the materials of the production department, etc., I The door needs to analyze the user's business process which is the system help management, which is to process the existing business and business processes outside the system, and we will enter the next step.
Second, use management ideas, optimize business processes
We provide management software products, to help users solve management problems, then users are such business processes, as needed to analyze such a reasonable process, have defects, how to improve efficiency, solve problems, Use more advanced management ideas .... In general, we need to consider the optimization of business processes from two aspects. First, we have adopted these new techniques such as network computers, compared with the original manual, telephone, etc., will bring new ways, and will change the original business. Process. On the other hand, we consider whether advanced management ideas can be used, such as MRPII, ERP, SCM, CRM, JIT, EIA, E-Business, etc., such as MRPII, ERP, SCM, CRM, JIT, EIA, E-Business, etc. Or optimization. Of course, once the changes involved in the business process must be adequately communicated with the customer's middle and high-level managers, only the customer's identity can be determined, as this will definitely need the corresponding management system to be executed in the software implementation.
Third, conduct business classification, planning system blueprint
After all over the above, we can depict the system blueprint. There are several subsystems, which modules have each subsystem, which services are processed, and it is important to have a data interface relationship between each subsystem module. Where is the basic data from entering, what to generate, etc. . This process needs to be organized, abstract user business, planning software implementation, planning the logical relationship between software system modules. Because the system's page implementation is planned according to the system module, the user should be used to understand, familiar, and the words are described in the module. For example, the material management subsystem in the ERP system first clarifies that this subsystem is a business processing system related to the equipment in the ERP system. It also provides production materials, cost management subsystems, and data consumption, etc. stand by. Therefore, in the planning subsystem module, according to the business process model, it should include major business modules such as materials, materials procurement plans, access library management, inventory management, and consider the initial data settings that must be operated, adding an underlying information maintenance. Modules (including information maintenance such as materials, materials coding), and considering different needs of different users, such as more manufacturers, managers' needs, add a comprehensive query and analysis module. In addition, there are services related to materials procurement such as procurement contracts, which can be put into contract management subsystem unified consideration, here only inquiry. So planning the processing of the software system for the material management business, checking if all core, main business in materials management, then we find that there is also such as materials procurement, acceptance, disk library, etc., still require material management business personnel. To do it, the system can do is the record results. Software systems are managed auxiliary systems that cannot be fully replaced by all people. The management software plus the management system, and the operation of the business has constituted a complete set of management systems. Fourth, detailed description software function point
Planning the functional module of the software, just the functional frame structure of the software, the next step needs to be clearly described in the specific content of each module. What content, what can be done, every function point, priority, business rules, detailed description, and more. These are also the content that the software needs specifications must be described.
Demand analysis, we now use the demand specifications documentation, the use case, class diagram, activity diagram, and physical relationship diagram, interface prototype, etc.
V. Quality control of demand analysis
Software demand analysis is directly related to the direction of software products, so the quality of demand analysis is critical. For this quality control of this key point, you can review the ways and peer reviews by internal reviews, and then the client's review. The internal judging or peer review in the project team is mainly based on the fact that the company's norms and reviewers itself is unclear, unreasonable, non-logical, and does not meet the norms. The customer's review is mainly to achieve the description of the software to actually meet their needs, and can help them solve the problem.
The demand analysis of the software must have an in-depth understanding, extraction, abstraction, and sublimation process for the original business, and management software demand analysis is especially true. (Finish)
