A Method for Secondary Development of Software

Abstract

A method for secondary development of software in the present invention includes step S11, creating a data structure; step S12, designing a program development interface; step S13, establishing a program development instruction; step S14, designing an external dynamic loading dynamic link library function, and When the program needs to be compiled, use the functions in the dynamic link library as the program development instructions; and step S15, designing the main program interface and interface management functions. This method not only has a simple and friendly user interface, but also has a powerful secondary development function, which can meet different application scenarios; reduces the project development cycle, and reduces software management and maintenance costs.

Description

technical field [0001] The invention relates to the field of automation in the optical communication industry, in particular to a method for secondary development of software. Background technique [0002] With the rapid development of the optical communication industry, automatic coupling technology has become the mainstream of production in the industry. Due to the wide variety of optical communication products, many coupling machines for different products have been born; the software on the machines is different, which brings great advantages for software debugging and production maintenance. A lot of difficulty and duplication of work came. [0003] There are two ways of developing software for existing coupling machines. The first is to decompose each action step and parameter according to the project requirements to form a flow chart, and then program directly according to the flow chart. All steps and parameters are written in the code. The advantage of this method ...

AI Technical Summary

Problems solved by technology

The first is to decompose each action step and parameters according to the project requirements to form a flow chart, and then program directly according to the flow chart. All steps and parameters are written in the code. The advantage of this method is that the early development speed is very fast, and the disadvantage is the later debugging. And process adjustment is very cumbersome, because it is often necessary to change the process, parameters and function expansion in actual production

This will lead to problems with multiple software versions on the same machine, which undoubtedly increases the workload of software maintenance; the second is to write each basic action as a module in the code and mark it. The execution order of the actions is determined by the software engineer or process engineer according to the step identification

This method solves the above-mentioned problem of frequently changing the process, but it can’t do anything about the need to add new functions and new processes; in addition, this method will also cause at least one software on the same product type machine to appear. Version issues, which provide a huge challenge for software management and maintenance

Images