Information system project acceptance usually includes project quality acceptance (product quality, service quality, etc. ) and document acceptance.
Project engineering quality. The American Quality Management Association defines quality as "the ability characteristics of processes, products and services to meet explicit or implicit needs." What needs to be pointed out here is that the quality and grade of information system projects cannot be confused. Classification is to classify or grade entities with the same function according to different technical characteristics; Quality focuses on describing the overall characteristics of product attributes that meet a given demand. Information systems can be of good quality (simple operation and stable operation) but low grade (limited functional features) or poor quality (a large number of code errors and lost documents) and high grade (many functional features).
Project engineering documents. As an important part of information system project achievements, project documents are essential for information system projects. The compilation of project documents must ensure the quality. Poor quality documents are not only difficult to understand, causing a lot of inconvenience to users, but also weakening the management of the project, increasing the project cost and even causing greater harm. High-quality project documents should reflect pertinence, accuracy, clarity, completeness and traceability. The information system project document system mainly includes project management documents, project change documents, project construction documents and technical documents (see the chart for details).
How to carry out information system project acceptance
Make a good project acceptance plan according to the project plan. Due to the complexity of informatization project construction, enterprises generally adopt the method of phased acceptance for project acceptance. It is necessary to deeply and carefully analyze the overall goal and overall progress plan of the project, and then decompose the overall goal in stages to form a phased goal. After the target of phased acceptance is formed, the content of acceptance in each stage should be refined and quantified, especially the conditions for entering the next stage from one stage should be clarified, so that each stage is interlocking. If the previous stage of acceptance fails, the next stage of acceptance is out of the question, let alone the final acceptance of the project. It can be seen that the key point of making a good project acceptance plan is to divide the project acceptance time points, and make clear the objectives, acceptance content details, acceptance standards and acceptance methods of each stage of the project.
Make a reasonable and effective project acceptance plan. The project acceptance plan points out the contents and procedures of project acceptance. Due to the different scale, nature and characteristics of the project, the content of the project acceptance plan is also different. Generally speaking, the project acceptance plan should include the following contents: acceptance purpose, acceptance principle, reference documents, acceptance scope, acceptance conditions and basis, construction overview and acceptance procedures. The general procedures include: determining the time and place of acceptance; Determine the institutions and personnel involved in the acceptance. Project construction units, contractors and supervision units generally send representatives to participate, but of course other project stakeholders, such as end users of information systems and experts in this information technology field, can also be included; Check the trial operation of the verification system since it went online to see if it can meet the acceptance conditions; Project quality acceptance, comprehensively and thoroughly check whether each function of the information system can achieve the goal, whether it meets the needs of end users, and whether the key indicators such as usability and reliability are qualified; Review and accept technical and management documents; Arrange the bidding documents, bidding documents and contract documents, and check whether the expected goals are achieved; Solve the remaining problems. If there are problems that cannot be solved temporarily, the contractor shall communicate with the construction unit and put forward solutions and commitments; Check the service and maintenance of the system, and check whether it meets the requirements in the bidding documents, bidding documents and contract documents; Issue acceptance conclusions and opinions.
Do a good job in post-project evaluation in time. Post-project evaluation refers to a systematic and objective analysis of the completed project objectives, implementation process, benefits, functions and impacts. Through the post-project evaluation, it can be determined whether the expected goal of the project has been achieved, whether the project decision-making and planning are effective and reasonable, and whether the main benefit indicators of the project can be realized. Summarize the experience and lessons through analysis and evaluation, provide the basis for improving the decision-making level and management level of new projects, and enhance the sense of responsibility and comprehensive skills of project implementers.