A Software Engineering Configuration Management Method, Device, Medium and Program Product

Abstract

The present application discloses a software engineering configuration management method, device, medium and program product, relating to the technical field of software engineering. The method includes: obtaining the identity type of the operator of the current operation target engineering project; the identity type includes developers, testers and users; determining the module usage permissions of the operator according to the identity type, and screening out the target configuration modules from all the configuration modules corresponding to the target engineering project according to the module usage permissions; the configuration modules are pre-constructed for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; the configuration modules include macro definition modules, dynamic loading modules, and environment variable modules; generating a configuration interface based on the configuration file corresponding to the target configuration module, obtaining the project configuration information issued by the operator through the configuration interface, and performing corresponding operations according to the project configuration information. It can improve the software engineering configuration management ability.

Description

Technical Field

[0001] The present invention relates to the technical field of software engineering, and particularly relates to a software engineering configuration management method, device, medium and program product. Background Art

[0002] With the continuous development of science and technology, the scale and complexity of software engineering projects have grown exponentially, and engineering configuration management for software engineering projects has emerged as the times require. In related technologies, the configuration management method can meet basic configuration requirements, but in the face of large projects and multi-role collaboration, its maintainability and flexibility are poor, and there is a lack of a security mechanism, making configuration changes may lead to system vulnerabilities and be easily affected by misoperations. How to improve software engineering configuration management capabilities is an urgent problem to be solved at present. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a software engineering configuration management method, device, medium and program product, which can improve software engineering configuration management capabilities. The specific solutions are as follows:

[0004] In a first aspect, the present application discloses a software engineering configuration management method, including:

[0005] Obtain the identity type of the operator of the current operation target engineering project; the identity type includes developers, testers and users;

[0006] Determine the module usage permissions of the operator according to the identity type, and screen out the target configuration modules from all the configuration modules corresponding to the target engineering project according to the module usage permissions; the configuration modules are pre-constructed for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; the configuration modules include macro definition modules, dynamic loading modules, and environment variable modules;

[0007] Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the engineering configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the engineering configuration information.

[0008] Optionally, the construction process of the configuration module includes:

[0009] Classify the configuration items involved in the target engineering project according to preset configuration types to determine the configuration items corresponding to each configuration type; the configuration types include macro definition configuration, dynamic loading configuration, and environment variable configuration;

[0010] Generate the corresponding configuration modules based on the configuration items corresponding to each configuration type.

[0011] Optionally, the macro definition module is used to control the compilation of the target engineering project;

[0012] Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the project configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the project configuration information, including:

[0013] Obtain the configuration parameters for the configuration items in the macro definition module through the configuration interface;

[0014] Perform the compilation of the target engineering project according to the configuration items and corresponding configuration parameters of the macro definition module.

[0015] Optionally, the dynamic loading module is used to control the global variables during the operation of the target engineering project;

[0016] Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the project configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the project configuration information, including:

[0017] Obtain the configuration parameters for the configuration items of the dynamic loading module through the configuration interface;

[0018] Perform the operation test of the target engineering project according to the configuration items and corresponding configuration parameters of the dynamic loading module.

[0019] Optionally, the configuration items of the dynamic loading module further include a configuration scheme identifier;

[0020] Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the project configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the project configuration information, including:

[0021] Select a target test configuration scheme from all preset test configuration schemes according to the configuration scheme identifier;

[0022] Perform the operation test of the target engineering project according to the target test configuration scheme and the remaining configuration items and corresponding configuration parameters of the dynamic loading module.

[0023] Optionally, performing the operation test of the target engineering project according to the target test configuration scheme and the remaining configuration items and corresponding configuration parameters of the dynamic loading module includes:

[0024] According to the priority of configuration items, perform a running test on the target engineering project based on the target test configuration plan, the remaining configuration items of the dynamic loading module, and the corresponding configuration parameters; the priority of the configuration items of the dynamic loading module is higher than that of the configuration items in the target test configuration plan.

[0025] Optionally, the environment variable module is used to configure the basic environment parameters for system operation;

[0026] Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the project configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the project configuration information, including:

[0027] Through the configuration interface, obtain the configuration parameters of the configuration items for the environment variable module;

[0028] Run the target engineering project according to the configuration items of the environment variable module and the corresponding configuration parameters.

[0029] Optionally, the configuration items of the macro definition module include any one or more of the items to be tested, enabling / disabling of function modules, compilation version, code version;

[0030] The configuration items of the dynamic loading module include any one or more of cache-related, operator call, log output;

[0031] The configuration items of the environment variable module include any one or more of hardware usage settings, path configuration.

[0032] Optionally, after screening out the target configuration module from all the configuration modules corresponding to the target engineering project, it further includes:

[0033] Obtain the default configuration information corresponding to the target configuration module, and perform corresponding operations according to the default configuration information.

[0034] Optionally, the testers include internal testers and external testers;

[0035] Determine the module usage permissions of the operator according to the identity type, including:

[0036] Determine the module usage permissions of the operator according to the preset permission information and the identity type;

[0037] The preset permission information includes: developers and internal testers have the usage permissions for the macro definition module, dynamic loading module, and environment variable module; external testers have the usage permissions for the dynamic loading module and environment variable module; users have the usage permissions for the environment variable module.

[0038] Optionally, according to the module usage authority, screening out target configuration modules from all the configuration modules corresponding to the target engineering project includes:

[0039] Screening out target configuration modules from all the configuration modules corresponding to the target engineering project according to the module usage authority and the identifiers of the parsing interfaces corresponding to the configuration modules.

[0040] Optionally, before obtaining the identity type of the operator of the currently operated target engineering project, it further includes:

[0041] Generating a configuration file corresponding to each of the configuration modules based on the target data management format; the configuration items and configuration parameters of the configuration file are stored in the form of key-value pairs.

[0042] In a second aspect, the present application discloses an electronic device, including:

[0043] A memory for storing a computer program;

[0044] A processor for executing the computer program to implement the foregoing software engineering configuration management method.

[0045] In a third aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the foregoing software engineering configuration management method.

[0046] In a fourth aspect, the present application discloses a computer program product including a computer program; wherein the computer program, when executed by a processor, implements the foregoing software engineering configuration management method.

[0047] In this application, the identity type of the operator for the currently operated target engineering project is obtained; the identity types include developers, testers, and users; according to the identity type, the module usage permissions of the operator are determined, and according to the module usage permissions, target configuration modules are screened out from all the configuration modules corresponding to the target engineering project; the configuration modules are pre-built for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; the configuration modules include macro definition modules, dynamic loading modules, and environment variable modules; a configuration interface is generated based on the configuration files corresponding to the target configuration modules, and the engineering configuration information sent by the operator is obtained through the configuration interface, and corresponding operations are performed according to the engineering configuration information. It can be seen that the various configuration parameters are processed in modules, and a customized configuration interface is generated according to the permissions of the operator, so that operators of different identity types can safely and effectively manage the configurations they need. Whether it is developers, testers, or users, customized configuration content can be provided for them to meet their specific usage scenarios. Different configuration models are constructed according to the configuration items involved in different stages of the engineering project, and corresponding module usage permissions are set for operators of different identities, so as to efficiently organize and manage complex configuration data and improve the software engineering configuration management ability. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0049] Figure 1 It is a flowchart of a software engineering configuration management method provided by this application;

[0050] Figure 2 It is a specific flowchart of a software engineering configuration management method provided by this application;

[0051] Figure 3 It is a structural diagram of an electronic device provided by this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0052] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0053] In the prior art, the configuration management method can meet basic configuration requirements. However, when faced with large-scale projects and multi-role collaboration, its maintainability and flexibility are poor, and there is a lack of security mechanisms, making configuration changes likely to lead to system vulnerabilities and being easily affected by misoperations. To overcome the above technical problems, this application proposes a software engineering configuration management method that can improve the software engineering configuration management ability.

[0054] An embodiment of this application discloses a software engineering configuration management method. Refer to Figure 1 As shown, the method may include the following steps:

[0055] Step S11: Obtain the identity type of the operator of the current operation target engineering project; the identity type includes developers, testers, and users.

[0056] It can be understood that the complete life process of an engineering project generally includes development, testing, and delivery for use, corresponding to three main operators, namely developers, testers, and users. For each role, their requirements for the engineering configuration system are different. For example, developers need to be able to quickly enable or disable specific function modules for system experimentation and function verification; through convenient configuration, they can switch between different development stages and versions. Testers need to adjust certain parameters without recompiling the project after receiving the engineering project to quickly respond to test requirements; testers can be further divided into internal testers and external testers. Among them, internal testers can access the underlying code, while external testers can only access the compiled engineering project for security reasons and cannot access the underlying code. Users: need the simplest deployment method to ensure that the system can be seamlessly integrated into their existing infrastructure.

[0057] Step S12: Determine the module usage permissions of the operator according to the identity type, and screen out the target configuration modules from all the configuration modules corresponding to the target engineering project according to the module usage permissions; the configuration modules are pre-built for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; the configuration modules include macro definition modules, dynamic loading modules, and environment variable modules.

[0058] Since operators of different types have different configuration requirements, that is, different types of operators correspond to different operation stages of the engineering project, and the configuration items involved in different stages are different. Therefore, in this embodiment, the configuration items involved in different stages are classified to obtain different configuration modules, and different configuration modules are used for the configuration of different configuration items. Then, the usage permissions of the modules owned by the identity type are preset. In this embodiment, first, the identity type of the operator of the engineering project is determined, and then the module usage permissions of the operator are determined according to the identity type, that is, which configuration module or modules the operator has the usage permission of.

[0059] Among them, the configuration modules include a macro definition module, a dynamic loading module, and an environment variable module. The macro definition module mainly meets the needs of developers. Through the macro definition and conditional compilation functions during compilation, developers can quickly enable or disable function modules and support switching between different versions. The dynamic loading module is mainly for testers, supports adjusting global variables at runtime, allows modifying program behavior without recompiling, and quickly adapts to different test scenarios. The environment variable module is used to meet the needs of users, provides statically loaded environment variable configurations, simplifies the deployment process, and ensures compatibility with their existing infrastructure. To improve security and simplify the user experience, each operator can only access the modules related to them. For example, users only need to deliver or view the environment variable module without paying attention to or changing the macro definition and dynamic loading modules; testers need to use the environment variable module and the dynamic loading module to quickly adapt to different test scenarios; for developers, they need to use all three modules. This role permission control and module isolation not only ensure that each user only comes into contact with the configuration parts related to their functions, but also allows users to complete their tasks quickly and efficiently without dealing with complex configuration options.

[0060] In some embodiments, the testers include internal testers and external testers; as described above, determining the module usage permissions of the operator according to the identity type includes: determining the module usage permissions of the operator according to the preset permission information and the identity type; the preset permission information includes: developers and internal testers have the usage permissions of the macro definition module, the dynamic loading module, and the environment variable module; external testers have the usage permissions of the dynamic loading module and the environment variable module; users have the usage permission of the environment variable module.

[0061] In some embodiments, the construction process of the configuration module includes: classifying the configuration items involved in the target engineering project according to a preset configuration type to determine the configuration items corresponding to each configuration type; the configuration types include macro definition configuration, dynamic loading configuration, and environment variable configuration; generating the corresponding configuration module based on the configuration items corresponding to each configuration type. That is, the configuration items involved in the target engineering project are divided into one of the types of macro definition configuration, dynamic loading configuration, or environment variable configuration, so as to classify all configuration items.

[0062] Among them, screening out the target configuration module from all the configuration modules corresponding to the target engineering project according to the module usage permission may include: screening out the target configuration module from all the configuration modules corresponding to the target engineering project according to the module usage permission and the identifier of the parsing interface corresponding to each configuration module. That is, each configuration module has an independent parsing interface, making the configuration content clear; different configuration modules can be managed independently, reducing the risk of configuration conflicts. When specifically used, three sets of parsing codes can be configured to parse the three configuration modules respectively, and a preset keyword is used as the parsing interface to distinguish the three modules.

[0063] Step S13: Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the project configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the project configuration information.

[0064] It can be understood that all configuration items are stored in the configuration file in a modular manner. Among them, before obtaining the identity type of the operator of the current operation target engineering project, it also includes: generating a configuration file corresponding to each configuration module based on the target data management format; the configuration items and configuration parameters of the configuration file are stored in the form of key-value pairs. That is, the configuration files of different configuration modules are generated through a unified target data management format. Through modular design, independent management of different configuration categories is achieved; and these configurations are integrated into a single format configuration file, which not only improves the readability and maintainability of the configuration file, but also supports complex data structures to adapt to various configuration scenarios. The specific preparation process of software engineering configuration management is as Figure 2 shown. First, classify all configuration items through requirements analysis, then generate configuration files of different configuration modules based on a unified target data management format, and finally, design corresponding parsing interfaces for different configuration modules.

[0065] For example, YAML (Yet Another Markup Language) can be specifically used as the target data management format for writing the configuration management of multiple modules. Different parsing codes are designed according to the different requirements of multiple modules to complete the docking of configuration parameters and scripting languages. All configurations are managed and distributed through a unified interface. YAML is used as a file in the.yaml format and is supported by many programming languages and tools, with a good ecosystem, and can be easily integrated into the development and deployment processes of various engineering projects. The content of each of the following modules can be saved in YAML in the same key-value pair format, only the parsing logics used by different modules are different; therefore, designers only need to design three different parsing logics, and then use a single YAML file to achieve the simultaneous configuration and management of three modules. The generated configuration file includes: module name, name (i.e., configuration item), and value (i.e., configuration parameter). The value of name is a preset and unchangeable value, and the value of value is filled and modified according to requirements; through this configuration file, the interfaces of a large number of code function modules are integrated, which is easy for adding, maintaining, and managing configuration parameters.

[0066] Due to the above multi-module isolation mechanism, the system can easily generate different views according to users. For example, three configuration files can be simply used. Among them, the configuration files for developers and internal testers can access and modify all configuration items; the configuration file for external testers can only modify dynamically loaded and environment variables; the configuration file for end users can only modify environment variables; this role-customized management ensures security and flexibility. That is, developers have full access and modification permissions to all configuration modules and can flexibly create and update configuration parameters; internal testers can comprehensively test the system performance under various configuration parameters to ensure the stability and reliability of the system; external testers can adjust the dynamically loaded and environment variable modules without affecting the core compilation settings for extensive test coverage; end users are restricted to only modifying specific environment variables to ensure the security of the system core logic and engineering code. Through strict permission control and security measures, the system realizes secure and reliable configuration change control, protects sensitive information, and ensures the security and reliability of configuration management.

[0067] In addition, if the engineering configuration information is not obtained, corresponding operations can be performed according to the default configuration information corresponding to the target configuration module. That is, it supports presetting default configuration parameters, and the default configuration can be used when the configuration file is not accessed. When accessing the configuration file, it supports automatically parsing the configuration file and applying the configuration. Through scripts or configuration management tools, it can automatically deploy configuration changes, support rapid environment switching and configuration updates.

[0068] In some embodiments, the macro definition module is used to control the compilation of a target engineering project; the configuration items of the macro definition module include any one or more of items to be tested, enabling / disabling of function modules, compilation version, code version; a configuration interface is generated based on the configuration file corresponding to the target configuration module, engineering configuration information issued by the operator is obtained through the configuration interface, and corresponding operations are performed according to the engineering configuration information, including: obtaining, through the configuration interface, configuration parameters for the configuration items in the macro definition module; and performing compilation on the target engineering project according to the configuration items of the macro definition module and the corresponding configuration parameters.

[0069] That is, the macro definition module can be used to control the behavior during project compilation and is used before the compilation of the engineering project. That is, the macro definition module is an optional option for developers when compiling the engineering project, that is, whether to enable or disable the content of specific modules, so as to increase development and compilation efficiency, and enable rapid switching and experimentation of functions between different versions, reducing the time required to modify the code. This module can configure any options before compilation. Specifically, the functions that can be achieved include but are not limited to: items to be tested. When the developer adds / tests a specific operator / function, compile this content and the necessary content, and skip other content that does not need to be compiled to improve development efficiency; switching of whether to compile function modules, such as whether to compile the performance test / log printing / debugging module; code version switching. For example, when compiling, select a version with higher precision (such as double-precision floating-point arithmetic) or a version with better performance (such as single-precision floating-point arithmetic) to meet the requirements of specific application scenarios. For example, the configuration file of the macro definition module is as follows:

[0070] Definitions:

[0071] - name: ENABLE_TEST;

[0072] value: cos;

[0073] - name: ENABLE_FUNC;

[0074] value: PROFILER;

[0075] - name: ENABLE_VERSION;

[0076] value: 1;

[0077] The above code is a code for a simplified macro definition module configured in a YAML file. Using the module name "Definitions" as the target for script language recognition, here are simple examples of three macro definition configurations: test item (ENABLE_TEST), functional module compilation selection (ENABLE_FUNC), and code version (ENABLE_VERSION). That is, here only the cos operator is selected for compilation, the performance test (PROFILER) function is enabled, and the project version is selected as version 1. Among them, the test item and functional module can include one or more items.

[0078] According to the configuration items of the macro definition module and the corresponding configuration parameters, to perform the compilation of the target engineering project, it is necessary to first parse and generate a string based on the configuration items of the macro definition module and the configuration parameters corresponding to each configuration item, and then convert the string into a variable recognizable by the script. That is, in the project compilation script, before compiling the code related to the project, the parsing of the macro definition module is added. According to the designed parsing code, the above code will be parsed as:

[0079] - name: ENABLE_TEST value: cos is parsed into a string: "operators / src / cos.cpp";

[0080] - name: ENABLE_FUNC value: PROFILER is parsed as #define profiler;

[0081] - name: ENABLE_VERSION value: 1 is parsed into the string: "V1.0";

[0082] Then, these parses are converted into variables recognizable by the script language, so that the project can be compiled into the required version according to the configuration in the YAML.

[0083] By using the macro definition module, the compilation configuration can be quickly selected in the YAML file before compilation. There is no need to select whether to configure each functional module through statements during compilation, which can improve development efficiency and is also convenient for adding functions, management, and maintenance. When developers add / test a specific operator / function, they can skip other content that does not need to be compiled, improving development efficiency. Control the compilation version. When the project is large and complex, the compilation time of the project may be very long. Developers can control whether the code of certain functional modules needs to be compiled by selecting the compilation version. For example, for the version delivered to users, all test-related functional modules can be turned off; only the corresponding values in the YAML script need to be modified, without deleting the code of the corresponding functional modules in the project, improving development efficiency. In addition, developers can also select the code version and deliver content with higher accuracy or higher efficiency according to user needs.

[0084] In some embodiments, the dynamic loading module is used to control global variables during the operation of the target engineering project; the configuration items of the dynamic loading module include any one or more of cache-related, operator call, and log output; a configuration interface is generated based on the configuration file corresponding to the target configuration module, and the engineering configuration information sent by the operator is obtained through the configuration interface, and corresponding operations are performed according to the engineering configuration information, including: obtaining the configuration parameters for the configuration items of the dynamic loading module through the configuration interface; performing a running test on the target engineering project according to the configuration items of the dynamic loading module and the corresponding configuration parameters.

[0085] That is, the dynamic loading module is mainly used to control the parameter values of global variables during project operation and is used after the engineering project is compiled and during operation; the dynamic loading module is mainly for developers and testers and allows dynamic modification during operation to adjust program behavior without recompiling the project. Global variables are usually used to adjust system operation parameters, such as cache size, log printing, operator call, etc. This module can configure any runtime options. Specifically, the functions that can be achieved are, for example: cache-related parameter configuration, including whether to start the cache, cache memory usage ratio, cache block size, free memory allocation policy, event processing interval, etc.; test module, including log level, log printing classification, etc.; operator call, during testing, used to select whether to call or skip a certain operator or certain operators to test the required functions and improve the accuracy of error location.

[0086] Further, the configuration items of the dynamic loading module further include a configuration scheme identifier; a configuration interface is generated based on the configuration file corresponding to the target configuration module, and the project configuration information issued by the operator is obtained through the configuration interface, and corresponding operations are performed according to the project configuration information, including: selecting a target test configuration scheme from all preset test configuration schemes according to the configuration scheme identifier; performing a running test on the target engineering project according to the target test configuration scheme, the remaining configuration items of the dynamic loading module, and the corresponding configuration parameters. That is, several sets of parameters are preset for the testers, and the preset test schemes can be set by the developers in advance after communicating with the testers according to their needs.

[0087] A configuration file of a specific dynamic loading module is as follows:

[0088] DynamicConfigs:

[0089] - name: SET_CONFIG_SERIES;

[0090] value: 2;

[0091] - name: ENABLE_MEMORY_CACHING;

[0092] value: 1;

[0093] - name: CACHING_MEMORY_FRACTION;

[0094] value: 100;

[0095] - name: CACHING_PROCESS_EVENTS;

[0096] value: 1;

[0097] - name: OPERATOR_UNREGISTER;

[0098] value: add;

[0099] - name: LOG_LEVEL;

[0100] value: warning;

[0101] - name: ENABLE_OPERATOR_LOG;

[0102] value: 1;

[0103] Taking the module name "DynamicConfigs" as the target for script language recognition, simple examples of dynamic loading module configurations such as the configuration master control (SET_CONFIG_SERIES), cache-related (ENABLE_MEMORY_CACHING, CACHING_MEMORY_FRACTION, CACHING_PROCESS_EVENTS), operator call (OPERATOR_UNREGISTER), and log output-related (LOG_LEVEL, ENABLE_OPERATOR_LOG) are provided here. That is, the second set of preset solutions is selected here, with caching enabled, the cache memory usage ratio set to 100%, the event processing interval set to 1, the "add" operator not called, the log output level set to "warning", and operator-related log output enabled.

[0104] Among them, according to the target test configuration scheme, the remaining configuration items of the dynamic loading module, and the corresponding configuration parameters, a running test for the target engineering project is executed, including: according to the priority of the configuration items, a running test for the target engineering project is executed according to the target test configuration scheme, the remaining configuration items of the dynamic loading module, and the corresponding configuration parameters; the priority of the configuration items of the dynamic loading module is higher than the priority of the configuration items in the target test configuration scheme. That is, if a certain item in the target test configuration scheme conflicts with a certain configuration item of the dynamic loading module, the configuration item of the dynamic loading module shall prevail.

[0105] During project operation, first, the project scans the name and value in the current YAML file, and then according to the designed parsing code, the name and value are converted into variables recognizable by the script language. Subsequently, in the code that controls the corresponding module, the parsing of the variables is added. For example, if the value of SET_CONFIG_SERIES is set to 2, that is, the second set of test configurations is selected. Generally, setting this configuration alone can set a subsequent set of configuration files. If there are values in the subsequent value, the code will recognize it as the additional configuration parameter mode, and on the basis of the second set of test configurations, various individual configuration modifications will be completed. For example, if caching is preset to be disabled in the second set of test configurations and the value of ENABLE_MEMORY_CACHING is set to 1, when the code runs, the variable related to enabling caching in the script language will be set to true, and the caching function will be enabled during operation. That is, the project configuration at this time will become the second set of test configurations + the version with caching enabled.

[0106] By dynamically loading modules, various runtime configurations can be quickly modified in a YAML file during runtime without going through complex compilation and deployment processes. By simply adjusting the value, the configuration parameters of various functional modules can be dynamically adjusted, such as those related to caching, testing, log printing, etc. This can greatly improve development and testing efficiency and significantly reduce development costs and time. The module provides preset test scenarios with various preset parameter configurations. For novice testers, they can simply adjust this interface to conduct relevant tests, reducing the difficulty of getting started. For testers with rich engineering project experience, there are also individual interfaces for each function for them to modify and use. Although the dynamically loaded module and the macro definition module are similar at a macroscopic level, they are for different usage requirements. For example, for the testing function, the macro definition module is equivalent to a general control at a high level, that is, whether to compile the test module into the project; while in the dynamically loaded module, it is to control whether to call the test module and control its variable parameter values. Similarly, for the operator call function, the macro definition module controls whether certain operators are compiled into the project, and the dynamically loaded module controls whether to call the operator. The purpose of such handling is that the former is more oriented towards development efficiency and usage requirements, while the latter is mainly for testing efficiency.

[0107] In some embodiments, the environment variable module is used to configure the basic environment parameters for the operation of the target engineering project; the configuration items of the environment variable module include any one or more of hardware usage settings and path configurations. A configuration interface is generated based on the configuration file corresponding to the target configuration module. The engineering configuration information issued by the operator is obtained through the configuration interface, and corresponding operations are performed according to the engineering configuration information, including: obtaining the configuration parameters for the configuration items of the environment variable module through the configuration interface; and running the target engineering project according to the configuration items of the environment variable module and the corresponding configuration parameters.

[0108] That is, the environment variable module is mainly for end-users and is used to configure the basic environment parameters required for system operation. This module does not involve controlling the internal code logic of the engineering project, but provides a simple and easy-to-use way for users to perform external configurations for interaction with other projects and external systems. These configurations include hardware usage settings, path configurations, etc., to ensure consistency in different operating environments. Adjusting the environment variables usually does not affect the core logic and security of the project, but is to ensure the compatibility of the software on different platforms and hardware. Specifically, functions that can be achieved include: setting device visibility, such as setting to use a certain card in a multi-card environment; configuring key paths, setting certain key paths for multi-project alignment. For example, the configuration file of the environment variable module:

[0109] EnvironmentVariables:

[0110] - name: USE_CUDA;

[0111] value: 0;

[0112] - name: CUDA_VISIBLE_DEVICES;

[0113] value: 2,3,4,5;

[0114] - name: BACKEND_PATH;

[0115] value: / workspace / ……;

[0116] - name: LIB_PATH;

[0117] value: / home / lib / libimpl.so;

[0118] The environment variable settings in the YAML configuration file target the module name "EnvironmentVariables" for script language recognition, which include the visibility configurations related to the CUDA graphics card (Compute Unified Device Architecture) (USE_CUDA, CUDA_VISIBLE_DEVICES), as well as the key path configurations (BACKEND_PATH, LIB_PATH). That is, here it is chosen not to use CUDA, set the visible cards to the "2nd, 3rd, 4th, 5th" cards, and set the backend path and LIB path (dynamic link library path). At program startup, the environment variable module affects the behavior of the software through environment settings at the operating system level; users can adjust the corresponding environment variables by modifying the parameters in the YAML file; to make these changes take effect, users usually need to reload the environment configuration, for example, through scripts or terminal commands; this allows users to adjust the environment required during program runtime according to specific hardware configurations and requirements. Adjusting the program runtime environment through the environment variable module only requires editing the YAML configuration file without delving into the details of code implementation, allowing users to easily configure the interaction paths with external libraries and systems, enabling the software to seamlessly integrate with other system components; it will not affect the core logic and security of the project, ensuring the stability and security of the software. It provides a unified management for developers and testers, as well as improves the usability for users.

[0119] It can be seen that through the engineering configuration management of role customization, the needs of different roles in engineering projects are met. Through the independent management of different configuration categories, the system significantly improves flexibility and maintainability. At the same time, using the YAML configuration file as the configuration module parsing interface enhances the readability and maintainability of the configuration file and reduces the risk of configuration errors. It can generate exclusive configuration views according to different user roles, and improves management efficiency by providing customized views and permissions.

[0120] Furthermore, the above method further includes: obtaining a new engineering project; based on the configuration module of the existing engineering project, updating the configuration module of the existing engineering project according to the differences in configuration items between the new engineering project and the existing engineering project to obtain the configuration module of the new engineering project; where the update includes addition and / or deletion operations. That is, according to the configuration module of the existing engineering project, by adding new configuration items or deleting old configuration items, the configuration module of the new engineering project is generated, realizing the reuse of some content, improving the creation speed of the configuration module, and further improving the engineering configuration management ability for a large number of multi-type engineering projects.

[0121] It is understandable that in the related art, it usually relies on static configuration files and manual management methods. Common technical solutions for various file formats and tools (such as XML, JSON, etc.) include using formats such as XML and JSON to save configuration data. Although these formats can meet basic configuration requirements, when faced with large projects and multi-role collaboration, their maintainability and flexibility are insufficient. Especially as the project scale expands and the complexity increases, developers, testers, and end-users have different configuration requirements, and more advanced configuration management solutions are needed. Moreover, the configuration files in the related art are usually directly edited by developers and version-controlled through source code management tools. At the same time, some configuration management tools provide basic automated configuration management functions. These tools are usually positioned for infrastructure configuration management and focus on the deployment of servers and applications. However, these solutions often lack fine-grained control over application-layer configurations and multi-role support. Additionally, some platforms provide API interfaces to achieve dynamic configuration updates, but they are still not flexible enough when dealing with complex multi-role collaboration. The deficiencies of traditional configuration management technologies and the need to address diverse configuration requirements specifically have the following problems: Lack of flexibility: In the existing technology, when dealing with dynamically changing configuration requirements, manual intervention is usually required, and it is difficult to automatically adapt to the specific requirements of different roles; Poor maintainability: As the project scale expands, the complexity of the configuration files increases, and the maintainability of the existing solutions gradually decreases, easily leading to configuration bloat and management difficulties; Lack of security: Many tools lack fine-grained permission management and security mechanisms, making configuration changes may lead to system vulnerabilities and are easily affected by misoperations; Limited integration: The existing technical solutions are usually bound to specific development frameworks or platforms, with insufficient cross-platform compatibility, and it is difficult to achieve unified configuration management in heterogeneous environments; Lack of user customization: Developers, testers, and end-users have different requirements, and the existing technology often cannot provide customized configuration views and tools for different roles.

[0122] In view of the above problems, the present application solves the deficiencies of these traditional configuration management systems through a multi-role customized engineering configuration management based on a unified file format. The configuration parameters are described in YAML format, greatly improving the readability and maintainability of the configuration files; through modular design, the system realizes independent and flexible management of macro definitions, dynamic loading, and environment variables, and can effectively integrate the configurations of these three different modules, providing a consistent configuration view and the ability to use them in combination, reducing the risk of configuration conflicts; at the same time, it is easy to manage and maintain the configuration and make continuous improvements. By introducing a role-driven permission management mechanism, personalized configuration views and permission management can be provided according to user roles (such as developers, testers, end users), providing a flexible and easy-to-maintain way for developers, testers, and end users to obtain configuration options suitable for their specific needs; through fine-grained permission control, while improving the efficiency of team collaboration, it also ensures the security of engineering configuration management. By solving the above technical problems, an innovative and practical solution is provided in terms of improving the flexibility, security, and team collaboration efficiency of configuration management.

[0123] As can be seen from the above, in this embodiment, the identity type of the operator who obtains the current operation target engineering project is obtained; the identity type includes developers, testers, and users; according to the identity type, the module usage permissions of the operator are determined, and according to the module usage permissions, the target configuration module is screened out from all the configuration modules corresponding to the target engineering project; the configuration module is pre-constructed for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; a configuration interface is generated based on the configuration file corresponding to the target configuration module, and the engineering configuration information sent by the operator is obtained through the configuration interface, and corresponding operations are performed according to the engineering configuration information. It can be seen that the various configuration parameters are processed in modules, and a customized configuration interface is generated according to the permissions of the operator, enabling operators of different identity types to safely and effectively manage the configurations they need. Whether it is developers, testers, or users, customized configuration content can be provided for them to meet their specific usage scenarios. Different configuration models are constructed according to the configuration items involved in different stages of the engineering project, and corresponding module usage permissions are set for operators of different identities, so as to efficiently organize and manage complex configuration data and improve the software engineering configuration management ability.

[0124] Correspondingly, the embodiment of the present application also discloses a software engineering configuration management device, which includes:

[0125] An identity determination module, configured to obtain the identity type of the operator who obtains the current operation target engineering project; the identity type includes developers, testers, and users;

[0126] A target configuration module determination module, configured to determine the module usage permissions of the operator according to the identity type, and screen out the target configuration module from all the configuration modules corresponding to the target engineering project according to the module usage permissions; the configuration module is pre-constructed for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; the configuration module includes a macro definition module, a dynamic loading module, and an environment variable module.

[0127] An engineering configuration information acquisition module, configured to generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the engineering configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the engineering configuration information.

[0128] As can be seen from the above, in this embodiment, the identity type of the operator of the current operation target engineering project is obtained; the identity type includes developers, testers, and users; the module usage permissions of the operator are determined according to the identity type, and according to the module usage permissions, the target configuration module is screened out from all the configuration modules corresponding to the target engineering project; the configuration module is pre-constructed for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; a configuration interface is generated based on the configuration file corresponding to the target configuration module, the engineering configuration information issued by the operator is obtained through the configuration interface, and corresponding operations are performed according to the engineering configuration information. It can be seen that the various configuration parameters are processed in modules, and a customized configuration interface is generated according to the permissions of the operator, so that operators of different identity types can safely and effectively manage the configurations they need. Whether it is developers, testers, or users, customized configuration content can be provided for them to meet their specific usage scenarios. Different configuration models are constructed according to the configuration items involved in different stages of the engineering project, and corresponding module usage permissions are set for operators of different identities, so as to efficiently organize and manage complex configuration data and improve the software engineering configuration management ability.

[0129] In some specific embodiments, the construction process of the configuration module may specifically include:

[0130] Classify the configuration items involved in the target engineering project according to the preset configuration types to determine the configuration items corresponding to each configuration type; the configuration types include macro definition configuration, dynamic loading configuration, and environment variable configuration.

[0131] Generate the corresponding configuration module based on the configuration items corresponding to each configuration type.

[0132] In some specific embodiments, the macro definition module is used to control the compilation of the target engineering project.

[0133] The engineering configuration information acquisition module may specifically include:

[0134] A configuration parameter acquisition unit, configured to acquire configuration parameters for configuration items in the macro definition module through the configuration interface;

[0135] A compilation unit, configured to perform compilation on the target engineering project according to the configuration items and corresponding configuration parameters of the macro definition module.

[0136] In some specific embodiments, the dynamic loading module is used to control global variables during the operation of the target engineering project;

[0137] The engineering configuration information acquisition module may specifically include:

[0138] A configuration parameter acquisition unit, configured to acquire configuration parameters for configuration items of the dynamic loading module through the configuration interface;

[0139] An operation test unit, configured to perform an operation test on the target engineering project according to the configuration items and corresponding configuration parameters of the dynamic loading module.

[0140] In some specific embodiments, the configuration items of the dynamic loading module further include a configuration scheme identifier;

[0141] The operation test unit may specifically include:

[0142] A target test configuration scheme determination unit, configured to select a target test configuration scheme from all preset test configuration schemes according to the configuration scheme identifier;

[0143] An operation test unit, configured to perform an operation test on the target engineering project according to the target test configuration scheme, the remaining configuration items of the dynamic loading module, and the corresponding configuration parameters.

[0144] In some specific embodiments, the operation test unit may specifically be configured to perform an operation test on the target engineering project according to the target test configuration scheme, the remaining configuration items of the dynamic loading module, and the corresponding configuration parameters in accordance with the priority of the configuration items; the priority of the configuration items of the dynamic loading module is higher than the priority of the configuration items in the target test configuration scheme.

[0145] In some specific embodiments, the environment variable module is used to configure basic environment parameters for system operation;

[0146] The engineering configuration information acquisition module may specifically include:

[0147] A configuration parameter acquisition unit, configured to acquire configuration parameters of configuration items for the environment variable module through the configuration interface;

[0148] A target engineering project running unit, configured to run the target engineering project according to the configuration items of the environment variable module and the corresponding configuration parameters.

[0149] In some specific embodiments, the configuration items of the macro definition module include any one or more of items to be tested, enabling / disabling of function modules, compilation version, and code version;

[0150] The configuration items of the dynamic loading module include any one or more of cache-related, operator call, and log output;

[0151] The configuration items of the environment variable module include any one or more of hardware usage settings and path configuration.

[0152] In some specific embodiments, the software engineering configuration management device may specifically include:

[0153] An execution unit, configured to, after screening out a target configuration module from all the configuration modules corresponding to the target engineering project, acquire default configuration information corresponding to the target configuration module, and perform corresponding operations according to the default configuration information.

[0154] In some specific embodiments, the testers include internal testers and external testers;

[0155] The identity determination module may specifically include

[0156] A module usage permission determination unit, configured to determine the module usage permission of the operator according to preset permission information and the identity type; the preset permission information includes: developers and internal testers have the usage permission for the macro definition module, the dynamic loading module, and the environment variable module; external testers have the usage permission for the dynamic loading module and the environment variable module; users have the usage permission for the environment variable module.

[0157] In some specific embodiments, the target configuration module determination module may specifically include:

[0158] A target configuration module screening unit, configured to screen out a target configuration module from all the configuration modules corresponding to the target engineering project according to the module usage permission and the identifiers of the parsing interfaces corresponding to the respective configuration modules.

[0159] In some specific embodiments, the software engineering configuration management device may specifically include:

[0160] A configuration file generation unit for generating a configuration file corresponding to each of the configuration modules based on a target data management format; configuration items and configuration parameters of the configuration file are stored in the form of key-value pairs.

[0161] Further, an embodiment of the present application also discloses an electronic device. Refer to Figure 3 As shown, the content in the figure cannot be considered as any limitation to the scope of use of the present application.

[0162] Figure 3 FIG. 9 is a schematic structural diagram of an electronic device 20 provided by an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Among them, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the software engineering configuration management method disclosed in any of the foregoing embodiments.

[0163] In this embodiment, the power supply 23 is used to provide a working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows is any communication protocol applicable to the technical solution of the present application, and no specific limitation is imposed here; the input / output interface 25 is used to obtain external input data or output data to the outside, and its specific interface type can be selected according to specific application needs, and no specific limitation is made here.

[0164] In addition, as a carrier for resource storage, the memory 22 may be a read-only memory, a random access memory, a magnetic disk, or an optical disc, etc. The resources stored thereon include an operating system 221, a computer program 222, and data 223 including configuration modules, etc., and the storage method may be temporary storage or permanent storage.

[0165] Among them, the operating system 221 is used to manage and control each hardware device on the electronic device 20 and the computer program 222 to enable the processor 21 to perform operations and processing on a large amount of data 223 in the memory 22. It may be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program that can be used to complete the software engineering configuration management method executed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program that can be used to complete other specific tasks.

[0166] Further, the embodiments of the present application also disclose a computer storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are loaded and executed by a processor, the steps of the software engineering configuration management method disclosed in any of the foregoing embodiments are implemented.

[0167] The various embodiments in this specification are described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. For the same or similar parts among the various embodiments, reference can be made to each other. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and reference can be made to the description in the method part for the relevant parts.

[0168] The steps of the method or algorithm described in combination with the embodiments disclosed in this article can be directly implemented by hardware, software modules executed by a processor, or a combination of both. The software module can be placed in a random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.

[0169] Finally, it should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

[0170] The above has introduced in detail a software engineering configuration management method, device, medium and program product provided by the present invention. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

Claims

1. A software engineering configuration management method, characterized in that: include: Obtaining the identity type of the operator currently operating the target engineering project; the identity types include developer, tester, and user; Determine the module use authority of the operator according to the identity type, and select a target configuration module from all configuration modules corresponding to the target engineering project according to the module use authority; the configuration module is pre-built for the target engineering project according to the configuration types corresponding to the configuration items involved in different stages of the target engineering project; the configuration module includes a macro definition module, a dynamic loading module, and an environment variable module; Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the engineering configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the engineering configuration information; Wherein, generating a configuration interface based on a configuration file corresponding to the target configuration module, obtaining the engineering configuration information issued by the operator through the configuration interface, and performing corresponding operations according to the engineering configuration information, including: Acquire configuration parameters for the configuration items of the dynamic loading module; perform operation test for the target engineering project according to the configuration items of the dynamic loading module and the corresponding configuration parameters; Selecting a target test configuration scheme from all preset test configuration schemes; performing a running test on the target engineering project according to the target test configuration scheme and the remaining configuration items and corresponding configuration parameters of the dynamic loading module; According to the target test configuration scheme and the remaining configuration items and corresponding configuration parameters of the dynamic loading module, the operation test for the target engineering project is performed, including: According to the configuration item priority, based on the target test configuration scheme and the remaining configuration items and corresponding configuration parameters of the dynamic loading module, the operation test for the target engineering project is performed; the priority of the configuration item of the dynamic loading module is higher than the priority of the configuration item in the target test configuration scheme.

2. The software engineering configuration management method according to claim 1, characterized in that: The construction process of the configuration module includes: Classifying the configuration items involved in the target engineering project according to preset configuration types to determine the configuration items corresponding to each configuration type; the configuration types include macro definition configuration, dynamic loading configuration, and environment variable configuration; Based on the configuration items corresponding to each of the configuration types, the corresponding configuration modules are generated.

3. The software engineering configuration management method according to claim 1, characterized in that: The macro definition module is used to control the compilation of the target engineering project; Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the engineering configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the engineering configuration information, including: Obtaining configuration parameters for configuration items in the macro definition module through the configuration interface; Compilation for the target engineering project is performed according to the configuration items and corresponding configuration parameters of the macro definition module.

4. The software engineering configuration management method according to claim 1, characterized in that: The dynamic loading module is used to control the global variables when the target engineering project is running.

5. The software engineering configuration management method according to claim 4, characterized in that: The configuration items of the dynamic loading module also include a configuration scheme identifier; Select the target test configuration from all preset test configurations, including: A target test configuration scheme is selected from all preset test configuration schemes according to the configuration scheme identifier.

6. The software engineering configuration management method according to claim 1, characterized in that: The environment variable module is used to configure the basic environment parameters for system operation; Generate a configuration interface based on the configuration file corresponding to the target configuration module, obtain the engineering configuration information issued by the operator through the configuration interface, and perform corresponding operations according to the engineering configuration information, including: Obtaining configuration parameters for configuration items of the environment variable module through the configuration interface; The target engineering project is run according to the configuration items of the environment variable module and the corresponding configuration parameters.

7. The software engineering configuration management method according to claim 1, characterized in that: The configuration items of the macro definition module include any one or more of the items to be tested, enabling / disabling of functional modules, compiled versions, and code versions; The configuration items of the dynamic loading module include any one or more of cache related, operator call, and log output; The configuration items of the environment variable module include any one or more of hardware usage settings and path configuration.

8. The software engineering configuration management method according to claim 1, characterized in that: The testers include internal testers and external testers; Determining the module use authority of the operator according to the identity type includes: Determining the module use authority of the operator according to the preset authority information and the identity type; The preset permission information includes: developers and internal testers have the permission to use the macro definition module, dynamic loading module and environment variable module; external testers have the permission to use the dynamic loading module and environment variable module; users have the permission to use the environment variable module.

9. The software engineering configuration management method according to claim 1, characterized in that: After selecting the target configuration module from all configuration modules corresponding to the target engineering project, the method further includes: Obtain default configuration information corresponding to the target configuration module, and perform corresponding operations according to the default configuration information.

10. The software engineering configuration management method according to claim 1, characterized in that: According to the module usage permission, a target configuration module is screened out from all configuration modules corresponding to the target engineering project, including: According to the module use permission and the identifier of the parsing interface corresponding to each of the configuration modules, a target configuration module is screened out from all configuration modules corresponding to the target engineering project.

11. The software engineering configuration management method according to any one of claims 1 to 10, characterized in that: Before obtaining the identity type of the operator currently operating the target project, it also includes: A configuration file corresponding to each configuration module is generated based on a target data management format; configuration items and configuration parameters of the configuration file are stored in the form of key-value pairs.

12. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the software engineering configuration management method according to any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein when the computer programs are executed by a processor, the software engineering configuration management method as described in any one of claims 1 to 11 is implemented.

14. A computer program product, characterized in that It comprises a computer program, which, when executed by a processor, implements the software engineering configuration management method according to any one of claims 1 to 11.

Images