CN112764731A - Software interface maintenance method, system, computer equipment and storage medium - Google Patents
Software interface maintenance method, system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112764731A CN112764731A CN202110067562.8A CN202110067562A CN112764731A CN 112764731 A CN112764731 A CN 112764731A CN 202110067562 A CN202110067562 A CN 202110067562A CN 112764731 A CN112764731 A CN 112764731A
- Authority
- CN
- China
- Prior art keywords
- interface document
- product
- updated
- macro
- document
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 35
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000012360 testing method Methods 0.000 claims abstract description 9
- 230000002349 favourable effect Effects 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 6
- 230000000007 visual effect Effects 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/72—Code refactoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
Abstract
The invention provides a software interface maintenance method, a system, computer equipment and a storage medium, wherein the method comprises the following steps: defining a product macro corresponding to the original interface document; when the interface is updated, the original interface document is correspondingly updated; reading the updated original interface document by using a script tool, and generating a corresponding header file and/or an external interface document by inputting the product macro; and if the header file is generated, updating the header file to a code base, and performing compiling test. The scheme has low maintenance workload, is convenient for tabular display of the interface parameters, can avoid inconsistency of the external interface document and the header file, and is favorable for reading of clients.
Description
Technical Field
The present invention relates to the field of software interface maintenance technologies, and in particular, to a software interface maintenance method, a software interface maintenance system, a computer device, and a storage medium.
Background
Interfaces in the computer world have two meanings: one is the narrow definition of "interface" of the software itself, such as various software development APIs and the like; the second is the interaction interface between the human and the software. Under the condition that the system architecture is not changed, the interface document and the header file are required to be expanded or changed for different customized customers.
In the prior art, a common method is that a software header file is modified every time an original interface document is changed; secondly, only maintaining the head file, and then reading the head file and generating an external interface document by using conversion tools such as Docco, Dexy, Doxygen, TurnAPI and the like. However, the first method is dispersive in modification, large in workload and low in efficiency, and the external interface document and the header file are often inconsistent, so that the maintenance and management of the software interface are affected; the second method cannot achieve tabular display of interface parameters, and is inconvenient for customers to read. Therefore, a software interface maintenance method is needed, which has low maintenance workload, is convenient for tabular display of interface parameters, and can avoid inconsistency between the external interface document and the header file.
Disclosure of Invention
The invention aims to provide a software interface maintenance method, a system, computer equipment and a storage medium, the scheme has low maintenance workload, is convenient for tabular display of interface parameters, can avoid inconsistency of external interface documents and header files, and is beneficial to reading of clients.
The technical scheme provided by the invention is as follows:
the invention provides a software interface maintenance method, which comprises the following steps:
defining a product macro corresponding to the original interface document;
when the interface is updated, the original interface document is correspondingly updated;
reading the updated original interface document by using a script tool, and generating a corresponding header file and/or an external interface document by inputting the product macro;
and if the header file is generated, updating the header file to a code base, and performing compiling test.
According to the scheme, the product macro corresponding to the original interface document is defined, so that when the interface is updated, only the original interface document needs to be updated, the updated original interface document is read by using a script tool, and the product macro is input to generate the corresponding header file and/or the external interface document. According to the scheme, only the original interface document needs to be updated, so that the maintenance workload is reduced, and the centralized control of the interface on the source is facilitated; meanwhile, when the header file is acquired, the product macro is input into the script tool to generate output from the original interface document, so that the inconsistency between the external interface document and the header file can be avoided, the updated interface parameters displayed in a form in the external interface document can be conveniently checked, and the reading of a client is facilitated.
Further, the reading of the updated original interface document by using the script tool and the generation of the corresponding header file and/or external interface document by inputting the product macro further comprises the steps of:
if the external interface document is generated and the updated part of the original interface document is not disclosed to the outside, calibrating the part which is not disclosed to the outside in the original interface document through a hidden macro;
and reading the updated original interface document by using a script tool, and generating the external interface document without the hidden macro calibration part by inputting the product macro.
The generated external interface document is provided for the client, so that the client can look up and use the document conveniently. Meanwhile, because the interfaces corresponding to the original interface document can not be completely disclosed, the parts which are not disclosed to the outside in the original interface document can be calibrated through the hidden macro, then the updated original interface document is read by using a script tool, and the external interface document which does not contain the calibration parts of the hidden macro can be generated by inputting the product macro.
Further, still include:
defining the product macros of different products corresponding to the original interface document under the same architecture;
defining the format of the original interface document, and updating the original interface document aiming at the product macro of different products;
and reading the updated original interface document by using the script tool, and generating the corresponding header file and/or external interface document by inputting the product macro of the corresponding product.
In actual operation, under the same architecture, the original interface document may support multiple products, and the interfaces of the products have different details, so different product macros need to be defined for different products.
Further, after the product macro defining different products corresponding to the original interface document under the same architecture, the method further includes the steps of:
determining the inclusion relationship of each interface;
calibrating interfaces belonging to different products through the product macro;
the interface belonging to the common portion is not limited.
Further, the scripting tool is a VBA scripting tool. In other embodiments, other scripting tools having the same functionality as the VBA scripting tool may be selected
VBA, namely Visual Basic for Applications, is a macro language of Visual Basic, is a programming language for executing general automation (OLE) tasks in desktop Applications thereof, and can be mainly used for extending application functions of Windows, in particular Microsoft Office software.
In addition, in this scheme, the VBA script tool needs to: identifying ' PROUDUCT _ A ' and ' content ' information in the middle of ' < PROUDUCT _ A > content </PROUDUCT _ A >; identifying "< -client info: client data information- >" intermediate "client info" and "client data information" information, the former being used as a structure name and the latter as a comment; identifying "_ INNER _" "secret" information in the middle of "_ INNER _ > secret </_ INNER _ >". "_ INNER _" is an externally hidden macro indicating that it is not possible to output to an externally interfaced document; a product macro generation header file and/or an external interface document can be specified; identifying key segment constant definitions, data structures, global variables and the like in an original interface document; the table and table contents can be identified and the desired contents output to the header file.
In addition, the present invention also provides a software interface maintenance system, including:
the definition module is used for defining the product macro corresponding to the original interface document;
the updating module is used for correspondingly updating the original interface document when the interface is updated;
the generating module is used for reading the updated original interface document by using a script tool when the original interface document is updated by the updating module, and generating a corresponding header file and/or an external interface document by inputting the product macro defined by the defining module;
and the compiling module is connected with the generating module and used for updating the header file to a code base and carrying out compiling test when the header file is generated.
The product macro corresponding to the original interface document is defined by the definition module, so that when the interface is updated, the original interface document is updated only by the update module, then the updated original interface document is read by the generation module by using a script tool, and the product macro is input to generate a corresponding header file and/or an external interface document. According to the scheme, only the original interface document needs to be updated, so that the maintenance workload is reduced, and the centralized control of the interface on the source is facilitated; meanwhile, when the header file is acquired, the product macro is input into the script tool to generate output from the original interface document, so that the inconsistency between the external interface document and the header file can be avoided, the updated interface parameters displayed in a form in the external interface document can be conveniently checked, and the reading of a client is facilitated.
Further, if the generation module generates an external interface document and the content of the updated original interface document part is not disclosed to the outside, calibrating the part which is not disclosed to the outside in the original interface document by a hidden macro, reading the updated original interface document by using a script tool, and generating the external interface document which does not contain the hidden macro calibration part by inputting the product macro.
Further, the definition module is further configured to define the product macros of different products corresponding to the original interface document under the same architecture;
the updating module is also used for defining the format of the original interface document and updating the original interface document aiming at the product macros of different products;
the generating module is further configured to read the updated original interface document using the script tool, and generate the corresponding header file and/or the external interface document by inputting the product macro of the corresponding product.
In addition, the present invention also provides a computer device comprising:
the memory is used for storing the running program;
and the processor is used for executing the running program stored in the memory and realizing the operation executed by the software interface maintenance method.
In addition, the present invention also provides a storage medium, where at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the operation performed by the software interface maintenance method.
According to the software interface maintenance method, the system, the computer equipment and the storage medium provided by the invention, by defining the product macro corresponding to the original interface document, when the interface is updated, only the original interface document needs to be updated, the updated original interface document is read by using a script tool, and the product macro is input to generate the corresponding header file. According to the scheme, only the original interface document needs to be updated, so that the maintenance workload is reduced, and the centralized control of the interface on the source is facilitated; meanwhile, when the head file is obtained, the product macro is input into the script tool to generate output from the original interface document, so that the inconsistency of the interface document and the head file can be avoided, the updated interface parameters displayed in a form in the interface document can be conveniently checked, and the reading of a client is facilitated.
Drawings
The foregoing features, technical features, advantages and embodiments of the present invention will be further explained in the following detailed description of the preferred embodiments, which is to be read in connection with the accompanying drawings.
FIG. 1 is a schematic flow diagram of one embodiment of the present invention;
FIG. 2 is a schematic diagram of a system architecture of an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
Reference numbers in the figures: 1-defining a module; 2-updating the module; 3-a generating module; 4-a compiling module; 100-a memory; 200-a processor; 300-a communication interface; 400-a communication bus; 500-input/output interface.
Detailed Description
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically illustrated or only labeled. In this document, "one" means not only "only one" but also a case of "more than one".
Example 1
An embodiment of the present invention, as shown in fig. 1, provides a software interface maintenance method, including the steps of:
and S1, defining the product macro corresponding to the original interface document.
In the scheme, the original interface document is used as a unique source, any interface change is completed in the original interface document, revision records are made, and the inclusion relation of each interface can be determined by defining the product macro corresponding to the original interface document.
And S2, correspondingly updating the original interface document when the interface is updated.
In the prior art, a common maintenance method is that a software header file is modified every time an original interface document is changed, and only the header file is maintained, and then conversion tools such as Docco, Dexy, Doxygen, TurnAPI and the like are used for reading the header file and generating an external interface document; when the interface is updated, the corresponding original interface document is directly updated, and then the updated original interface document generates a header file and/or an external interface document, specifically:
and S3, reading the updated original interface document by using a script tool, and generating a corresponding header file and/or an external interface document by inputting the product macro.
Preferably, in this embodiment, the scripting tool is a VBA scripting tool, and in other embodiments, other scripting tools having the same function as the VBA scripting tool may also be used.
VBA, namely Visual Basic for Applications, is a macro language of Visual Basic, is a programming language for executing general automation (OLE) tasks in desktop Applications thereof, and can be mainly used for extending application functions of Windows, in particular Microsoft Office software.
In addition, in this scheme, the VBA script tool needs to: identifying ' PROUDUCT _ A ' and ' content ' information in the middle of ' < PROUDUCT _ A > content </PROUDUCT _ A >; identifying "< -client info: client data information- >" intermediate "client info" and "client data information" information, the former being used as a structure name and the latter as a comment; identifying "_ INNER _" "secret" information in the middle of "_ INNER _ > secret </_ INNER _ >". "_ INNER _" is an externally hidden macro indicating that it is not possible to output to an externally interfaced document; a product macro generation header file or an external interface document can be specified; identifying key segment constant definitions, data structures, global variables and the like in an original interface document; the table and table contents can be identified and the desired contents output to the header file.
And S4, if the header file is generated, updating the header file to a code base, and performing compiling test. After the test is finished, the latest version of the corresponding product can be released.
According to the scheme, the product macro corresponding to the original interface document is defined, so that when the interface is updated, only the original interface document needs to be updated, the updated original interface document is read by using a script tool, and the product macro is input to generate the corresponding header file and/or the external interface document. According to the scheme, only the original interface document needs to be updated, so that the maintenance workload is reduced, and the centralized control of the interface on the source is facilitated; meanwhile, when the header file is acquired, the product macro is input into the script tool to generate output from the original interface document, so that the inconsistency between the external interface document and the header file can be avoided, the updated interface parameters displayed in a form in the external interface document can be conveniently checked, and the reading of a client is facilitated.
Example 2
An embodiment of the present invention, on the basis of embodiment 1, uses a script tool to read the updated original interface document, and generates a corresponding header file and/or external interface document by inputting the product macro, and further includes the steps of:
if the external interface document is generated and the content of the updated original interface document part is not disclosed to the outside, calibrating the part which is not disclosed to the outside in the original interface document through the hidden macro.
And reading the updated original interface document by using a script tool, and generating an external interface document without a hidden macro calibration part by inputting the product macro.
The generated external interface document is provided for the client, so that the client can look up and use the document conveniently. Meanwhile, because the interfaces corresponding to the original interface document can not be completely disclosed, the parts which are not disclosed to the outside in the original interface document can be calibrated through the hidden macro, then the updated original interface document is read by using a script tool, and the external interface document which does not contain the calibration parts of the hidden macro can be generated by inputting the product macro.
Example 3
An embodiment of the present invention, on the basis of embodiment 1 or 2, further includes: and defining product macros of different products corresponding to the original interface documents under the same architecture.
The format of the original interface document is defined, and the original interface document is updated for product macros of different products.
And reading the updated original interface document by using a script tool, and generating a corresponding header file and/or an external interface document by inputting a product macro of a corresponding product.
Preferably, after defining product macros of different products corresponding to the original interface documents under the same architecture, the method further includes the steps of:
determining the inclusion relationship of each interface; calibrating interfaces belonging to different products through product macro; the interface belonging to the common portion is not limited.
In actual operation, under the same architecture, the original interface document may support multiple products, and the interfaces of the products have different details, so different product macros need to be defined for different products.
Specifically, if the original interface document of the same architecture is needed to support product A, B of type 2, there are some detail differences on the A, B interface. Two product macros are defined to distinguish between A and B: PROUDUCT _ A, PROUDUCT _ B.
The content belonging to the product A is limited in < PROUDUCT _ A > … … </PROUDUCT _ A >, and the content belonging to the product B is limited in < PROUDUCT _ B > … … </PROUDUCT _ B >, so that the extraction or filtering processing of a VBA script tool is facilitated.
The format of the original interface document is defined as follows:
[ definitions of constants ]
[ data Structure ]
< -SERVERINFO server data information- >
< -CLIENTINFO client data information- >)
[ Global variables ]
SERVERINFO gServerDataInfo; // server data information Global variables
CLIENTINFO gClientDataInfo; // client data information Global variables
<_INNER_>
int gTimerLenSet [8] ═ {1,2,4,5,8,10,16,20 }; // Timer timing value set
</_INNER_>。
(1) If the header a.h of the product a needs to be generated, the following header is generated by inputting the prosuct _ a macro when the VBA script tool is run:
//a.h is header file for PROUDUCT_A
// constant definition
const int mailboxx _ MAX is 1024; // maximum number of mailbox resources
const int SERVER _ TCP _ PORT 9003; // Server side TCP port number
const int CLIENT _ CONNECT _ MAX equals to 100; // maximum number of client connections
const char PRODUCT NAME [50] "PRODUCT a"; // product display name
// data Structure
struct server info// server data information
{
char server ip [15 ]; // Server IP Address
int server Port; // Server Port number
}
struct CLIENTINFO// client data information
{
char clientName [50 ]; // client name
char clientIp [15 ]; // client IP Address
int clientReq; // customer request language (A product requirement)
}
v/Global variables
SERVERINFO gServerDataInfo; // server data information Global variables
CLIENTINFO gClientDataInfo; // client data information Global variables
int gTimerLenSet [8] ═ {1,2,4,5,8,10,16,20 }; // Timer timing value set.
(2) If the header b.h of the B product needs to be generated, the following header is generated by inputting the prosuct _ B macro when the VBA script tool is run:
//b.h is header file for PROUDUCT_B
// constant definition
const int mailboxx _ MAX 512; // maximum number of mailbox resources
const int SERVER _ TCP _ PORT 9003; // Server side TCP port number
const int CLIENT _ CONNECT _ MAX is 50; // maximum number of client connections
const char PRODUCT _ NAME [50] ═ B PRODUCT; // product display name
// data Structure
struct server info// server data information
{
char server ip [15 ]; // Server IP Address
int server Port; // Server Port number
}
struct CLIENTINFO// client data information
{
char clientName [50 ]; // client name
char clientIp [15 ]; // client IP Address
int clientAck; // customer answer language (B product requirement)
}
v/Global variables
SERVERINFO gServerDataInfo; // server data information Global variables
CLIENTINFO gClientDataInfo; // client data information Global variables
int gTimerLenSet [8] ═ {1,2,4,5,8,10,16,20 }; // Timer timing value set.
(3) If an external interface document of an A product needs to be output, a PROUDUCT _ A macro needs to be input when a VBA script tool is run, and the following external interface document is generated:
[ definitions of constants ]
[ data Structure ]
< -SERVERINFO server data information- >
< -CLIENTINFO client data information- >)
[ Global variables ]
SERVERINFO gServerDataInfo; // server data information Global variables
CLIENTINFO gClientDataInfo; // client data information global variables.
(4) If the external interface document of the B product needs to be output, the PROUDUCT _ B macro needs to be input when the VBA script tool is run, and the following external interface document is generated:
[ definitions of constants ]
[ data Structure ]
< -SERVERINFO server data information- >
< -CLIENTINFO client data information- >)
[ Global variables ]
SERVERINFO gServerDataInfo; // server data information Global variables
CLIENTINFO gClientDataInfo; // client data information global variables.
Example 4
An embodiment of the present invention, as shown in fig. 2, further provides a software interface maintenance system, which includes a definition module 1, an update module 2, a generation module 3, and a compiling module 4.
The definition module 1 is used for defining the product macro corresponding to the original interface document.
In the scheme, the original interface document is used as a unique source, any interface change is completed in the original interface document, revision records are made, and the inclusion relation of each interface can be determined by defining the product macro corresponding to the original interface document.
The updating module 2 is used for correspondingly updating the original interface document when the interface is updated.
In the prior art, a common maintenance method is that a software header file is modified every time an original interface document is changed, and only the header file is maintained, and then conversion tools such as Docco, Dexy, Doxygen, TurnAPI and the like are used for reading the header file and generating an external interface document; when the interface is updated, the corresponding original interface document is directly updated, and then the updated original interface document generates a header file and/or an external interface document, specifically:
the generating module 3 is used for reading the updated original interface document by using a script tool when the original interface document is updated by the updating module 2, and generating a corresponding header file and/or an external interface document by the product macro defined by the input defining module 1.
Preferably, in this embodiment, the scripting tool is a VBA scripting tool, and in other embodiments, other scripting tools having the same function as the VBA scripting tool may also be used.
VBA, namely Visual Basic for Applications, is a macro language of Visual Basic, is a programming language for executing general automation (OLE) tasks in desktop Applications thereof, and can be mainly used for extending application functions of Windows, in particular Microsoft Office software.
In addition, in this scheme, the VBA script tool needs to: identifying ' PROUDUCT _ A ' and ' content ' information in the middle of ' < PROUDUCT _ A > content </PROUDUCT _ A >; identifying "< -client info: client data information- >" intermediate "client info" and "client data information" information, the former being used as a structure name and the latter as a comment; identifying "_ INNER _" "secret" information in the middle of "_ INNER _ > secret </_ INNER _ >". "_ INNER _" is an externally hidden macro indicating that it is not possible to output to an externally interfaced document; a product macro generation header file or an external interface document can be specified; identifying key segment constant definitions, data structures, global variables and the like in an original interface document; the table and table contents can be identified and the desired contents output to the header file.
The compiling module 4 is connected with the generating module 3 and used for updating the header file to the code base and carrying out compiling test when the header file is generated. After the test is finished, the latest version of the corresponding product can be released.
The product macro corresponding to the original interface document is defined by the definition module 1, so that when the interface is updated, only the original interface document needs to be updated by the update module 2, and then the updated original interface document is read by the generation module 3 by using a script tool and the product macro is input to generate a corresponding header file and/or an external interface document. According to the scheme, only the original interface document needs to be updated, so that the maintenance workload is reduced, and the centralized control of the interface on the source is facilitated; meanwhile, when the header file is acquired, the product macro is input into the script tool to generate output from the original interface document, so that the inconsistency between the external interface document and the header file can be avoided, the updated interface parameters displayed in a form in the external interface document can be conveniently checked, and the reading of a client is facilitated.
Example 5
In an embodiment of the present invention, if the generation module 3 generates an external interface document and the contents of the updated original interface document are not disclosed to the outside, the hidden macro is used to calibrate the part of the original interface document which is not disclosed to the outside, a script tool is used to read the updated original interface document, and the product macro is input to generate the external interface document which does not include the hidden macro calibration part.
The generated external interface document is provided for the client, so that the client can look up and use the document conveniently. Meanwhile, because the interfaces corresponding to the original interface document can not be completely disclosed, the part which is not disclosed to the outside in the original interface document can be limited by the hidden macro, and then the updated original interface document is read by using a script tool, and the external interface document which does not contain the calibration part of the hidden macro can be generated by inputting the product macro.
Preferably, in this scheme, the defining module 1 is further configured to define product macros of different products corresponding to an original interface document in the same architecture; the updating module 2 is also used for defining the format of the original interface document and updating the original interface document aiming at the product macros of different products; the generating module 3 is further configured to read the updated original interface document using a script tool, and generate a corresponding header file and/or the external interface document by inputting a product macro of a corresponding product.
In actual operation, under the same architecture, the original interface document may support multiple products, and the interfaces of the products have different details, so different product macros need to be defined for different products. The specific operation can be referred to example 3, and is not described herein redundantly.
Example 6
In addition, as shown in fig. 3, the present invention further provides a computer device, which includes a memory 100 and a processor 200, where the memory 100 is used to store an operating program, and the processor 200 is used to execute the operating program stored in the memory, so as to implement the operations performed by the software interface maintenance method according to any one of embodiments 1 to 3.
Specifically, the computer device may further include a communication interface 300, a communication bus 400 and an input/output interface 500, wherein the processor 200, the memory 100, the input/output interface 500 and the communication interface 300 are communicated with each other through the communication bus 400.
A communication bus 400 is a circuit that connects the elements described and enables transmission between these elements. For example, the processor 200 receives commands from other elements through the communication bus 400, decrypts the received commands, and performs calculations or data processing according to the decrypted commands. The memory 100 may include program modules such as a kernel (kernel), middleware (middleware), an Application Programming Interface (API), and applications. The program modules may be comprised of software, firmware or hardware, or at least two of the same. The input/output interface 500 forwards commands or data entered by a user via an input/output device (e.g., sensor, keyboard, touch screen). The communication interface 300 connects the computer device with other network devices, user devices, networks. For example, the communication interface 300 may be connected to a network by wire or wirelessly to connect to external other network devices or user devices. The wireless communication may include at least one of: wireless fidelity (WiFi), Bluetooth (BT), Near Field Communication (NFC), Global Positioning Satellite (GPS) and cellular communications, among others. The wired communication may include at least one of: universal Serial Bus (USB), high-definition multimedia interface (HDMI), asynchronous transfer standard interface (RS-232), and the like. The network may be a telecommunications network and a communications network. The communication network may be a computer network, the internet of things, a telephone network. The computer device may connect to the network through the communication interface 300, and a protocol by which the computer device communicates with other network devices may be supported by at least one of an application, an Application Programming Interface (API), middleware, a kernel, and a communication interface.
Example 7
In addition, the present invention further provides a storage medium, where at least one instruction is stored, and the instruction is loaded and executed by a processor to implement the operation performed by the software interface maintenance method according to any one of embodiments 1 to 3. For example, the computer readable storage medium may be a read-only memory (ROM), a random-access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like. They may be implemented in program code that is executable by a computing device such that it may be stored in a memory device and executed by the computing device, or they may be separately fabricated into various integrated circuit modules, or multiple modules or steps thereof may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
It should be noted that the above embodiments can be freely combined as necessary. The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for maintaining a software interface, comprising the steps of:
defining a product macro corresponding to the original interface document;
when the interface is updated, the original interface document is correspondingly updated;
reading the updated original interface document by using a script tool, and generating a corresponding header file and/or an external interface document by inputting the product macro;
and if the header file is generated, updating the header file to a code base, and performing compiling test.
2. The method for maintaining software interface according to claim 1, wherein the script tool reads the updated original interface document and generates the corresponding header file and/or external interface document by inputting the product macro, further comprising the steps of:
if the external interface document is generated and the updated part of the original interface document is not disclosed to the outside, calibrating the part which is not disclosed to the outside in the original interface document through a hidden macro;
and reading the updated original interface document by using a script tool, and generating the external interface document without the hidden macro calibration part by inputting the product macro.
3. The software interface maintenance method of claim 1, further comprising:
defining the product macros of different products corresponding to the original interface document under the same architecture;
defining the format of the original interface document, and updating the original interface document aiming at the product macro of different products;
and reading the updated original interface document by using the script tool, and generating the corresponding header file or the external interface document by inputting the product macro of the corresponding product.
4. The method of claim 3, wherein after defining the product macros of different products corresponding to the original interface document under the same architecture, the method further comprises the following steps:
determining the inclusion relationship of each interface;
calibrating interfaces belonging to different products through the product macro;
the interface belonging to the common portion is not limited.
5. A software interface maintenance method according to any one of claims 1 to 4, characterized in that: the script tool is a VBA script tool.
6. A software interface maintenance system, comprising:
the definition module is used for defining the product macro corresponding to the original interface document;
the updating module is used for correspondingly updating the original interface document when the interface is updated;
the generating module is used for reading the updated original interface document by using a script tool when the original interface document is updated by the updating module, and generating a corresponding header file and/or an external interface document by inputting the product macro defined by the defining module;
and the compiling module is connected with the generating module and used for updating the header file to a code base and carrying out compiling test when the header file is generated.
7. A software interface maintenance system according to claim 6, wherein:
if the generation module generates an external interface document and the contents of the updated original interface document part are not disclosed to the outside, calibrating the part which is not disclosed to the outside in the original interface document through a hidden macro, reading the updated original interface document by using a script tool, and generating the external interface document which does not contain the calibration part of the hidden macro by inputting the product macro.
8. A software interface maintenance system according to claim 6, wherein:
the definition module is further used for defining the product macros of different products corresponding to the original interface document under the same architecture;
the updating module is also used for defining the format of the original interface document and updating the original interface document aiming at the product macros of different products;
the generating module is further configured to read the updated original interface document using the script tool, and generate the corresponding header file and/or the external interface document by inputting the product macro of the corresponding product.
9. A computer device, comprising:
the memory is used for storing the running program;
a processor for executing the operating program stored in the memory to implement the operations performed by the software interface maintenance method according to any one of claims 1 to 5.
10. A storage medium, characterized by: the storage medium has at least one instruction stored therein, and the instruction is loaded and executed by a processor to implement the operations performed by the software interface maintenance method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110067562.8A CN112764731A (en) | 2021-01-19 | 2021-01-19 | Software interface maintenance method, system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110067562.8A CN112764731A (en) | 2021-01-19 | 2021-01-19 | Software interface maintenance method, system, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112764731A true CN112764731A (en) | 2021-05-07 |
Family
ID=75703125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110067562.8A Pending CN112764731A (en) | 2021-01-19 | 2021-01-19 | Software interface maintenance method, system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112764731A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090138846A1 (en) * | 2007-11-23 | 2009-05-28 | Microsoft Corporation | Extended macro recording |
| CN101681621A (en) * | 2007-05-17 | 2010-03-24 | 微软公司 | Speech recognition macro runtime |
| CN103186377A (en) * | 2011-12-30 | 2013-07-03 | 鸿富锦精密工业（深圳）有限公司 | Intelligent code generation system and method |
| CN109857670A (en) * | 2019-02-15 | 2019-06-07 | 太仓市同维电子有限公司 | A kind of test report automatic generation method based on common template |
| CN110297651A (en) * | 2019-06-18 | 2019-10-01 | 广州华多网络科技有限公司 | The update method and device of the common variable of protocol interface |
| CN111857663A (en) * | 2020-07-17 | 2020-10-30 | 济南浪潮数据技术有限公司 | Software design method, system, electronic equipment and storage medium |
| CN112148302A (en) * | 2020-09-23 | 2020-12-29 | 北京自如信息科技有限公司 | Interface document generation method, device, equipment and readable storage medium |
-
2021
- 2021-01-19 CN CN202110067562.8A patent/CN112764731A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101681621A (en) * | 2007-05-17 | 2010-03-24 | 微软公司 | Speech recognition macro runtime |
| US20090138846A1 (en) * | 2007-11-23 | 2009-05-28 | Microsoft Corporation | Extended macro recording |
| CN103186377A (en) * | 2011-12-30 | 2013-07-03 | 鸿富锦精密工业（深圳）有限公司 | Intelligent code generation system and method |
| CN109857670A (en) * | 2019-02-15 | 2019-06-07 | 太仓市同维电子有限公司 | A kind of test report automatic generation method based on common template |
| CN110297651A (en) * | 2019-06-18 | 2019-10-01 | 广州华多网络科技有限公司 | The update method and device of the common variable of protocol interface |
| CN111857663A (en) * | 2020-07-17 | 2020-10-30 | 济南浪潮数据技术有限公司 | Software design method, system, electronic equipment and storage medium |
| CN112148302A (en) * | 2020-09-23 | 2020-12-29 | 北京自如信息科技有限公司 | Interface document generation method, device, equipment and readable storage medium |
Non-Patent Citations (4)
| Title |
|---|
| R KOLB.ET AL: "A Refactoring a legacy component for reuse in a software product line: a case study", 《IEEE》 * |
| 徐植: "基于动模实验平台的上位机软件研究与开发", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 05 * |
| 朱国防等: "软件产品线技术简介", 《信息技术与信息化》, no. 02 * |
| 郑飞虎: "参数化产品文档快速生成系统", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 03 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210109742A1 (en) | Dynamically Deploying a Web Component in an Application | |
| US9442744B2 (en) | Multilingual build integration for compiled applications | |
| US20230308504A9 (en) | Method and system of application development for multiple device client platforms | |
| US7920852B2 (en) | Compression of data transmitted between server and mobile device | |
| US20070078925A1 (en) | Porting an interface defining document between mobile device platforms | |
| JP2010176336A (en) | Client program, terminal, method, server system, and server program | |
| CN105335132B (en) | Method, device and system for customizing application program function | |
| JP2022529178A (en) | Features of artificial intelligence recommended models Processing methods, devices, electronic devices, and computer programs | |
| CN111026439B (en) | Application program compatibility method, device, equipment and computer storage medium | |
| CN111045683A (en) | Applet code compiling method, device, equipment and medium | |
| EP1199643A1 (en) | Method and apparatus for providing data adapted to a user environment | |
| CN109144619A (en) | Icon font information processing method, apparatus and system | |
| JP2005285105A (en) | Method and apparatus for generating communication message instance, and method for generating data instance | |
| CN113746840A (en) | JSON format message generation method and device | |
| US8082528B2 (en) | Process-independent schema library | |
| CN112764731A (en) | Software interface maintenance method, system, computer equipment and storage medium | |
| JP7014960B2 (en) | Information processing equipment, servers, their processing methods and programs | |
| CN114661402A (en) | Interface rendering method and device, electronic equipment and computer readable medium | |
| US7805715B2 (en) | Model publishing framework | |
| CN111949296A (en) | Data updating method and device | |
| WO2013088534A1 (en) | Server and method for accessing portable terminal via network from client, and program allowing computer to function as said server | |
| WO2021232909A1 (en) | Remote function customization method and apparatus, device, and storage medium | |
| CN112639730A (en) | Method, device and system for writing and running processing of program file | |
| KR102560619B1 (en) | Electronic device providing no-code tool service and method thereof | |
| JP5965661B2 (en) | Display screen conversion apparatus, display screen conversion method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |