There is always a success and failure of the project, and it is necessary to summarize it. One of the following carated is a failed item I have experienced, written, everyone pointed out. First introduce the background, the customer of this project is the internal customer, the application range is to provide a channel and tool for the user to collect the opinions and recommendations of the user, and provide the necessary information view to the Manager layer to facilitate intuitive The number of problems and the number of questions. Before the project was started, the user had already talked about it, saying that they saw a system in other branches, very suitable for them, hoping to transplant, and hope to build better. Considering the urgency of the user's requirements, we have made preliminary assessment actions: [] A person who is familiar with the system is preliminary, clarify the system's design background and application situation, to know the system required by the local customer is one Part of the large system. In addition, the system is supported by Out Sourcing, and the current administrator is limited to the system. [] To the branch colleague, I hope to further understand the functionality of the system, and contact the customer, try to understand the system with the customer to facilitate the customer confirmation, whether the system is the system you need, whether the function is satisfied. The reply obtained is that the customer has used this system. Because there is a customer's confirmation, the direct access to the system introduction phase [] Understand the software and hardware requirements of the system, to the branch to the system Copy, try the installation: There is no database initialization script, only the database design document And the branch colleague negotiated, the unnailed, there is only to write the database initialization script {} database script runs successfully, but the running system discovers the lack of view, to the branch colleague, other views and Table scripts And other projects are performed, the time has been in the past approximately one week {} database ready to complete, let users become familiar with the system, and change the requirements initially receive the changes demand, because we are not familiar with the system, try to get a branch colleague Will change the demand to the branch office, please help confirm the feasibility of the system modification. Here we are mainly worried about the system's changes will be more complicated than the re-need to do a system. This change needs, in fact, the need for the original system, in the case of the original system, the business process does not understand, The risk of system change is a big branch, think that it will not affect the process of the system. After many communication, the branch colleagues also indicate the files and precautions that need to be modified for each modified point. What to explain here is that the colleague is not very familiar with the system. This is the confirmation of the branch colleague and a more detailed modification, we started to modify the work, and the project proceeds to the formal implementation phase. It takes only two to three days of initial consideration of modification. At this point, the customer is looking for us for the first time, I have been around for about two weeks. But unfortunately, after the system has been modified, it is found that there is a function that does not work properly, and this function is the core of this system. So started to be familiar with the system, do the work of Deep Dig, time is very fast, one week has passed, and finally confirmed that the system has a poor portability, many Hard Code exists, some modifications have hidden dangers exist. Beginners need to understand the business processes of the system, although it is a system that is tied, it is also necessary for a customer's needs. Time is lost, and immediately communicate with our customers. I hope to sit down and talk about demand.
