I have been busy for a week. Let's summarize the time.

1. Only the original system is used to understand the requirements, but the requirement can be raised within the company. Due to the high estimation of the user level (the requirement initiator), the customer has not been well communicated with the user, there is no chance to get to the end user for on-site understanding, which leads to a very important process, which is ignored from the beginning of the demand investigation, and leads to a wrong demand. At the same time, users who need to submit their requests do not actively understand the system, resulting in delays until problems are exposed during the release phase;
2. There are still many opportunities to correct this mistake throughout the process, but it is not up to me to decide. There are many excuses to ask for it, and I have not attended several meetings, this is the most depressing one. The question raised during the final release stage should be considered as a requirement (Version) change. After all, it was not written into the initial requirement, however, I am still very depressed. After all, the changes are great;
3. Fortunately, my design philosophy solves the serious problems of the original system, which reduces the burden on the original system. It can be said that the success and failure of this project are 5 to 5, just give it a try.