Introduction to ERP Secondary Development Process

Review the secondary development of ERP over the past two years and talk about your understanding of the current secondary development model of the Department (please correct me if you have any shortcomings )!

1.Causes of Secondary Development

No matter which industry, no matter which ERP supplier, it is impossible to develop products that are perfect for every enterprise. Enterprises that purchase ERP will always need ERP for customization (OEM) due to their own unique processes ), at this time, the secondary development of the product came into being.

2. Secondary Development Process

1) Each regional business department shall write the requirement documents based on the customer's specific needs. After confirmation by the customer, the documents will be sent to the secondary development department for customization.

Requirement Review: As the business department consultant does not have a high degree of understanding about the system, the requirements confirmed to the customer may not be completed on the basis of the existing platform. Therefore, the product personnel should be added to the requirement document. 2) you can submit the specification to the programmer for development only after it is approved. The advantage is that the customer needs can be realized on the basis of the existing platform, and whether the hours evaluated by the consultant are reasonable, which can greatly improve the efficiency of the secondary development department.

3) Program Development ① the department manager will arrange the program development schedule and enter the dispatch system according to the writing hours confirmed after reviewing the specifications and the current manpower status of the Department! At the same time, reply the specific situation to the business department consultant. ② Establish development platforms, test platforms, and other environments. ③ The programmer starts to write a program based on the requirement document (specification.

4) after the program test program is developed, the customer data is simulated in the existing environment for Integrated Testing (Function Testing and system testing ).

5) after the program shipment program is tested, the test list and the compiled package are loaded and then delivered to the consultant.

6) The program installation consultant will install the program in the customer's environment, complete the test in the customer's test environment, test OK, and install the program in the customer's normal environment.

7) after the customer closes the case, the consultant closes the case and notifies the secondary development department.

3. Assistance Tools

1) external recording system: Strengthen the query and control over the entire development cycle between the regional business department consultants and secondary development departments, and promptly and in detail reflect the state of program development.

2) environment building tool: Helps programmers quickly and efficiently establish a secondary development environment and complete related configurations.

3) self-testing tool: detects certain fixed requirements of the product and effectively prevents errors caused by programmer negligence.

4) Packaging tool: quickly and efficiently complete the build Process of the development program, and package the required database information and related file information into a zip file.

5) Internal Dispatch System: efficiently manages the working conditions of all Department staff and responds to existing problems in a timely manner.

This is the General Department workflow. In the future, we will continue to introduce the problems frequently encountered during the operation of the Department and the corresponding solutions (to be continued ).

We hope that our work processes will become more and more standardized and constantly improve ourselves.