Unified configuration method, system and equipment for software modules and storage medium

Abstract

The invention relates to the technical field of software services, and particularly provides a unified configuration method, system and device for software modules and a storage medium, and the method comprises the following steps: creating a component window, a tool window and a configuration window in a graphical interface; a developed software module is obtained, and basic description information of the software module is collected; generating a corresponding component icon for the software module based on the basic description information of the software module, and outputting the component icon to the component window; component icons in a component display window are dragged to a configuration window, a matched data flow indication arrow is dragged to the position between the component icons of the configuration window, and a configuration framework is constructed; and generating a configuration rule based on the configuration architecture, and performing rationality verification on the configuration rule based on the basic description information of the software module. According to the method, the configuration accuracy is improved, the configuration period is shortened, and the system can be put into operation more quickly.

Description

Technical Field

[0001] The present invention belongs to the technical field of software services, and in particular relates to a unified configuration method, system, device and storage medium for software modules. Background Art

[0002] In short, modular design does not mean to write a program by entering computer statements and instructions one by one from the beginning, but to first describe the main structure and execution flow of the software in a macro sense by building high-level frameworks such as main programs, subroutines, and subprocesses. In this process, the input and output links between various frameworks (or modules) are also clearly defined and debugged to ensure that they can work together to form a fully functional whole.

[0003] Traditional software systems often have difficulty adapting to the ever-changing market demands, especially in terms of function expansion and system configuration. Faced with this situation, the SaaS (Software as a Service) model came into being, providing a more flexible service method. However, although SaaS has achieved remarkable results in improving system flexibility, it still faces difficulties such as high system configuration complexity and low configuration efficiency. In order to solve these problems, the industry continues to explore and practice more efficient and concise modular configuration methods, striving to reduce configuration difficulty and improve configuration efficiency while ensuring system flexibility, so as to better meet market needs and user expectations. Summary of the invention

[0004] In view of the above-mentioned deficiencies in the prior art, the present invention provides a unified configuration method, system, device and storage medium for software modules to solve the above-mentioned technical problems.

[0005] In a first aspect, the present invention provides a unified configuration method for software modules, comprising: Creating a component window, a tool window and a configuration window in a graphical interface, wherein the tool window includes a data flow indication arrow; Acquire the developed software module and collect basic description information of the software module, wherein the basic description information includes module name, function information, interface information and supported data formats; generating a corresponding component icon for the software module based on the basic description information of the software module, and outputting the component icon to the component window; Build the configuration architecture by dragging the component icons in the component display window to the configuration window, and dragging the matching data flow indicator arrows between the component icons in the configuration window; A configuration rule is generated based on the configuration architecture, and a rationality check is performed on the configuration rule based on the basic description information of the software module.

[0006] In an optional embodiment, a component window, a tool window and a configuration window are created in a graphical interface, wherein the tool window contains a data flow indication arrow, including: Using a window creation tool to create a component window, a tool window, and a configuration window, and setting the layout of the component window, the tool window, and the configuration window in the graphical interface; Add drag and resize controls to component windows, tool windows, and configuration windows; A plurality of arrow tools are added to the tool window, the colors of the arrow tools are unique, and the colors and the data formats have a one-to-one mapping relationship.

[0007] In an optional implementation, a developed software module is obtained, and basic description information of the software module is collected, wherein the basic description information includes function information, interface information, and supported data formats, including Obtain the program files and basic description information of the software module; Generating a statistical list of software modules based on the basic description information of the software modules; A module list generated during the software development phase is obtained, and the statistical list is compared with the module list for consistency. If the two are consistent, it is determined that the program files of all software modules are obtained.

[0008] In an optional implementation, generating a corresponding component icon for the software module based on the basic description information of the software module, and outputting the component icon to the component window includes: Cleaning the basic description information and converting the cleaned basic description information into a preset standard format; According to the basic description information of the software module, a mapping rule from information to component icons is established, wherein the mapping rule defines how to convert information such as function description, interface information and data format into specific elements in the component icon; Applying the mapping rule to generate a unique component icon for each software module; The generated component icon is dynamically output to the component window of the graphical user interface.

[0009] In an optional implementation, the mapping rule is applied to generate a unique component icon for each software module, including: Pre-built icon library; Icons matching the function information, interface information and data format are selected from the icon library, and the icons are named using the module name.

[0010] In an optional implementation, generating a configuration rule based on the configuration architecture, and performing a rationality check on the configuration rule based on the basic description information of the software module includes: Analyze the initially built configuration architecture, including identifying the various software modules, the connection relationships between software modules, and the properties and configuration parameters of the software modules; Generate corresponding configuration rules based on the parsed structure, wherein the configuration rules include connection rules between components, data transmission rules, and processing logic rules; By comparing the generated configuration rules with the basic description information of the software module, check whether the software module in the configuration rules actually exists, whether the connection relationship is correct, and whether the data transmission and processing logic match the functions and interfaces of the software module.

[0011] In a second aspect, the present invention provides a unified configuration system for software modules, comprising: An interface processing module, used to create a component window, a tool window and a configuration window in a graphical interface, wherein the tool window includes a data flow indication arrow; An information acquisition module is used to acquire the developed software module and collect basic description information of the software module, wherein the basic description information includes module name, function information, interface information and supported data formats; An icon generation module, used to generate a corresponding component icon for the software module based on the basic description information of the software module, and output the component icon to the component window; An architecture building module, used to build a configuration architecture by dragging component icons in a component display window to a configuration window, and dragging matching data flow indicator arrows between component icons in the configuration window; A rule generation module is used to generate configuration rules based on the configuration architecture and perform rationality verification on the configuration rules based on the basic description information of the software module.

[0012] In an optional embodiment, the interface processing module includes: A window creation unit, used to create a component window, a tool window and a configuration window using a window creation tool, and to set the layout of the component window, the tool window and the configuration window in the graphical interface; Window management unit, used to add drag and drop controls and size adjustment controls to component windows, tool windows, and configuration windows; The tool adding unit is used to add multiple arrow tools in the tool window, the colors of the arrow tools are unique, and the colors and data formats have a one-to-one mapping relationship.

[0013] In a third aspect, a device is provided, comprising: A memory, used for storing a unified configuration program of the software modules; The processor is used to implement the steps of the unified configuration method of software modules provided in the first aspect when executing the unified configuration program of the software modules.

[0014] In a fourth aspect, a computer-readable storage medium is provided, on which a unified configuration program for software modules is stored. When the unified configuration program for software modules is executed by a processor, the steps of the unified configuration method for software modules provided in the first aspect are implemented.

[0015] The beneficial effect of the present invention is that the unified configuration method, system, device and storage medium of the software module provided by the present invention greatly reduces the chance of human intervention through the drag-and-drop operation of the graphical interface and the automated verification process, thereby reducing the configuration errors caused by operational errors. This not only improves the accuracy of the configuration, but also shortens the configuration cycle, so that the system can be put into operation more quickly.

[0016] In addition, the invention has a reliable design principle, a simple structure and a very broad application prospect. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention.

[0019] Figure 2 It is a schematic diagram of a graphical visualization interface of a method according to an embodiment of the present invention.

[0020] Figure 3 is a schematic block diagram of a system according to an embodiment of the present invention.

[0021] Figure 4 A schematic diagram of the structure of a device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0024] The unified configuration method of software modules provided in the embodiment of the present invention is executed by a computer device, and accordingly, the unified configuration system of software modules runs in the computer device.

[0025] Figure 1 is a schematic flow chart of a method according to an embodiment of the present invention. Figure 1 The execution subject may be a unified configuration system of a software module. According to different requirements, the order of the steps in the flow chart may be changed, and some may be omitted.

[0026] like Figure 1 As shown, the method includes: S1. Create a component window, a tool window and a configuration window in a graphical interface, wherein the tool window includes a data flow indication arrow.

[0027] In the graphical user interface, users can create multiple key windows, including component windows, tool windows, and configuration windows. Specifically, the tool window is an area that integrates a variety of auxiliary tools, and it especially contains a set of data flow indicator arrows, which are used to visually represent the data transmission path between various components in the subsequent steps.

[0028] S2. Acquire a developed software module and collect basic description information of the software module, wherein the basic description information includes module name, function information, interface information and supported data formats.

[0029] In the preparation phase, the system first obtains a series of developed software modules from the existing resource library. These software modules represent the various functional units in the system or application. Next, the system will collect detailed information about these software modules, mainly to obtain their basic description information. This information is comprehensive and specific, covering the module name (used to identify and distinguish different modules), functional information (a brief description of the functions that the module can achieve), interface information (listing the interfaces and parameters for the module to interact with other modules), and supported data formats (indicating the type of data that the module can process or output).

[0030] S3. Generate a corresponding component icon for the software module based on the basic description information of the software module, and output the component icon to the component window.

[0031] After obtaining the basic description information of the software module, the system will generate a unique component icon for each software module based on this information. These icons are not only visually recognizable, but also reflect the functional characteristics of the module to a certain extent. Subsequently, these carefully designed component icons will be automatically output to the component window for users to select and drag when building system configurations.

[0032] S4. Build a configuration architecture by dragging component icons in the component display window to the configuration window, and dragging matching data flow indicator arrows between the component icons in the configuration window.

[0033] Entering the configuration stage, users can move component icons in the component window to the configuration window by simply dragging. At this point, the configuration window becomes the core area of ​​system configuration, used to display and edit various components and their relationships. In order to further clarify the data flow between components, users can drag the matching data flow indicator arrow in the tool window to the configuration window and accurately place it between two component icons to establish a data transmission path between them.

[0034] S5. Generate configuration rules based on the configuration architecture, and perform rationality check on the configuration rules based on the basic description information of the software module.

[0035] When the configuration architecture is initially built, the system will automatically generate a series of configuration rules based on the current configuration architecture. These rules define in detail the connection methods of each component, the data transmission order, and the necessary processing logic. In order to ensure the correctness and rationality of the configuration, the system will once again use the basic description information of the software module obtained previously to conduct a comprehensive verification of the generated configuration rules. This verification process can promptly discover and correct errors or unreasonable aspects in the configuration, thereby ensuring that the final system can run stably and meet the design requirements.

[0036] To facilitate understanding of the present invention, the unified configuration method for software modules provided by the present invention is further described below based on the principle of the unified configuration method for software modules of the present invention and in combination with the process of uniformly configuring software modules in the embodiment.

[0037] In an embodiment of the present invention, based on step S1, a possible embodiment is given below to illustrate its specific implementation scheme in a non-limiting manner.

[0038] Use the window creation tool to create component windows, tool windows and configuration windows, and set the layout of the component windows, tool windows and configuration windows in the graphical interface; add drag controls and size adjustment controls to the component windows, tool windows and configuration windows; add multiple arrow tools to the tool window, the colors of the arrow tools are unique, and the colors have a one-to-one mapping relationship with the data format.

[0039] Specifically, Figure 2 It demonstrates the modular design of the system, clearly represents the relationship between services and rules, and completes rule configuration by dragging and dropping components.

[0040] First, through the window creation tool, three key windows can be created: component window, tool window and configuration window. These windows play different roles in the graphical interface. The component window is used to display the icons of the available software module components, the tool window integrates a variety of auxiliary tools, especially a set of data flow indicator arrows used to represent the data transmission path, and the configuration window is the core area of ​​the system configuration, which is used to display and edit various components and their relationships.

[0041] After creating these windows, you need to set their layout in the graphical interface reasonably. The layout setting should not only take into account the aesthetics, but also ensure that users can easily drag, drop and edit. Therefore, you can use grid layout, free layout or flow layout, and make flexible adjustments according to actual needs.

[0042] Next, in order to improve the user experience and ease of operation, drag controls and resize controls will be added to the component window, tool window, and configuration window. The drag control allows users to move the window or the component icon in the window by simply dragging, while the resize control allows users to adjust the size of the window or component icon as needed. The addition of these controls makes it easier for users to perform configuration operations.

[0043] In the tool window, add multiple arrow tools to represent the data transmission path between components in the configuration window. To improve readability and accuracy, a unique color is set for each arrow tool, and there is a one-to-one mapping relationship between these colors and data formats. In this way, users can intuitively judge the path and format of data transmission by the color of the arrow.

[0044] For example, if a component outputs text data, the arrow connected to it can be set to blue; if it outputs image data, the arrow can be set to green, and so on. This mapping relationship between color and data format not only helps users quickly understand system configuration, but also provides convenience in subsequent system maintenance and debugging.

[0045] In summary, by using window creation tools to create component windows, tool windows, and configuration windows, and by reasonably setting their layouts, adding drag controls and size adjustment controls, and adding arrow tools with unique colors and mapping relationships in tool windows, you can build an intuitive, easy-to-use, and powerful graphical user interface for building and managing system configurations.

[0046] In an embodiment of the present invention, based on step S2, a possible embodiment is given below to illustrate its specific implementation scheme in a non-limiting manner.

[0047] Obtain program files and basic description information of software modules; generate a statistical list of software modules based on the basic description information of the software modules; obtain the module list generated during the software development phase, and compare the statistical list with the module list for consistency. If the two are consistent, it is determined that the program files of all software modules have been obtained.

[0048] First, obtain the program files of each software module from the software development team or software warehouse. These program files contain the specific implementation code of the software module and are the basis for building the system configuration. At the same time, obtain the basic descriptive information associated with each software module. This basic information usually includes the module name, version number, function description, interface definition, input and output parameters, supported data formats and other key contents. This information is crucial for subsequent system configuration, data interaction between modules and the overall operation of the system.

[0049] After obtaining the program files and basic description information of the software modules, a statistical list of software modules is generated based on this information. This list will list in detail all the acquired software modules and their basic information, such as module name, version number, etc. This statistical list not only helps us clearly understand the current situation of the acquired software modules, but also facilitates subsequent comparison and verification work.

[0050] Next, obtain the module list generated during the software development phase. This list is usually prepared by developers in the early stages of software development based on system requirements and design documents. It lists in detail all the software modules required by the system and their relationships. By comparing the statistical list with the module list, verify whether the program files of all the software modules required by the system have been obtained.

[0051] During the specific comparison process, check whether all the software modules in the statistical list appear in the module list, and whether their version numbers and function descriptions are consistent. If the two are completely consistent, then we can determine that we have successfully obtained the program files of all the software modules required by the system. The completion of this step indicates that the important foundation of system configuration work has been laid, providing strong support for subsequent system integration, testing and deployment.

[0052] In summary, by obtaining the program files and basic description information of the software modules, a statistical list of the software modules is generated, and a consistency comparison is performed with the module list generated in the software development phase to ensure that all software modules required for the system configuration have been successfully obtained, laying a solid foundation for subsequent system development work.

[0053] In an embodiment of the present invention, based on step S3, a possible embodiment is given below to illustrate its specific implementation scheme in a non-limiting manner.

[0054] S301. Clean the basic description information and convert the cleaned basic description information into a preset standard format.

[0055] After obtaining the basic description information of the software module, due to the diversity of information sources, there may be problems such as inconsistent data formats, redundant information, missing or incorrect information. Therefore, we first need to clean this information. The cleaning process includes removing redundant information, filling in missing information, correcting incorrect information, etc. Through this step, the quality of data for subsequent processing is ensured.

[0056] After the cleaning process is completed, the processed basic description information is converted into a pre-set standard format. This standard format is designed according to system requirements and subsequent processing procedures. It specifies the organizational structure, data type and encoding rules of the information. Converting information into a standard format helps to automate the subsequent steps and reduce human errors.

[0057] S302. According to the basic description information of the software module, establish a mapping rule from information to component icons, wherein the mapping rule defines how to convert information such as function description, interface information and data format into specific elements in the component icon.

[0058] In order to convert the basic description information of the software module into the component icon in the graphical user interface, a set of mapping rules is established. This set of mapping rules defines how to convert information such as function description, interface information and data format into specific elements in the component icon. For example, the function description can be converted into the text description in the icon, the interface information can be converted into the interface identifier in the icon, and the data format can be converted into the color or pattern in the icon.

[0059] The establishment of mapping rules needs to be designed according to system requirements and user experience to ensure that the converted component icons can intuitively reflect the basic characteristics and functions of the software modules.

[0060] S303. Apply the mapping rule to generate a unique component icon for each software module.

[0061] After the mapping rules are established, these rules are applied to generate a unique component icon for each software module. This icon not only contains the basic description information of the software module, but also distinguishes different software modules through specific design elements (such as color, pattern, text, etc.). The unique component icon helps users quickly identify and select the required software module in the graphical user interface.

[0062] In a specific example, the process of generating a component icon includes: In the early stages of software development and system configuration, a rich icon library should be pre-built based on possible software module types, functions, interfaces, and data formats. This icon library should contain a variety of icon elements that may be used, such as different shapes, colors, patterns, and texts. These elements can be combined and modified as needed to generate component icons that meet the requirements.

[0063] When building an icon library, consider the following aspects: Diversity of icon elements: Make sure the icon library contains enough elements to meet the needs of different software modules.

[0064] Icon customizability: Allows icon elements to be combined and modified according to specific needs to generate unique component icons.

[0065] Icon readability and intuitiveness: Ensure that the generated component icons can intuitively reflect the basic features and functions of the software module, making it easy for users to identify and select.

[0066] After obtaining the basic description information of the software module, select the matching icons from the pre-built icon library based on this information. During the screening process, pay attention to the following aspects: Matching of functional information: According to the functional description of the software module, select icon elements that can intuitively reflect the function.

[0067] Matching of interface information: According to the interface information of the software module, select icon elements that can represent the interface type and connection method.

[0068] Data format matching: According to the data format supported by the software module, select an icon element that can represent the data format, such as a specific color or pattern.

[0069] In order to facilitate subsequent management and use, name each generated component icon. The naming method can use the name of the software module, which can ensure a one-to-one correspondence between the icon name and the software module it represents. By naming, icons can be quickly identified and used, improving the efficiency of system configuration.

[0070] In summary, by pre-building an icon library, selecting icons that match the functional information, interface information, and data format from the icon library, and naming the icons using the module names, unique and intuitive component icons are generated for software modules. These icons not only help users quickly identify and select the required software modules in the graphical user interface, but also provide strong support for subsequent system configuration work.

[0071] S304. Dynamically output the generated component icon to the component window of the graphical user interface.

[0072] The generated component icons are dynamically output to the component window of the graphical user interface. This window is an important interface for users to interact with the system. It displays all available software module component icons. By dynamically outputting component icons, users can obtain the latest software module information at any time and select and configure them as needed.

[0073] The dynamic output process can be achieved through programming, which usually involves the updating of graphical interface and event processing. Through this step, an intuitive, easy-to-use and powerful graphical user interface is provided to users for the construction and management of system configuration.

[0074] In summary, through steps S301 to S304, the basic description information of the software module is converted into component icons in the graphical user interface, and provides strong support for subsequent system configuration work.

[0075] In an embodiment of the present invention, based on step S4, a possible embodiment is given below to illustrate its specific implementation scheme in a non-limiting manner.

[0076] Users can drag the required component icons from the component window to the configuration window to build the preliminary configuration of the system. Users need to drag the data flow indicator arrows from the tool window to the corresponding component icons in the configuration window according to the data transmission relationship between the software modules to indicate the data transmission path. That is, users can drag the service components from the toolbar to the workspace through drag operations, and connect the service components through connecting lines to define the execution order and dependency relationship between services.

[0077] In addition, each service component can be configured with parameters, such as input data, output data, execution conditions, etc. Users can set these parameters through the configuration interface to meet different business needs. Supports automatic configuration, users can pre-set configuration files, and the system automatically completes the deployment and adjustment of services and rules based on the configuration files. Automatic configuration not only improves the deployment efficiency of the system and reduces errors caused by human intervention, but also enables the system to quickly adapt to changing needs.

[0078] In an embodiment of the present invention, based on step S5, a possible embodiment is given below to illustrate its specific implementation in a non-limiting manner.

[0079] S501. Analyze the initially constructed configuration architecture, including identifying various software modules, connection relationships between software modules, and properties and configuration parameters of software modules.

[0080] After the configuration architecture is built, it is analyzed in depth to ensure its accuracy and effectiveness. This step mainly includes the following sub-steps: Identify individual software modules: First, identify all included software modules from the configuration architecture and confirm their names, versions, and whether they have been correctly imported into the system.

[0081] Identify the connection relationship between software modules: Next, analyze the connection relationship between each software module in detail, including the data transmission path, connection sequence, and connection conditions between them.

[0082] Identify properties and configuration parameters of software modules: In addition, the properties and configuration parameters of each software module are parsed to understand their configuration requirements, performance parameters, and how they interact with other modules.

[0083] S502. Generate corresponding configuration rules based on the parsed structure, wherein the configuration rules include connection rules between components, data transmission rules, and processing logic rules.

[0084] After parsing the configuration architecture, the corresponding configuration rules are generated based on its structure. These rules will guide the system on how to correctly connect, transmit data and process logic. Specific rules include: Connection rules between components: Based on the analyzed software module connection relationships, establish connection rules between components to ensure that each module can be connected in the expected manner.

[0085] Data transmission rules: According to the analyzed data transmission path and conditions, formulate data transmission rules to ensure that data can be correctly transmitted between modules.

[0086] Processing logic rules: Based on the analyzed software module properties and configuration parameters, formulate processing logic rules to clarify the logic and algorithms that each module needs to follow when processing data.

[0087] S503. By comparing the generated configuration rules with the basic description information of the software module, check whether the software module in the configuration rules actually exists, whether the connection relationship is correct, and whether the data transmission and processing logic matches the function and interface of the software module.

[0088] To ensure that the generated configuration rules match the actual requirements of the software module, compare them with the basic description information of the software module. This step mainly includes the following sub-steps: Check whether the software module actually exists: First, confirm whether the software module referenced in the configuration rule actually exists in the system, and check whether its version is consistent with the description information.

[0089] Check whether the connection relationship is correct: Next, check whether the connection relationship defined in the configuration rules is consistent with the connection relationship obtained by parsing, and ensure that they conform to the actual interaction mode between software modules.

[0090] Check whether the data transmission and processing logic match the functions and interfaces of the software modules: Finally, check whether the data transmission and processing logic defined in the configuration rules match the functions and interfaces of the software modules to ensure that the system can operate as expected.

[0091] Finally, a configuration file is generated based on the configuration rules. The configuration file can be in XML, JSON and other formats to describe the system's services and rule configuration. The configuration file can be written and modified through an editor for easy maintenance and management.

[0092] Automatically deploy and adjust services and rules based on configuration files, reducing errors and time consumption in manual operations. The automatic deployment process includes initialization of services, loading of rules, and application of configurations.

[0093] Before actual operation, the simulation test function is supported. Users can test the configuration effect in a simulation environment to ensure the stability and efficiency of the system during real operation. Simulation testing can discover and solve potential problems in advance, reducing failures and downtime in actual operation.

[0094] In some embodiments, the unified configuration system of software modules may include multiple functional modules composed of computer program segments. The computer programs of each program segment in the unified configuration system of software modules may be stored in a memory of a computer device and executed by at least one processor to perform (see Figure 1 Description) The function of unified configuration of software modules.

[0095] In this embodiment, the unified configuration system of the software modules can be divided into multiple functional modules according to the functions they perform, such as Figure 3 As shown. The functional modules of the system 300 may include: an interface processing module 310, an information acquisition module 320, an icon generation module 330, an architecture construction module 340 and a rule generation module 350. The module referred to in the present invention refers to a series of computer program segments that can be executed by at least one processor and can complete fixed functions, which are stored in a memory. In this embodiment, the functions of each module will be described in detail in subsequent embodiments.

[0096] An interface processing module, used to create a component window, a tool window and a configuration window in a graphical interface, wherein the tool window includes a data flow indication arrow; An information acquisition module is used to acquire the developed software module and collect basic description information of the software module, wherein the basic description information includes module name, function information, interface information and supported data formats; An icon generation module, used to generate a corresponding component icon for the software module based on the basic description information of the software module, and output the component icon to the component window; An architecture building module, used to build a configuration architecture by dragging component icons in a component display window to a configuration window, and dragging matching data flow indicator arrows between component icons in the configuration window; A rule generation module is used to generate configuration rules based on the configuration architecture and perform rationality verification on the configuration rules based on the basic description information of the software module.

[0097] Optionally, as an embodiment of the present invention, the interface processing module includes: A window creation unit, used to create a component window, a tool window and a configuration window using a window creation tool, and to set the layout of the component window, the tool window and the configuration window in the graphical interface; Window management unit, used to add drag and drop controls and size adjustment controls to component windows, tool windows, and configuration windows; The tool adding unit is used to add multiple arrow tools in the tool window, the colors of the arrow tools are unique, and the colors and data formats have a one-to-one mapping relationship.

[0098] Optionally, as an embodiment of the present invention, a developed software module is obtained, and basic description information of the software module is collected, wherein the basic description information includes function information, interface information and supported data formats, including Obtain the program files and basic description information of the software module; Generating a statistical list of software modules based on the basic description information of the software modules; A module list generated during the software development phase is obtained, and the statistical list is compared with the module list for consistency. If the two are consistent, it is determined that the program files of all software modules are obtained.

[0099] Optionally, as an embodiment of the present invention, generating a corresponding component icon for the software module based on the basic description information of the software module, and outputting the component icon to the component window includes: Cleaning the basic description information and converting the cleaned basic description information into a preset standard format; According to the basic description information of the software module, a mapping rule from information to component icons is established, wherein the mapping rule defines how to convert information such as function description, interface information and data format into specific elements in the component icon; Applying the mapping rule to generate a unique component icon for each software module; The generated component icon is dynamically output to the component window of the graphical user interface.

[0100] Optionally, as an embodiment of the present invention, applying the mapping rule to generate a unique component icon for each software module includes: Pre-built icon library; Icons matching the function information, interface information and data format are selected from the icon library, and the icons are named using the module name.

[0101] Optionally, as an embodiment of the present invention, generating a configuration rule based on the configuration architecture, and performing a rationality check on the configuration rule based on the basic description information of the software module includes: Analyze the initially built configuration architecture, including identifying the various software modules, the connection relationships between software modules, and the properties and configuration parameters of the software modules; Generate corresponding configuration rules based on the parsed structure, wherein the configuration rules include connection rules between components, data transmission rules, and processing logic rules; By comparing the generated configuration rules with the basic description information of the software module, check whether the software module in the configuration rules actually exists, whether the connection relationship is correct, and whether the data transmission and processing logic match the functions and interfaces of the software module.

[0102] Figure 4The unified configuration method of the software module provided for the embodiment of the present application can be applied to equipment. It will be appreciated by those skilled in the art that the equipment structure involved in the embodiment of the present invention does not constitute a limitation on the equipment, and the equipment may include more or less components than shown, or combine certain components, or different component arrangements. In an embodiment of the present invention, the equipment includes but is not limited to laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The equipment may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples, and are not intended to limit the implementation of the embodiments of the present application described herein and / or required.

[0103] The device 400 may include: a processor 410, a memory 420 and a communication unit 430. These components communicate via one or more buses. Those skilled in the art will appreciate that the server structure shown in the figure does not limit the present invention, and it may be a bus structure or a star structure, and may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently.

[0104] The memory 420 may be used to store the execution instructions of the processor 410, and the memory 420 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. When the execution instructions in the memory 420 are executed by the processor 410, the device 400 is enabled to perform some or all of the steps in the following method embodiments.

[0105] The processor 410 is the control center of the storage device, and uses various interfaces and lines to connect various parts of the entire electronic device. It runs or executes software programs and / or modules stored in the memory 420, and calls data stored in the memory to perform various functions of the electronic device and / or process data. The processor can be composed of an integrated circuit (IC), for example, it can be composed of a single packaged IC, or it can be composed of a plurality of packaged ICs with the same or different functions. For example, the processor 410 can include only a central processing unit (CPU). In an embodiment of the present invention, the CPU can be a single computing core or multiple computing cores.

[0106] The communication unit 430 is used to establish a communication channel so that the storage device can communicate with other devices, receive user data sent by other devices or send user data to other devices.

[0107] The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM).

[0108] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes, including several instructions for enabling a computer device (which can be a personal computer, a server, or a second device, a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention.

[0109] In this specification, the same or similar parts between the various embodiments can be referred to each other. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description in the method embodiment.

[0110] In the several embodiments provided by the present invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of systems or modules, which can be electrical, mechanical or other forms.

[0111] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0112] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0113] Although the present invention has been described in detail with reference to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person of ordinary skill in the art may easily think of changes or substitutions within the technical scope disclosed by the present invention, and these shall be within the scope of protection of the present invention.

Claims

1. A unified configuration method for software modules, characterized in that: include: Creating a component window, a tool window and a configuration window in a graphical interface, wherein the tool window includes a data flow indication arrow; Acquire the developed software module and collect basic description information of the software module, wherein the basic description information includes module name, function information, interface information and supported data formats; generating a corresponding component icon for the software module based on the basic description information of the software module, and outputting the component icon to the component window; Build the configuration architecture by dragging the component icons in the component display window to the configuration window, and dragging the matching data flow indicator arrows between the component icons in the configuration window; A configuration rule is generated based on the configuration architecture, and a rationality check is performed on the configuration rule based on the basic description information of the software module.

2. The method according to claim 1, characterized in that A component window, a tool window and a configuration window are created in a graphical interface, wherein the tool window contains a data flow indication arrow, including: Using a window creation tool to create a component window, a tool window, and a configuration window, and setting the layout of the component window, the tool window, and the configuration window in the graphical interface; Add drag and resize controls to component windows, tool windows, and configuration windows; A plurality of arrow tools are added to the tool window, the colors of the arrow tools are unique, and the colors and the data formats have a one-to-one mapping relationship.

3. The method according to claim 1, characterized in that: Obtain the developed software module and collect the basic description information of the software module, which includes function information, interface information and supported data formats, including Obtain the program files and basic description information of the software module; Generating a statistical list of software modules based on the basic description information of the software modules; A module list generated during the software development phase is obtained, and the statistical list is compared with the module list for consistency. If the two are consistent, it is determined that the program files of all software modules are obtained.

4. The method according to claim 1, characterized in that: Generating a corresponding component icon for the software module based on the basic description information of the software module, and outputting the component icon to the component window, including: Cleaning the basic description information and converting the cleaned basic description information into a preset standard format; According to the basic description information of the software module, a mapping rule from information to component icons is established, wherein the mapping rule defines how to convert information such as function description, interface information and data format into specific elements in the component icon; Applying the mapping rule to generate a unique component icon for each software module; The generated component icon is dynamically output to the component window of the graphical user interface.

5. The method according to claim 4, characterized in that Applying the mapping rules, a unique component icon is generated for each software module, including: Pre-built icon library; Icons matching the function information, interface information and data format are selected from the icon library, and the icons are named using the module name.

6. The method according to claim 1, characterized in that Generating configuration rules based on the configuration architecture, and performing rationality verification on the configuration rules based on the basic description information of the software module, including: Analyze the initially built configuration architecture, including identifying the various software modules, the connection relationships between software modules, and the properties and configuration parameters of the software modules; Generate corresponding configuration rules based on the parsed structure, wherein the configuration rules include connection rules between components, data transmission rules, and processing logic rules; By comparing the generated configuration rules with the basic description information of the software module, check whether the software module in the configuration rules actually exists, whether the connection relationship is correct, and whether the data transmission and processing logic match the functions and interfaces of the software module.

7. A unified configuration system for software modules, characterized in that: include: An interface processing module, used to create a component window, a tool window and a configuration window in a graphical interface, wherein the tool window includes a data flow indication arrow; An information acquisition module is used to acquire the developed software module and collect basic description information of the software module, wherein the basic description information includes module name, function information, interface information and supported data formats; An icon generation module, used to generate a corresponding component icon for the software module based on the basic description information of the software module, and output the component icon to the component window; An architecture building module, used to build a configuration architecture by dragging component icons in a component display window to a configuration window, and dragging matching data flow indicator arrows between component icons in the configuration window; A rule generation module is used to generate configuration rules based on the configuration architecture and perform rationality verification on the configuration rules based on the basic description information of the software module.

8. The system according to claim 7, characterized in that The interface processing module includes: A window creation unit, used to create a component window, a tool window and a configuration window using a window creation tool, and to set the layout of the component window, the tool window and the configuration window in the graphical interface; Window management unit, used to add drag and drop controls and size adjustment controls to component windows, tool windows, and configuration windows; The tool adding unit is used to add multiple arrow tools in the tool window, the colors of the arrow tools are unique, and the colors and data formats have a one-to-one mapping relationship.

9. A device, characterized in that: include: A memory, used for storing a unified configuration program of the software modules; A processor, configured to implement the steps of the method for unified configuration of software modules as claimed in any one of claims 1 to 6 when executing the unified configuration program of the software modules.

10. A computer-readable storage medium storing a computer program, characterized in that: The readable storage medium stores a unified configuration program of software modules, and when the unified configuration program of software modules is executed by a processor, the steps of the unified configuration method of software modules according to any one of claims 1 to 6 are implemented.

Images