Program data query method and device, equipment, medium and product

Abstract

The invention provides a program data query method which can be applied to the technical field of financial science and technology. The program data query method comprises the following steps: in response to an input operation in an input box of a program data query client, obtaining index content in the input box; according to the index content, a program list and a relation list in a pre-constructed program data query database are called, the program list comprises m programs, program types corresponding to the m programs and program attributes corresponding to the m programs, the relation list comprises program relations among the m programs and attributes of the program relations, m is an integer larger than or equal to 10, and the m is an integer larger than or equal to 10; the program data query database comprises a mapping relation among the index content, the program list and the relation list; and in response to a click on a download button of the program data query client, sending the program list and the relationship list to the program data query client. The invention further provides a program data query device and equipment, a storage medium and a program product.

Description

Technical Field

[0001] This application relates to the field of financial technology, specifically to a method, apparatus, device, medium, and program product for querying program data. Background Technology

[0002] Corporate online banking is a platform that integrates account management, group financial management, and online settlement, supplemented by finance departments, VIP rooms, and investment management. It combines asset and liability operations with integrated domestic and foreign currency cash management, serving as one of the channels through which banks provide internet services to corporate clients. With the increasing business demands and the standardization of various technologies, developers are increasingly requiring thorough code analysis when modifying programs. Furthermore, for a new developer taking on corporate online banking, the quickest way to get up to speed is by reading the code; however, developers new to corporate online banking code may feel overwhelmed by the sheer volume of code. Therefore, how to build a program data query system to help developers quickly clarify the functions and relationships within the program has become a pressing technical problem for those skilled in the art. Summary of the Invention

[0003] In view of the above problems, this application provides a method, apparatus, device, medium and program product for querying program data to help developers quickly clarify the functions and relationships of a program, thereby significantly shortening the familiarization cycle and quickly entering an efficient development state.

[0004] According to a first aspect of this application, a method for querying program data is provided, which, in response to an input operation in an input box of a program data query client, obtains the index content in the input box; based on the index content, retrieves a program list and a relationship list from a pre-constructed program data query database, wherein the program list includes m programs, program types corresponding to the m programs, and program attributes corresponding to the m programs, and the relationship list includes program relationships between the m programs and attributes of the program relationships, where m is an integer greater than or equal to 10, and the program data query database includes a mapping relationship between the index content, the program list, and the relationship list; and in response to clicking the download button of the program data query client, sends the program list and the relationship list to the program data query client.

[0005] In some examples, the method for querying program data further includes: in response to clicking the select file button on the program data query client, obtaining an updated program list and an updated relationship list, wherein the updated program list includes a list of added, deleted, and / or modified programs, and the updated relationship list includes a list of added, deleted, and / or modified relationships; and in response to clicking the upload file button on the program data query client, storing the updated program list and the updated relationship list in the program data query database.

[0006] In some examples, the method for querying program data further includes: in response to clicking the download template button of the program data query client, obtaining a template that conforms to the storage format requirements of the program data query database for the updated program list and the updated relationship list.

[0007] In some examples, the step of pre-constructing a program data query database includes: obtaining m programs from the application code library; defining the program types of the m programs; obtaining the program attributes of the m programs; integrating the m programs, their corresponding program types, and their corresponding program attributes to obtain a program list; defining the program relationships between the m programs; obtaining the attributes of the program relationships; integrating the program relationships between the m programs and their attributes to obtain a relationship list; and storing the program list and the relationship list in the program data query database.

[0008] In some examples, the step of defining the program types of the m programs includes: matching each of the m programs in a pre-built program type library, and defining the matched program type as the program type of that program, wherein the program type library includes a mapping relationship between programs and program types.

[0009] In some examples, the steps of pre-building a program type library include integrating specifications from the application framework, web design specifications, database specifications, and application design specifications to form a program type library.

[0010] A second aspect of this application provides a program data query apparatus, comprising: an acquisition module, configured to acquire index content in the input box in response to an input operation in the input box of a program data query client; a retrieval module, configured to retrieve a program list and a relationship list from a pre-built program data query database based on the index content, wherein the program data query database includes a mapping relationship between the index content, the program list, and the relationship list; and a sending module, configured to send the program list and the relationship list to the program data query client in response to a click on the download button of the program data query client.

[0011] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0012] A fourth aspect of this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0013] The fifth aspect of this application also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0014] The program data query method of this application embodiment can obtain the index content in the input box of the program data query client in response to the input operation. Based on the index content, a program list and a relationship list in a pre-built program data query database can be retrieved. The program list includes m programs, the corresponding program types of the m programs, and the corresponding program attributes of the m programs. The relationship list includes the program relationships between the m programs and the attributes of these relationships, where m is an integer greater than or equal to 10. In response to clicking the download button on the program data query client, the program list and relationship list can be sent to the program data query client. This application, by storing the program list and relationship list in the program data query database and configuring the export function of the program data query client (implemented through the input box and download button), can transform the constructed program graph (program-program relationship-program) into an interactive and queryable online service. Thus, the digitization and knowledge-based management of application assets can be realized. This application systematically transforms the scattered, unstructured programs in the application codebase into structured program and relationship lists through a pre-built program data query database. This creates a comprehensive and accurate digital twin of the entire application codebase, making its macro-structure and micro-relationships visible, understandable, and manageable. Developers no longer need to sift through countless lines of code and documentation; they can simply enter the index content into the program data query client and submit a query to instantly obtain a clearly structured and logically defined program and relationship list. A download button allows them to easily obtain a usable program and relationship list. This application breaks down the barriers between code, dependencies, and business functions, quickly helping developers clarify program functions and relationships. It fundamentally solves the pain points of developers facing massive amounts of code in complex applications—difficulty in organizing, slow learning curve, and high risk of changes—achieving a dual leap in development efficiency and application system stability. This significantly shortens the familiarization period and allows developers to quickly enter a highly efficient development state. Attached Figure Description

[0015] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0016] Figure 1 The illustrations depict application scenarios of a method, apparatus, device, medium, and program product for querying program data according to embodiments of this application.

[0017] Figure 2 A flowchart illustrating a method for querying program data according to an embodiment of this application is shown schematically.

[0018] Figure 3 A flowchart illustrating a pre-built program data query database according to an embodiment of this application is shown schematically;

[0019] Figure 4 This illustration schematically shows a page design diagram of a program data query client according to an embodiment of this application;

[0020] Figure 5 This schematic diagram illustrates the structural block diagram of a program data query device according to an embodiment of the present application;

[0021] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a method for querying program data according to an embodiment of this application. Detailed Implementation

[0022] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0023] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0024] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0025] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0026] In this document, unless otherwise specified, the term "electrical connection" refers to an electrical coupling relationship that enables the transmission of current, voltage or electrical signals through a conductor medium, including, but not limited to, the following: (1) a conductive connection through physical contact (e.g., a conductive connection through crimped wires, PCB pads, etc.); (2) an indirect connection through a conductor (e.g., a conductive connection through copper foil traces, shielded cables, etc.); and (3) a logic signal path (e.g., a conductive connection through microstrip lines, coaxial cables, etc.).

[0027] Corporate online banking is a platform that integrates account management, group financial management, and online settlement, supplemented by finance departments, VIP rooms, and investment management. It combines asset and liability operations with integrated domestic and foreign currency cash management, serving as one of the channels through which banks provide internet services to corporate clients. With the increasing business demands and the standardization of various technologies, developers are increasingly requiring thorough code analysis when modifying programs. Furthermore, for a new developer taking on corporate online banking, the quickest way to get up to speed is by reading the code; however, developers new to corporate online banking code may feel overwhelmed by the sheer volume of code. Therefore, how to build a program data query system to help developers quickly clarify the functions and relationships within the program has become a pressing technical problem for those skilled in the art.

[0028] Embodiments of this application provide a method, apparatus, electronic device, computer-readable storage medium, and computer program product for querying program data. The method for querying program data includes: in response to an input operation in an input box of a program data query client, obtaining index content in the input box; based on the index content, retrieving a program list and a relationship list from a pre-built program data query database, wherein the program list includes m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs, and the relationship list includes program relationships between the m programs and the attributes of those relationships, where m is an integer greater than or equal to 10, and the program data query database includes the mapping relationship between the index content, the program list, and the relationship list; in response to clicking the download button on the program data query client, sending the program list and the relationship list to the program data query client.

[0029] It should be noted that the method, apparatus, electronic device, computer-readable storage medium and computer program product for querying program data of this application can be used in the field of financial technology technology, and can also be used in any field other than the field of financial technology technology, such as the field of computer information technology. The field of this application is not limited here.

[0030] Figure 1 The illustrations depict application scenarios of a method, apparatus, device, medium, and program product for querying program data according to embodiments of this application.

[0031] like Figure 1 As shown, application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0032] Users can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 via the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0033] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0034] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0035] It should be noted that the program data query method provided in this application embodiment can generally be executed by server 105. Correspondingly, the program data query device provided in this application embodiment can generally be located in server 105. The program data query method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the program data query device provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0036] It should be understood that Figure 1The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0037] The following will be based on Figure 1 The described scene, through Figures 2-4 The method for querying program data according to the embodiments of this application will be described in detail.

[0038] Figure 2 A flowchart illustrating a method for querying program data according to an embodiment of this application is shown.

[0039] like Figure 2 As shown, the program data query method in this embodiment includes operations S110 to S130.

[0040] In operation S110, in response to the input operation in the input box of the program data query client, the index content in the input box is obtained.

[0041] In operation S120, based on the index content, the program list and relationship list in the pre-built program data query database are retrieved. The program list includes m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs. The relationship list includes the program relationships between the m programs and the attributes of the program relationships. m is an integer greater than or equal to 10.

[0042] In operation S130, in response to the click of the download button on the program data query client, the program list and relationship list are sent to the program data query client.

[0043] In some examples, the index content can be keywords entered in the input box that can locate the target program list and / or target relationship list. After locating the target program list and / or target relationship list by keywords, the target program list and / or target relationship list can be exported via the download button.

[0044] In some examples, the functional module to which the program belongs can have a function number, and the index content in the input box can be the function number. Through the function number, all programs under that functional module and the relationships between programs can be linked.

[0045] In some examples, the fields of the exported program listing may be as shown in Table 1, and the fields of the exported relation listing may be as shown in Table 2. The contents of Table 1 and Table 2 are set only to facilitate understanding of the ideas of this application and should not be regarded as a limitation of this application.

[0046] Table 1

[0047]

[0048] Table 2

[0049]

[0050] As some possible ways to achieve this, such as Figure 3 As shown, the steps of pre-constructing the program data query database may include operations S210 to S280.

[0051] In operation S210, obtain m programs from the application code library.

[0052] In some examples, an application codebase can include a collection of repositories containing all of the application's software assets and configuration metadata. In other words, an application codebase encompasses all executable components, configuration files, data definitions, and user interface elements required to implement the application's functionality. All executable components, configuration files, data definitions, and user interface elements can be understood as m programs.

[0053] In some examples, the program may include business logic code, database object definitions, system configuration metadata, and related resource files.

[0054] In some examples, business logic code can be understood as programs written based on the application framework, including XML files for orchestrating business processes and Java files for implementing specific business steps. Other Java files, JSP files, JavaScript files, and HTML files are used to implement the application's front-end and back-end logic.

[0055] In some examples, database object definitions may include definition scripts or metadata for database tables, stored procedures, functions, sequences, and synonyms, which are the core of business data storage and processing.

[0056] In some examples, system configuration metadata may include configuration information defining the user interface and function navigation, specifically configuration files or database tables containing menu IDs and function IDs. These configurations are themselves considered a kind of "program" because they are directly associated with background executable components.

[0057] In some examples, resource files may include XML configuration files and property files, which determine the system's behavior.

[0058] In operation S220, define the program types of m programs.

[0059] As one possible implementation method, the steps of defining the program types of m programs may include a matching operation.

[0060] Matching operation: Match each of the m programs against a pre-built program type library, and define the matched program type as the program type of that program. The program type library includes the mapping relationship between programs and program types. The matching operation makes it easy to define the program types of m programs.

[0061] Furthermore, the step of pre-building the program type library may include integration operations.

[0062] Integration Operation: Integrate the specifications, web design specifications, database specifications, and application design specifications in the application framework to form a program type library.

[0063] For ease of understanding, the matching and integration operations can be understood as the following process.

[0064] A program type library can be built, which can be understood as a concept dictionary. The content of the concept dictionary comes from the specifications in the application framework, web design specifications, database specifications, and application design specifications. The specifications in the application framework, web design specifications, database specifications, and application design specifications represent what types of programs should be in the application system (e.g., OP: business process orchestration document, OPSTEP: modular program for implementing specific business logic, TABLE: database table, MENU: user interface menu, FUNCID: function node, etc.).

[0065] Based on this, the m programs obtained in operation S210 can be scanned according to the concept dictionary. These m programs may include business logic code, database object definitions, system configuration metadata, and related resource files. Pattern matching is then performed between these m programs and the program type library. For example, matching an .xml file in the OP directory to the concept "OP" allows the program type of the .xml file in the OP directory to be defined as type OP. Similarly, matching a Java class called by OP to the concept "OPSTEP" allows the program type of the Java class called by OP to be defined as type OPSTEP. Furthermore, matching a table in the database to the concept "TABLE" allows the program type of the table in the database to be defined as type TABLE. Finally, matching a functional node in the configuration table to the concept "FUNCID" allows the program type of the functional node in the configuration table to be defined as type FUNCID.

[0066] By integrating the specifications in the application framework, web design specifications, database specifications, and application design specifications to form a program type library, it is easier to build a program type database.

[0067] In operation S230, obtain the program attributes of m programs.

[0068] In some examples, program attributes can be set and uploaded based on expert experience, thus allowing the acquisition of program attributes for m programs. Each program's program attributes can at least include whether the program is a public program, its functional module, and whether it contains invalid data.

[0069] Whether a program is public or not can be used to identify whether the program is a public program. Generally, for public programs, the caller does not need to further analyze its internal call chain. For special requirements, refer to the specific program's description, remarks, and other explanations.

[0070] A program may be called by multiple functional modules, but it needs to belong to a single functional module. Configuring the program's module affiliation attribute facilitates the division of labor and management for subsequent development and maintenance, clearly defining maintenance boundaries. For programs belonging to other functional modules, similar to common programs, the caller does not need to further analyze their internal call chains. For special requirements, refer to the specific program's description, comments, and other explanations.

[0071] The "Invalid Data" flag can be used to identify whether data is invalid in the program. Due to limitations in automatic identification rules, the results of automatic analysis may be inaccurate. Identified invalid data is marked as invalid here. The reason for not deleting it directly is that incremental automatic analysis can inherit the results of manual annotation, eliminating the need for repeated manual confirmation.

[0072] In operation S240, the m programs, their corresponding program types, and their corresponding program attributes are integrated to obtain a program listing. Here, the program listing can be as shown in Table 3. The content in Table 3 is only for the purpose of understanding the ideas of this application and should not be considered a limitation of this application.

[0073] Table 3

[0074]

[0075] In operation S250, define the program relationships between m programs.

[0076] It is understandable that, similar to the program type defined in operation S220, a database of program relationship templates can be pre-built, in which program relationships between m programs can be matched. For example, the program relationships can be shown in Table 4. The content in Table 4 is only set for the purpose of understanding the ideas of this application and should not be regarded as a limitation of this application. The stored procedure in the table represents a stored procedure.

[0077] Table 4

[0078]

[0079] In operation S260, obtain the attributes of the program relationship.

[0080] Understandably, similar to obtaining the program attributes of m programs in operation S230, the attributes of program relationships can be set and uploaded based on expert experience, thus allowing the acquisition of program relationship attributes. Each program relationship's attributes can at least include whether the data is invalid.

[0081] In operation S270, the program relationships and attributes of the program relationships between m programs are integrated to obtain a relationship list.

[0082] In operation S280, the program listing and relationship listing are stored in the program data query database.

[0083] Operations S210 to S280 facilitate the construction of a program data query database, laying the data foundation for exporting program listings and relationship lists via a program data query client. This application injects rich metadata into each program file by defining program types and obtaining program attributes, essentially giving each program a clear technical identity label (program type) and business attribution label (program attributes), thereby associating the program's technical role with its business value. By defining the program relationships between m programs and obtaining the attributes of these relationships, implicit dependencies originally hidden in the code text are made explicit and structured into data records in the relationship list. This transforms the process of finding and analyzing call chains between programs from requiring manual analysis to being queried from a database, improving the efficiency and accuracy of data query and analysis.

[0084] According to the program data query method of this application embodiment, the index content in the input box of the program data query client can be obtained in response to the input operation. Based on the index content, a program list and a relationship list in a pre-built program data query database can be retrieved. The program list includes m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs. The relationship list includes the program relationships between the m programs and the attributes of the program relationships, where m is an integer greater than or equal to 10. In response to clicking the download button of the program data query client, the program list and the relationship list can be sent to the program data query client. This application, by storing the program list and the relationship list in the program data query database and configuring the export function of the program data query client (implemented through the input box and the download button), can transform the constructed program graph (program-program relationship-program) into an interactive and queryable online service. Thus, the digitization and knowledge-based management of application assets can be realized. This application systematically transforms the scattered, unstructured programs in the application codebase into structured program and relationship lists through a pre-built program data query database. This creates a comprehensive and accurate digital twin of the entire application codebase, making its macro-structure and micro-relationships visible, understandable, and manageable. Developers no longer need to sift through countless lines of code and documentation; they can simply enter the index content into the program data query client and submit a query to instantly obtain a clearly structured and logically defined program and relationship list. A download button allows them to easily obtain a usable program and relationship list. This application breaks down the barriers between code, dependencies, and business functions, quickly helping developers clarify program functions and relationships. It fundamentally solves the pain points of developers facing massive amounts of code in complex applications—difficulty in organizing, slow learning curve, and high risk of changes—achieving a dual leap in development efficiency and application system stability. This significantly shortens the familiarization period and allows developers to quickly enter a highly efficient development state.

[0085] According to some embodiments of this application, the method for querying program data may further include a first acquisition operation and a storage operation.

[0086] First acquisition operation: In response to the click of the select file button in the program data query client, acquire the updated program list and the updated relationship list, wherein the updated program list includes the program list after addition, deletion and / or modification, and the updated relationship list includes the relationship list after addition, deletion and / or modification.

[0087] Storage operation: In response to the click of the upload file button on the program data query client, the updated program list and the updated relationship list are stored in the program data query database.

[0088] Understandably, after an application is deployed, architects will update it for various reasons, resulting in additions, deletions, and / or modifications to programs in the application codebase. Architects (developers) can download the program manifest and relationship manifest through the export menu (input box and download button). After updating the content that needs to be added, deleted, and / or modified, they can obtain updated program manifests and updated relationship manifests. Triggering the import function for program manifests and program relationships allows them to upload the updated program manifest and updated relationship manifests, which the program data query system can then store in the program data query database.

[0089] Therefore, the program data query database in this application, combined with the function of exporting program listings and relationship listings, can reduce the risk of code changes caused by unclear dependency relationships. Before making program modifications, developers can use this system to conduct precise impact analysis. By querying a program's out-degree (which program it calls) and in-degree (who calls it), all upstream and downstream programs that may be affected by the modification can be comprehensively and without omission. This makes the design of test cases more complete, effectively avoiding the chain reaction of modifying program A causing program B to malfunction in integration testing or production environments, greatly improving the reliability of software delivery and the stability of production systems.

[0090] In some examples, such as Figure 4 The page design of the program data query client shown can be configured with the function menu for importing program lists and program relationships as: Select File button and Upload File button.

[0091] In some examples, users can select the target updater list and target update relationship list to be uploaded via the "Select File" button. After selecting these lists, users can upload them to the program data query database via the "Upload File" button. Displaying the "Select File" and "Upload File" buttons facilitates user updates to the program data query database, thereby improving the real-time performance and effectiveness of the database.

[0092] In some examples, the fields of the imported program listing may be as shown in Table 5, and the fields of the imported relation listing may be as shown in Table 6. The contents of Tables 5 and 6 are set only to facilitate understanding of the ideas of this application and should not be regarded as a limitation of this application.

[0093] Table 5

[0094]

[0095] Table 6

[0096]

[0097] According to some embodiments of this application, the method for querying program data may further include a second acquisition operation.

[0098] The second retrieval operation: In response to clicking the download template button in the program data query client, the template is retrieved. The template conforms to the storage format requirements of the program data query database for updating the program list and updating the relationship list.

[0099] In some examples, such as Figure 4 The page design of the program data query client shown can also be configured with a "Download Template" button, where the template obtained in response to clicking the "Download Template" button conforms to the format requirements for updating the program list and updating the relationship list. The template fields can be as shown in Tables 5 and 6.

[0100] It is understandable that allowing data of arbitrary formats to flood the program data query database would severely impact its structured storage, potentially leading to data parsing failures, system anomalies, or data corruption. This application establishes a robust firewall before data flows into the system by setting data storage conditions that conform to the specified format. This ensures that the fields, types, and structures of updated data are consistent with the internal specifications of the program data query database, preventing system crashes or mismatches between updated and imported data caused by dirty or disordered data. This lays a solid foundation for subsequent highly reliable query analysis. Secondly, downloadable templates improve the efficiency and accuracy of manual corrections by architects, lowering the barrier to entry. Without templates, architects need to manually create files and accurately memorize or repeatedly consult complex field definitions (such as naming rules for program identifiers, type dictionaries of program relationships, and Boolean representations of invalid data). This process is not only tedious and inefficient but also prone to errors. The downloadable templates in this application simplify this complex process into three steps: "download, fill in, and upload." The template itself is a pre-structured file with built-in standard fields and data validation. It's like a standard fill-in-the-blank exam paper; architects only need to fill in the correction information in the designated places, without worrying about formatting issues. This significantly reduces the time and cognitive burden of manual operations, fundamentally solving the problem of import failures caused by formatting errors, making manual corrections quick and accurate. Furthermore, by providing downloadable templates and standardized import requirements, the import process can be transformed into a standardized, efficient, and high-quality workflow. This not only ensures the stability and integrity of the core database but also greatly improves the system's usability and human-computer collaboration efficiency, ultimately enhancing the accuracy and reliability of the entire program's data query database output results, making it a truly trustworthy engineering decision support tool.

[0101] Based on the above-described method for querying program data, this application also provides a device for querying program data. The following will be combined with... Figure 5 The device is described in detail.

[0102] Figure 5 The diagram illustrates the structure of a program data query device according to an embodiment of this application.

[0103] like Figure 5 As shown, the program data query device 10 includes a main acquisition module 1, a retrieval module 2, and a sending module 3.

[0104] The main acquisition module 1 is used to respond to input operations in the input box of the program data query client and acquire the index content in the input box.

[0105] The retrieval module 2 is used to retrieve the program list and relationship list from the pre-built program data query database based on the index content. The program list includes m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs. The relationship list includes the program relationships between the m programs and the attributes of the program relationships. m is an integer greater than or equal to 10. The program data query database includes the mapping relationship between the index content, the program list, and the relationship list.

[0106] The sending module 3 is used to send the program list and relationship list to the program data query client in response to the click of the download button on the program data query client.

[0107] According to some embodiments of this application, the program data query device may further include a first acquisition module and a storage module.

[0108] The first acquisition module is used to acquire an updated program list and an updated relationship list in response to a click on the select file button of the program data query client. The updated program list includes newly added, deleted, and / or modified program lists, and the updated relationship list includes newly added, deleted, and / or modified relationship lists.

[0109] The storage module is used to store the updated program list and the updated relationship list in the program data query database in response to the click of the upload file button of the program data query client.

[0110] According to some embodiments of this application, the program data query device may further include a second acquisition module.

[0111] The second acquisition module is used to acquire a template in response to clicking the download template button on the program data query client. The template conforms to the storage format requirements of the program data query database for the updated program list and the updated relationship list. According to some embodiments of this application, the program data query device may further include a main construction module, which is used to pre-build the program data query database. The main construction module includes a first acquisition unit, a first definition unit, a second acquisition unit, a first integration unit, a second definition unit, a third acquisition unit, a second integration unit, and a storage unit.

[0112] The first acquisition unit is used to acquire m programs from the application code library, where m is an integer greater than or equal to 10.

[0113] The first definition unit is used to define the program type of m programs.

[0114] The second acquisition unit is used to acquire the program attributes of m programs.

[0115] The first integration unit is used to integrate m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs to obtain a program list.

[0116] The second definition unit is used to define the program relationships between m programs.

[0117] The third acquisition unit is used to acquire the attributes of program relationships.

[0118] The second integration unit is used to integrate the program relationships and attributes of the program relationships among m programs to obtain a relationship list.

[0119] The storage unit is used to store the program listing and the relationship listing in the program data query database.

[0120] According to some embodiments of this application, the first defining unit may include defining elements.

[0121] The defined element is used to match each of the m programs in a pre-built program type library, and the matched program type is defined as the program type of that program. The program type library includes the mapping relationship between programs and program types.

[0122] According to some embodiments of this application, the program data query device may include a construction module for pre-building a program type library, and the construction module includes an integration unit. The integration unit is used to integrate specifications, web page design specifications, database specifications, and application design specifications in the application framework to form a program type library.

[0123] According to the program data query device of this application embodiment, in response to an input operation in the input box of the program data query client, the index content in the input box can be obtained; based on the index content, a program list and a relationship list in a pre-built program data query database can be retrieved, wherein the program list includes m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs, and the relationship list includes the program relationships between the m programs and the attributes of the program relationships, where m is an integer greater than or equal to 10; in response to clicking the download button of the program data query client, the program list and the relationship list can be sent to the program data query client. This application, by storing the program list and the relationship list in the program data query database and configuring the export function of the program data query client (implemented through the input box and the download button), can transform the constructed program graph (program-program relationship-program) into an interactive and queryable online service. Thus, the digitization and knowledge-based management of application assets can be realized. This application injects rich metadata into each program file by defining program types and obtaining program attributes, essentially giving the program a clear technical identity label (program type) and business attribution label (program attributes), thereby associating the program's technical role with its business value. By defining the program relationships between m programs and obtaining the attributes of these relationships, implicit dependencies originally hidden in the code text are made explicit and structured into data records in a relationship list. This transforms the call chain between programs from requiring manual analysis and searching into database queries, improving the efficiency and accuracy of data query and analysis. This application systematically transforms the scattered, unstructured programs in the application codebase into structured program and relationship lists through a pre-built program data query database, creating a panoramic and accurate digital twin of the entire application codebase. This makes the macro-structure and micro-relationships of the application codebase visible, understandable, and manageable. Developers no longer need to sift through countless codes and documents; they can simply enter the index content and submit a query through the program data query client to obtain a clearly structured and relationally defined program and relationship list with one click. A download button allows them to easily obtain a program and relationship list that they can use. This application breaks down the barriers between code, dependencies, and business functions, quickly helping developers to clarify the functions and relationships of the program. This fundamentally solves the pain points of developers facing massive amounts of code in complex applications, such as difficulty in sorting out the code, slow learning, and high risk of changes. It achieves a double leap in development efficiency and application system stability, thereby significantly shortening the familiarization cycle and quickly entering a state of efficient development.

[0124] According to embodiments of this application, any plurality of modules among the main acquisition module 1, the retrieval module 2, and the transmission module 3 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this application, at least one of the main acquisition module 1, the retrieval module 2, and the transmission module 3 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the main acquisition module 1, the retrieval module 2, and the transmission module 3 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0125] Figure 6 A block diagram schematically illustrates an electronic device suitable for the described method according to an embodiment of this application.

[0126] like Figure 6 As shown, an electronic device 900 according to an embodiment of this application includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0127] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0128] According to embodiments of this application, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the input / output (I / O) interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0129] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0130] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0131] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this application.

[0132] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this application embodiment. According to the embodiments of this application, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0133] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0134] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this application embodiment. According to the embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0135] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0136] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0137] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A method for querying program data, characterized in that, include: In response to an input operation in the input box of the program data query client, the index content in the input box is obtained; Based on the index content, retrieve the program list and relationship list from the pre-built program data query database. The program list includes m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs. The relationship list includes the program relationships between the m programs and the attributes of the program relationships. m is an integer greater than or equal to 10. The program data query database includes the index content, the mapping relationship between the program list and the relationship list. In response to a click of the download button on the program data query client, the program list and the relationship list are sent to the program data query client.

2. The method for querying program data according to claim 1, characterized in that, Also includes: In response to a click on the "Select File" button in the program data query client, an updated program list and an updated relationship list are obtained, wherein the updated program list includes newly added, deleted, and / or modified program lists, and the updated relationship list includes newly added, deleted, and / or modified relationship lists; In response to a click on the upload file button in the program data query client, the updated program list and the updated relationship list are stored in the program data query database.

3. The method for querying program data according to claim 2, characterized in that, Also includes: In response to clicking the download template button in the program data query client, a template is obtained, which conforms to the storage format requirements of the program data query database for the updated program list and the updated relationship list.

4. The method for querying program data according to claim 1, characterized in that, The steps for pre-building the program data query database include: Retrieve m programs from the application code library; Define the program type of the m programs; Obtain the program attributes of the m programs; By integrating the m programs, the program types corresponding to the m programs, and the program attributes corresponding to the m programs, a program list is obtained; Define the program relationships between the m programs; Obtain the attributes of the program relationship; By integrating the program relationships and attributes of the m programs, a relationship list is obtained; The program list and the relationship list are stored in the program data query database.

5. The method for querying program data according to claim 4, characterized in that, The steps for defining the program types of the m programs include: Each of the m programs is matched against a pre-built program type library, and the matched program type is defined as the program type of that program. The program type library includes a mapping relationship between programs and program types.

6. The method for querying program data according to claim 5, characterized in that, The steps for pre-building a program type library include: The application framework specifications, web page design specifications, database specifications, and application design specifications are integrated to form a program type library.

7. A device for querying program data, characterized in that, include: The acquisition module is used to acquire the index content in the input box in response to the input operation in the input box of the program data query client; The retrieval module is used to retrieve the program list and relationship list from a pre-built program data query database according to the index content, wherein the program data query database includes the mapping relationship between the index content, the program list and the relationship list; A sending module is configured to send the program list and the relationship list to the program data query client in response to a click on the download button of the program data query client.

8. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 6.

Images