"See the OA" series of lectures eight: 100 steps 99 [ZT]
Talking about the OA system application development User test China International Information Trust Investment Company Management Information Center OA Director Huang Yan 2002-10-14 China Computer User "OA System Construction Universal Existence, Spend Many, Treatment, Most Ideal, But Really welcomed by users, there are not many OA systems for more than three years. I believe that during the OA system project development process, it is not enough to manage the user's test, which is one of the basic reasons for this phenomenon. Therefore, OA system The key to success is the ultimately whether the application's 'taste' is, it is - "Huang Yanling: Now China International Information Trust Investment Company (Abbreviation CITIC Corporation) Management Information Center OA Director, participated in CITIC Corporation Construction of the three - generation OA system. Engaged in OA system for more than 20 years, participating in a number of large OA system construction projects, such as the first generation of China Journalists, and won the third prize of national technology applications. There is a wealth of practical experience and profound understanding in the OA construction. OA system projects are not from the needs of management reforms. Some people say that the construction OA system can do "turnkey project". I think this is just a market speculation. Different units have different management needs, inevitably determine the personalized characteristics of the OA system, and there is no universal OA system product, so the user testing has an irreplaceable role of the OA system items, and cannot jump over a key role. Development and Application "View" User Test is a relatively independent phase before the end of the system test phase and the system trial operation phase begins. The subject of the test is converted from the development technician to the final application. The user accepts and approves the software throughout the OA system to fully understand the requirements of the OA system, and gradually understand whether the OA system fully implements the requirements of the demand, which is guaranteed to ensure that the OA system function and process is correct and integrity. The key to practicality. Practice has proved that only user trials can we make reasonable recommendations to promote software practical and productive. Therefore, we regard the user test as the development of development work. It is the process of user skill training. It is the preparation process of the equipment, technology, organization and system required for the system trial operation. It is also Party A, Party B and the user understand each other, and establish long-term The process of close cooperative relationship. Prepare the beginning of "bag" user testing, there must be some preparations. First of all, the review is performed, and the system has a user test condition that can be converted from the development phase to the test phase. Second, the organization and system preparation are performed. First, determine that the project party (Party A) and the developer (Party B) and the end user jointly form a project coordination group, and the main task is the demand control and test coordination. Second, Party A is a team leader, focusing on demand control and project supervision. Third, Party B is responsible for optimizing the OA system. It should be noted that this phase of development team cannot dissolve or decrease. Fourth, the user representative is primarily responsible for using all the functions and processes of the application software and makes recommendations and comments. The user representative is best to understand the department management needs and business global, and are familiar with the backbone of the main business. Fifth, establish a weekly project coordination system. Coordination will maintain scientific, serious, authoritative and democratic. The three parties should be responsible for the coordination, and the coordination will be responsible for the Internal Network Project Leading Group. Choosing the "Target and Route" user test To formulate the corresponding test key, such as the first test function post-test process; between the first test room internal post-test arrangement, the internal post-test department (including the group leadership) , Other functions and subsidiaries); finally integrated tests and actual exercises. At the same time, it is also necessary to design a test plan and select a typical case. The specifically can have the following steps: 1. As the basis for the main basic data of the user test, it is necessary to establish a typical case to simulate actual work, and to cover the test functions and processes.
It is generally proposed by the development parties, approved by Party A and the user; 2. Test technical solutions and technical documents are mainly prepared by the development parties; 3. The whole process test record is mainly based on the Case and Party B according to the case and process design. 4, When integrated testing, the relevant departments, the relevant leaders must personally organize and coordinate; try to use the true role, true data, the closer to the actual use; 5, the test record table is followed by Party B; the feedback table is filled in; As the basis for evaluation system and optimization, the development side can provide a list of functions and processes to be tested when testing, which is generally tested for beginners. 7. User testing generally tests multiple times; our experience is general It is necessary to test through 3 rounds. When you encounter problems, the user test is initially filling some of the BUG in the program. However, after one, two-wheeled test, the issue of user feedback will focus on functional integrity and process rationality, especially joint adjustments or integration. When testing, users are familiar with software usage, more consideration and ease of use, and the opinions are directly related to the system's practicality and productization level, it is important and critical. Therefore, whenever the user completes a round of testing, the coordination team must carefully conduct a demand control seminar. In the test, there are also some unexpected problems - 1. Demand change is difficult to control the project requirements research phase, because there is no IT knowledge, you can't tell what you want to do, although the user needs the book, but in user test In the process, with the increase in IT experience, it will naturally find some unreasonable or incomplete or lack of demand, it will inevitably cause change. Our experience is: demand variation is inevitable, the key is to do demand control. If the degradation of demand changes, the full user has said that the project may fall into endless development or progressive state of failure. However, if you think of the need for an uncharged bible, from the surface, it is insisting on the contract, but countless facts show that the entire OA system may eventually fail. Our experience is: Demand change control management is the core and key of project management. In the implementation, we designed the user testing the feedback form, allowing users to fill in at any time in the test. Then study the opinions and suggestions of users in the feedback table at each coordination. For user opinions, we have three strategies: First, do not meet the requirements of demand, or meet the needs but did not satisfy users reasonable use requirements, Party B should resolve as soon as possible; secondly, new needs to users, if the three-party negotiation Agree to achieve, in writing in writing, in the form of a total demand attachment, incorporating project development plans, protected by contract; third, if it is not consensus, it is not subject to contract protection. For the unreasonable requirements of users, they must dare to make a practical understanding of the user to seek the user's full understanding. Experience has shown that it is very lack of understanding of users' business with their own technical personnel. 2. The progress of technology development and cost difficult control demand are not sufficient, or because developers understand the user's business understanding, or because of variety of reasons, user demand changes, will cause modifications or new development programs, and even causing changes in technology routes. , Cause progress delay, and progress delay, inevitably cause cost-out of control, similar problems are quite common. 3. Data import work is difficult to predict the historical data left by the old system, the complexity or irregularity of the structure, and the vast amount of data, and the like are often estimated.
