Developer Note (3)-A huge copy of the world's articles. Do not run the achievements of the predecessors

People often ask: "Which one is important for requirements, design, programming, and testing ?" This question is hard to answer. The four are all essential links in the software development process. A good system cannot be produced only when one of the links is completed. However, if any part is broken, it will definitely have a bad impact on the system. From the perspective of risk management, demand development and management may be the most important link. Because demand is the root cause of the product, whether or not the understanding of product requirements has the greatest impact on the product. Like a River, if the source is polluted, the whole river will be polluted. Fortunately, I am both a software developer and an end user of this system. I have personally worked in the cost management department, bidding department, and project legal person settlement department, we have a better understanding of most of the requirements of the system, which reduces the burden on demand analysis. The requirement may be too self-satisfied, so the depth of the survey on the needs of water conservancy design units is not enough, leading to a defect in the current system's provision of functions for the design unit users, it is not easy to make up for. This requirement is associated with many modules, and the entire army is triggered. Just as Frederick Brooks described the importance of the demand in his 1987 classic article "No Silver Bullet": "The most difficult part of developing a software system is to accurately describe what to develop. The most difficult conceptual work is to compile detailed requirements, including all interfaces for users, machines, and other software systems. If a mistake occurs in this job, it will cause great damage to the system and it will be extremely difficult to modify it in the future ." Software requirements are the source of system design. After detailed requirement analysis is completed, the next step is to enter the system design stage. The core content of software system design includes architecture design, user interface design, database design, module design, data structure and algorithm design. According to the specific development of the software, the system has prepared two sets of solutions: one is to inherit the mainstream design ideas of the existing water cost software on the market, improve its imperfect parts and add some advanced design ideas. Another solution is to abandon the mainstream design ideas and develop a comprehensive product with a new path. I have compared the advantages and disadvantages of the two schemes: the advantages of the first scheme: 1. The feasibility of the structure design of the mainstream water conservancy cost system has precedent, and the development risk coefficient is low.
2. A large number of old users are used to the previous software operation modes. Mainstream user interfaces and module painting sections give old users a sense of familiarity, so they do not have to learn how to use the software.