Formal acceptance of the project includes acceptance of project products, documents and completed deliverables

The acceptance of the system integration project needs to be based on the contract signed in the early stage of the project and the corresponding technical work content. If the contract changes during the execution of the project, the changed content should also be used as the basis for evaluation of project acceptance.

Project acceptance work requires the completion of a formal acceptance report. The acceptance report contains the main contents of the acceptance and the corresponding acceptance conclusions. All parties involved in the acceptance should sign and confirm the acceptance conclusions and bear corresponding responsibilities for the acceptance results.

Acceptance testing is a comprehensive test of the information system, in accordance with the system environment agreed in the contract between the two parties, to ensure that the function and technical design of the system meet the functional and non-functional requirements of the builder and can operate normally.

The acceptance test phase should include writing acceptance test cases, establishing an acceptance test environment, comprehensively executing the acceptance test, issuing an acceptance test report, and signing the acceptance test report.

After the information system passes the acceptance test, the system test operation can be started.

The system trial operation period mainly includes data migration, daily maintenance, defect tracking and repair, etc.

For problems that occur in the system during the trial operation, determine whether it is a system defect based on its nature. If it is a system defect, the system functions should be corrected in a timely manner.

If it is not a flaw in the system itself, but new requirements for additional information systems, changes can be made following the project change process and can be used as part of the subsequent upgrade project work content.

After the system has undergone acceptance testing, the system's documentation should be handed over to the customer gradually and comprehensively

Introduction to system integration projects

System Integration Project Final Report

Information System Maintenance Manual

Information System Instructions Manual

Software and hardware product manuals, quality guarantee certificates, etc.

After the trial operation of the system, at an agreed time, such as three months or six months, both parties can start the final acceptance of the project.

Large-scale projects can be divided into two steps: trial operation and final acceptance.

For general projects, system testing and final acceptance can be combined, but the final acceptance process needs to be confirmed.

The final acceptance report is one of the most important documents for the owner to approve the contractor's project work. It is an important symbol to confirm the completion of the project work.

The final acceptance includes both parties’ recognition and acceptance of the acceptance test documents, both parties’ recognition and acceptance of the working conditions during the system trial operation, both parties’ recognition and acceptance of the system documents, and both parties’ recognition and acceptance of the completed project work.

After the project passes the final acceptance, the project teams of both parties should write an acceptance report and submit it to the work supervisors of both parties for approval. This marks the end of the project team's development work and the beginning of project follow-up activities

Understand the work status of the entire project process and the performance status of relevant teams or members

Understand the problems and summarize improvement measures

Understand and summarize the lessons learned during the entire project process

Discuss the summarized documents and store them in the company's knowledge base after approval, thereby incorporating them into the company's process assets.

Collect and organize project process documents and lessons learned

Collection of lessons learned and preparation of discussion notes for the project summary meeting

The project summary meeting needs to be attended by all members involved in the project and will be documented by the plenary discussion.

The documents produced by the project summary meeting must be confirmed by everyone. Any documents that violate this principle cannot be used as the result of the project summary meeting.

The project summary meeting should also conduct self-evaluation of the project, which will facilitate subsequent project evaluation and audit work.

Project summary meeting discussion content

After the system integration project completes the acceptance work, the information system will transform from the early construction stage to the corresponding operation and maintenance stage.

Modification of software bugs

software upgrade

Follow-up technical support

Information system daily maintenance work

Hardware product updates

Meet new needs for information systems

Information system target evaluation is the focus of information system post-evaluation. An important basis for evaluating the success of an information system is whether the information system has achieved various goals set at the beginning of the information system planning.

When evaluating information system goals, it is necessary to analyze and evaluate the correctness, rationality and feasibility of the project's preset goals.

Information system process evaluation is to evaluate the conformity and rationality of the process from the perspective of process analysis and review

Information system process evaluation focuses on whether the entire process management of the information system is carried out according to the plan, and whether major deviations in process management are responded to and analyzed in a timely manner.

According to the life cycle characteristics of information systems, information system process evaluation mainly includes four stages of process evaluation: the early stage of information system demonstration, the information system bidding stage, the information system development and construction stage, and the information system operation and maintenance stage.

Information Systems Technology Assessment

Information system economic benefit evaluation

Information system management benefit evaluation

Information system social benefit evaluation

Information system environmental impact assessment

The sustainable evaluation of information systems mainly evaluates the possibility of continued operation and development of the information system, and analyzes whether the established goals of the information system can be continuously achieved.

Evaluate whether the information system can be continuously and stably upgraded in the future, and whether similar information system projects can be implemented in a similar manner within the organization in the future