Shulou(Shulou.com)06/03 Report--

At present, there is no mandatory content and standard for domestic software project acceptance management. in this way, there are great differences and uncertainties for software project acceptance, which also places hidden dangers for the whole process of software quality assurance. To this end, our Shandong Software Evaluation Center has referred to a large number of documents, combined with the actual acceptance management experience, summed up part of the work of software acceptance management, deficiencies, welcome to correct, you can also log on to the center website http://www. × / message exchange, if there is a need, we can provide free software acceptance management consulting services. The contents of the software project acceptance management work: first, the preparation work of the software acceptance management; 1, to confirm the operation of the complete product; 2. To confirm that the system has met the conditions stipulated in the contract and the requirements for the system function and performance in the requirement statement. 3. Sort out the list of documents needed for acceptance and the list of software and hardware configuration of the system: (1) approval documents for software engineering (2) Application report for project acceptance (3) Tender (4) Tender (5) notice of winning the bid (6) contract (including budget table) (7) Software requirements specification; (8) Summary design specification; (9) data and database design requirements specification; (10) detailed design specification; (11) operation manual; (12) user manual (13) project user evaluation process comments; (14) software interface specification (15) original code or installation disk; (16) other materials required by the expert group 4. Develop plans for personnel training and technical support. 2. Software system acceptance application report 1. The seller shall submit a software system acceptance application report to the buyer, indicating the preparation of the application system acceptance and the acceptance conditions of the system. The application report for system acceptance must be submitted in accordance with the relevant provisions of the contract, including system equipment and system software configuration list, documents, technical summary report and test analysis report, etc. the application report for system acceptance shall be signed by the technical person in charge of the seller. 2. The buyer's agent or the third-party acceptance management agency must understand the requirements of the function, performance, system configuration and documentation of the acceptance system, master the system acceptance provisions stipulated in the contract, examine the system acceptance application report submitted by the seller, and put forward opinions for handling; after examination, the technical person in charge of the buyer shall sign the application report and reply to the seller's application. The buyer will make all preparations for system acceptance in accordance with the relevant provisions of the contract, including the preparation of test cases, test data, test process and test environment. Third, formulate a system acceptance plan before the software system acceptance activities are carried out, a complete set of system acceptance test plan should be developed. The plan shall be approved by the buyer and include some test programs provided by the buyer, the plan shall include the activity procedures of the system acceptance work, acceptance test requirements, technical conditions, equipment resources, acceptance criteria, staff composition and schedule, etc. 4. Formulate the organizational structure and personnel composition. 1. Set up a special software system acceptance committee, as the organizational body for system acceptance, the committee shall have a number of chairmen, and the committee shall organize and set up a system acceptance test group, a technical group and a document review group, equipped with a number of testers and recorders. 2. The acceptance committee shall be composed of the buyer's representative, specially invited experts or third-party testing agency experts and the final buyer's representative. If necessary, the seller's representative may also be invited to participate. Invited experts must be the authority in the field of industry information and be familiar with the technological development in this field at home and abroad. Standardize the task and authority of the acceptance committee 1, the task of the acceptance committee to examine and approve the system acceptance plan; listen to the seller's "technical summary report" and "test analysis report"; determine whether the system accepted meets the requirements of the contract and the system requirements specification; examine and approve the acceptance test plan; organize the acceptance test and conduct the system acceptance review, and form the system acceptance report Supervise the product delivery after the acceptance of the system. 2. the authority of the acceptance committee shall have the right to require the seller and the buyer to explain, question and explain the relevant problems in the process of system development; coordinate the disputes that may occur between the seller and the buyer during the acceptance process; decide whether the system passes the acceptance or not. 6. the whole process of the acceptance record must be recorded in detail, recording all questions and suggestions raised by the acceptance committee during the acceptance process, the seller's answers and the evaluation of the acceptance system by the acceptance committee, and form documents for inspection and filing during the review. 7. making software acceptance test plan the acceptance test of the software system is the most critical step in the system acceptance activities, and the system to be accepted must meet the requirements specified in the terms of the contract and the system requirements specification. The test plan and procedures include the following: 1, the purpose of the test plan and procedure; 2, the data to be input for each functional test; 3, the description of the record of the test results; 4, the equipment, tools and procedures for observing and testing the results; the relevant test results shall be submitted by the seller to the buyer in the form of a written report, including: (1), the system function of the test (2) the changes that need to be made to correct the shortcomings of the system; (3) the suggestions to improve the performance of the system.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.