Enterprise ERP System Development Summary and Suggestions

Enterprise ERP System Development Summary and Suggestions

Author: Cheng Xiaoxu

 

For large companies like ours, self-built, implemented, and maintained management information systems that meet the company's specific management requirements are common ideas for some large companies to build ERP. For example, xxxx, and other well-known enterprises.

In fact, I am not optimistic about and recommended this ERP System Construction Method: today, when the social division of labor is further refined, it is the trend of the times for more professional teams to do more professional things. However, since the company adopts this method to build its own integrated information management system, in line with the principle of doing well and reassuring the company, it will provide more effective support for the company's integrated information management system in the coming year, after finishing the development and maintenance work of the team over the past year, let's put forward some points:

1,Strengthen the abstraction and refinement of similar business processes and management modes, and implement the source code library of our own infrastructure through system analysis and design and coding.. The following uses a simple source code statistics tool to analyze the number of lines of code for the XX system of the new and old versions developed and launched this year:

By re-developing the system infrastructure and reducing the amount of system code, we believe that the complexity and workload of testing, debugging, maintenance, and upgrade in the later stages of the system can be greatly reduced.

2,Focus on creating subsystems, function modules, business components, and even the simplest new unit and Class re-analysis, design, and implementation. We are unlikely to have enough manpower and time to reconstruct the various online subsystems in view of the new operation and daily maintenance workload of the entire system. However, the implementation of new business needs has occurred from time to time. Since new features and new code are added, we have more reasons to discard the original poor development methods and ideas and adopt more professional and mature software development models and architectures, at least starting from the launch of the new feature blocks, the new feature blocks have good stability, high reusability, and high scalability. In this way, the internal quality characteristics of the entire software system can be gradually and gradually improved, and the maintenance workload of the system can be gradually and gradually reduced; otherwise, with the increasing amount of software code, increasingly complex system functions, and frequent changes in business requirements, it is increasingly difficult to meet the new requirements of existing systems: the "snowball effect" is likely to happen in the System Support Team, which makes it difficult for the System Support Team to continue to effectively support it.

3,Select appropriate software development methodology for supporting the software development and maintenance work of the team, and crop or supplement the software based on specific work practices.. Introducing more appropriate software development methods based on the actual work of the Team will greatly improve the efficiency of the development team and improve the internal and external quality of the delivery of software products: This is an undeniable fact. Traditional software development methods, information-based software development methods, and unified software development methods are not suitable for our company's current situation of "frequent application requirements and tight resource allocation support.

We recommend that you use the principles and modes of Agile Software Development:

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

2. Moderate design and flexible design;

3. Simple development to meet current needs;

4. Frequent reconstruction and iteration maintain the original design principles of the system;

5. Test-driven development and enhanced unit testing to ensure system robustness from the very bottom.

4,In the process of system development, maintenance, and support, we recommend that you adhere to the analysis, design, and coding principles at the initial stage of system construction. At least the baseline principles must be adhered.. I have been in the company for a few months and have heard and seen too many good principles to compromise in the face of reality. On the surface, our compromise was to shorten the development time, improve the response to the company's leadership decision-making, or the management requirements of finance, human resources, general manager, and other department managers; in fact, afterwards, we often pay a higher price for violating these principles. As we all know, the construction of any project system is restricted and mutually restricted in terms of manpower, time and quality. Classic design patterns and principles of software systems are also well known. The final quality of software products depends to a large extent on the development team in the process of software building, adhere to and execute the principles.

6,Strengthen system testing, especially unit testing at the early stage of development.In the system development and maintenance work, we often find this phenomenon: A program function that has been running for a long time suddenly has an exception. by tracking the code, errors are usually identified as basic pointer protection or logical errors, which are easily overwritten, discovered, and resolved in unit tests. On the contrary, it is difficult to reproduce components, integration, regression, and system tests in the later stages of the system. These problems also reflect the low code coverage of our original test cases.

 

In the new year, the company will be able to respond more effectively to the company's development strategic specifications and support the implementation and implementation of the enterprise's informatization strategy. The requirements for supporting the team's system work in the coming year are as follows:

1.Accurately grasp the current needs of the company's informatization, but does not blame all;

2. Adopt classic and mature design principles and models without transitional design;

3. Try to use simple encoding to implement the current function;

4. Adhere to the design and implementation principles at the beginning of the period through frequent reconstruction;

5. Rebuild and reuse functions before maintenance and new functions, and avoid similar system functions through "code replication;

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

 

Finally, I shared my previous project experience:"Use exquisite and elegant design to cope with the ever-changing needs; Use reconstruction and iteration to maintain a good system architecture; pay attention to unit testing to ensure internal and external quality of the system".