Summary and suggestion on enterprise ERP system development

For large companies such as ours, building, implementing and maintaining the management information system to meet the specific management requirements of the company is a common train of thought for the construction of ERP in some large companies. For example: XXXX, XXXX, XXXX, XXXX and so on well-known enterprises.

In fact: This kind of ERP system construction way, I am not optimistic and recommend: the Social division of labor further refined today, let more professional team to do more professional things is the general trend. However, since the company used this way to build their own integrated information management system, the spirit of doing things well, let the company rest assured that the principle of the next year to more effective for the company's comprehensive information management system to provide support, knot team one year of development, maintenance work, put forward a few humble opinions:

1, strengthen the similar business process, management model abstraction and refinement, through system analysis and design, and coding to achieve our own infrastructure source library. The following is a simple source statistics tool for this year's development of the online new, old two version of the XX system, the number of lines of code statistics analysis:

By re developing the system infrastructure and reducing the amount of system code, it is believed that it will greatly reduce the complexity and workload of testing, debugging, maintenance and upgrading in the later stage of the system.

2, focus on the new subsystem, functional modules, business components, or even the simplest of a new unit, new classes of the redesign, design and implementation. In view of the current overall system in the new operation and day-to-day maintenance work, we are not likely to have sufficient manpower and time to rebuild the whole of the online subsystems. However, the implementation of new business needs occurs. Now that it's new, write code, we have more reason to abandon the original not too good development methods and ideas, using some more professional, more mature software development model and architecture, at least let the new function block from the line to start, there will be better stability, high reusability, strong scalability. Adhere to this, in order to gradually, gradually improve the whole software system's internal quality characteristics, in order to gradually reduce the maintenance workload of the system, otherwise, with the increasing amount of software code, the complexity of the system functions, the frequent changes in business needs, the system has become more and more difficult to meet the changes in new requirements: " The snowball effect "is likely to occur in the System support group, which ultimately makes it difficult for the system support team to continue to sustain effectively."

3, to support the group's software development, maintenance work to choose the appropriate software development methodology, combined with specific work practices to cut or add. The introduction of a more appropriate software development approach based on the team's actual work will greatly improve the productivity of the development team and enhance the quality of delivery of the software products. Traditional software development methods, information software development methods, unified software development methods, are not very suitable for our company system This "application demand changes frequently, support resource allocation tension" status quo.

The principles and patterns of agile software development methodologies are recommended:

1. Accurately grasp the company's production management and operation needs;

2, moderately design and maintain the flexibility of design;

3. Simple development to meet the current needs;

4. Frequent reconfiguration and iterative maintenance system design principles;

5. Test-driven development and reinforcement unit testing start at the bottom to ensure system robustness.

4, in the company's system development, maintenance, support process, the proposal must adhere to the initial system construction analysis, design, coding principles, at least the minimum baseline principle must adhere to. Into the company for several months, hear, see too much, good principles in the face of the situation of compromise. On the surface, our compromise was to shorten the time of development, improve the response to the decision of the company leadership, or finance, manpower, general management and other department managers to manage the requirements; in fact, we often pay a greater price for violating these principles afterwards. As we all know, the construction of any project system is limited and restricts each other in terms of manpower, time and quality. The classic design patterns and principles of software systems are also well known, and ultimately the quality of software products depends to a large extent on the development team's adherence to the principles and enforcement efforts in the software construction process.

6, strengthen the system testing, especially the initial development of unit testing. In the system development, maintenance work, many times found this phenomenon: a long-running program function suddenly has an exception, through the tracking code, the error is actually positioned very basic pointer protection or logic errors, and these errors are easily covered in unit testing, discovery and resolution, in contrast, in the late system of component testing, Integration testing, regression testing and system testing are difficult to reproduce. This kind of problem also reflects the low code coverage of our original test cases.

For the new year can more effectively respond to the company's development strategy norms, supporting the landing and implementation of enterprise Informatization strategy, to support the team in the next year's system work to put forward a few requirements, the general situation is as follows:

1. Accurately grasp the current needs of the company's information but not perfection;

2. Adopt Classic, mature design principle and pattern but not transition design;

3. Try to use simple coding to realize the current function;

4. Through frequent reconstruction to adhere to the beginning of the design and implementation of the principle;

5. Maintenance and new functions before the first possible reconfiguration and reuse, to eliminate the "code copy" to achieve similar system functions;

6. Strengthen unit testing to ensure the reliability and robustness of the system components, most of the software bugs are resolved during the unit development.

Finally, share personal experience of previous projects: "With sophisticated, elegant design to respond to the rapid change in demand, with refactoring and iteration to maintain a good system architecture, focus on unit testing to ensure the internal and external quality of the system."