The software test came later, there was a strange bug. After several findings, it is because the status of the status FLAG in DB is not enough. The code is reflected from the code to only if if there is IF without ELSE, which reflects that there is unexpected effect in the system. In general, there are two problems that have been worth a summary, which will lead to this section.
Development software projects have to come into contact with a lot of status, such as state migration. For example, a program state (temporary, draft, check, review, verification, approval, release, archiving, invalid). I have thought of so much, and the state single-step transformation can be easily grasped, but the status may be tripped and retracted. These transformations are mainly concentrated on the business terminal, and the status field of the data sheet should be simple and unified. Suppose there is a three-level plan, and the levels of the plans have different states, and the states of the plans are interacting, complex enough. From the designer's point of view, I hope to realize the realistic function as much as possible. However, due to the complexity of the real world, it is not as easy as the easiest way to use the easiest way. Therefore, there should be enough attention to the state.
It involves programming, especially the web system. The market for single soldiers is difficult to exist, and each project will consume great human resources. The problem is a long-term issue, from analysis, design, encoding, testing. Use a saying: State is everywhere. If the system is analyzed, the business is clear, and the status is clearly written. If the detailed design, the process is complete, and the side of the state is detailed in various charts. If the code is encoded, the accurate meaning of the status will be appreciated, and the status of the status and the various aspects (business, DB) will be understood that the processing of the state is displayed in the code. If testing, things must be deeply understood, and should do it, should not be able to do it.
Have you had this situation, a form is frequently used in the development process, and from time to time, it is a precious reference material from time to time. State migration diagram is a common picture. There is also a two-dimensional table is useful, such as the effectiveness of the status / action. In short, at all stages of software implementation, it is necessary to settle down in the state of the sky as soon as possible.
