2019-09-30 14:34 浏览次
The development of a software project is divided into five phases: the requirements analysis phase, the design phase, the coding phase, the testing phase, and the maintenance phase.
The results obtained during the demand analysis phase are prerequisites for the other four phases of software project development. From past experience, a small deviation in the demand analysis may cause the entire project to fail to achieve the desired results, or the final product developed is not what the user needs. What is software requirements analysis. Let me give an example to illustrate that most people know that building a house. If a user wants to build a house, the builder will discuss the details with the user in detail. How high is the floor? How is the structure? Drawing style, etc. Each link has detailed process documentation, and both parties understand the damage caused by the modification after completion and the hazard of the change details. Also in the software requirements analysis, detailed documentation is required. The software developer should extract the business problems that the software system can help the user to solve from the user's business, and plan the developer's software products through the analysis of the user's business problems. This step is a sublimation of the user's business needs. It is a leap to optimize the user's business management process and transform it into a software product, thereby improving management. Whether this step is successful or not depends directly on whether the developed software product can be obtained. User approval, smooth delivery to customers, customers can really use the developer's products to help him solve business or management problems.
The task of software requirements analysis is not to determine how the system performs, but to determine that the system must complete those tasks, that is, to provide complete, accurate, clear, and specific requirements for the target system. It does the job of describing the functionality and performance of the software in depth, determining the limitations of the software design and the interface details of the software with other systems, and defining other validity requirements for the software.
