CN116088926A - Decision component version management method - Google Patents
Decision component version management method Download PDFInfo
- Publication number
- CN116088926A CN116088926A CN202310030062.6A CN202310030062A CN116088926A CN 116088926 A CN116088926 A CN 116088926A CN 202310030062 A CN202310030062 A CN 202310030062A CN 116088926 A CN116088926 A CN 116088926A
- Authority
- CN
- China
- Prior art keywords
- component
- decision
- version
- version information
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a decision component version management method, which comprises the following steps: acquiring first version information and component identification of a decision component, and determining an upgrade mode of the decision component based on a received strategy version upgrade instruction; upgrading the decision component according to the first version information of the decision component version and the component identifier based on the upgrading mode, and determining the second version information of the decision component based on an upgrading result; and carrying out association record on the first version information and the second version information of the decision-making component based on the component identification, and storing a record result to finish the version management of the decision-making component. The method and the system are convenient for the user terminal to check the version condition and the association relation of the decision-making component in time, are convenient for checking the change condition of the decision-making component in time, ensure effective management of version information of the decision-making component in the upgrading process, and are convenient for improving the upgrading efficiency of the decision-making component, reducing a large number of repeated components and reducing the development and modification cost.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a decision component version management method.
Background
At present, decision components of the existing decision engine are isolated, each component only belongs to one strategy, a large number of repeated components can be generated by version upgrading of the decision components, and when the same rule changes, all the components need to be modified and tested, and certain storage resources are wasted;
meanwhile, as the decision-making component is required to be continuously updated, different version information can be generated, the current running condition of the decision-making component can be effectively mastered by effectively managing the version of the decision-making component, and meanwhile, the updating requirement of the decision-making component can be conveniently mastered in time;
accordingly, the present invention provides a decision component version management method.
Disclosure of Invention
The invention provides a decision component version management method, which is used for upgrading a decision component in a corresponding upgrading mode according to a strategy version upgrading instruction, and recording second version information of the upgraded decision component and first version information before upgrading, so that a user terminal can check the version condition and association relation of the decision component in time, check the change condition of the decision component in time, effectively manage the version information of the decision component in the upgrading process, improve the upgrading efficiency of the decision component, reduce a large number of repeated components and reduce development and modification cost.
The invention provides a decision component version management method, which comprises the following steps:
step 1: acquiring first version information and component identification of a decision component, and determining an upgrade mode of the decision component based on a received strategy version upgrade instruction;
step 2: upgrading the decision component according to the first version information of the decision component and the component identifier based on the upgrading mode, and determining the second version information of the decision component based on an upgrading result;
step 3: and carrying out association record on the first version information and the second version information of the decision-making component based on the component identification, and storing a record result to finish the version management of the decision-making component.
Preferably, in step 1, a method for managing version of a decision component, acquiring first version information and component identifier of the decision component, includes:
acquiring an upgrading task of the decision component, and analyzing the upgrading task to obtain a target type of the decision component to be upgraded;
sending an access request to a preset server based on a target type, searching configuration files corresponding to decision-making components based on a search engine in the preset server when the preset server makes access permission feedback, and obtaining target configuration files corresponding to decision-making components to be upgraded based on search results;
Extracting configuration content of the target configuration file to obtain document content of the target configuration file, and analyzing the document content to obtain first version information and component identification of the decision component.
Preferably, in step 1, an upgrade mode of the decision component is determined based on the received policy version upgrade instruction, which includes:
acquiring a strategy version upgrading instruction sent by a user terminal, analyzing an upgrading request carried in the strategy version upgrading instruction, and determining a target requirement of the user terminal on an upgraded execution function of a decision component;
meanwhile, first version information of the decision-making component is acquired, and an initial execution function of the decision-making component is determined based on the first version information;
and determining target requirements of the upgraded execution function and a function difference of the initial execution function, and determining an upgrade mode of the decision component based on the function difference.
Preferably, a decision component version management method, the upgrade mode includes: newly built component, inheritance component and component inherited with change.
Preferably, a decision component version management method determines an upgrade mode of a decision component based on a functional difference, including:
Acquiring an upgrade mode corresponding to the decision-making component, acquiring a component identifier corresponding to the decision-making component, and determining a corresponding relation between the component identifier and the upgrade mode;
binding an upgrade mode of the decision-making component with the component identifier based on the corresponding relation, and generating a decision-making component upgrade mode record table based on a binding result;
extracting configuration parameters of a decision component upgrading mode record table, and determining a component name, a component identifier and a record format of an upgrading mode in the decision component upgrading mode record table based on the configuration parameters;
and recording and storing the component name, the component identification and the upgrade mode of the decision component in a decision component upgrade mode record table based on the record format.
Preferably, in step 2, the decision component is upgraded according to the first version information and the component identifier of the decision component based on the upgrade mode, and the second version information of the decision component is determined based on the upgrade result, which includes:
acquiring first version information and a component identifier of a decision component, determining a storage directory of a script file corresponding to the first version information of the decision component based on the component identifier, and extracting the script file of the decision component based on the storage directory;
Determining configuration information of source codes in a script file, determining association relations between the source codes based on the configuration information, analyzing the association relations between the source codes based on an upgrading target of a decision component, and determining parameter modification values and source code modification positions of the source codes;
and generating compiling configuration information based on the parameter modification value of the source code and the source code modification position, converting the script file into a compiling file based on the upgrading mode, recompiling the compiling file based on the compiling configuration information, and packaging the compiling file after compiling is finished to finish upgrading the decision component.
Preferably, a decision component version management method encapsulates a compiled file after compiling is finished, and completes upgrading of a decision component, including:
acquiring an upgraded decision component, and determining the dependency relationship between the upgraded decision component and other decision components based on the component identification of the decision component;
extracting the functional attribute of the updated decision-making component, and sending a data configuration request to the decision-making component to be configured, which has a dependency relationship with the updated decision-making component, based on the functional attribute;
setting parameter nodes for each decision component to be configured based on the data configuration request, determining target configuration parameters based on the updated decision components and function dependency attributes between the decision components to be configured, and issuing the target configuration parameters to the parameter nodes corresponding to the decision components to be configured to complete the adaptation of the decision components to be configured.
Preferably, a decision component version management method converts a script file into a compiled file based on an upgrade mode, and recompiles the compiled file based on compiling configuration information, including:
extracting attribute information of the upgrade mode, and determining a target type of the upgrade mode based on the attribute information;
when the target type is a newly built component, giving second version information to the newly built component based on a preset version setting rule;
when the target type is inheritance and the inheritance has change, determining the iteration times of the script file of the decision component, determining the change degree of the script file of the decision component based on the iteration times, and correcting the first version information of the decision component based on the change degree to obtain the second version information.
Preferably, in step 3, the method for managing the version of the decision component includes performing association recording on the first version information and the second version information of the decision component based on the component identifier, and saving the recording result to complete the version management of the decision component, including:
acquiring first version information and second version information of a decision component, and extracting vocabulary of the first version information and the second version information to obtain key fields in the first version information and the second version information;
Normalizing the key field to obtain a field feature vector corresponding to the key field, and determining whether the second version information has a target file inheriting the first version information or not based on the field feature vector;
when the target file exists, determining a blood-edge relation between the second version information and the first version information based on the target file, and drawing a blood-edge map between the first version information and the second version information based on the blood-edge relation;
otherwise, judging that the second version information and the first version information have no blood relationship, and independently recording and storing the second version information and the first version information.
Preferably, in step 3, the record result is saved to complete the version management of the decision component, which includes:
the method comprises the steps of obtaining a version viewing request submitted by a management terminal, analyzing the version viewing request and determining a target viewing component identifier;
matching the target view component identification with the stored component identifications of the components, determining a target decision component based on a matching result, and summarizing the target decision component and component versions with inheritance relation with the target decision component;
And transmitting the summarized results to the management terminal for display and viewing, and receiving an adjustment instruction of the management terminal to the component version in real time based on the viewing process and adjusting the component version based on the adjustment instruction, wherein the adjustment instruction comprises recovering the component version.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
FIG. 1 is a flowchart of a decision component version management method according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a decision component version management method according to step 1 of the present invention;
fig. 3 is a flowchart of step 2 in a decision component version management method according to an embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described below with reference to the accompanying drawings, it being understood that the preferred embodiments described herein are for illustration and explanation of the present invention only, and are not intended to limit the present invention.
Example 1:
the embodiment provides a decision component version management method, as shown in fig. 1, including:
step 1: acquiring first version information and component identification of a decision component, and determining an upgrade mode of the decision component based on a received strategy version upgrade instruction;
step 2: upgrading the decision component according to the first version information of the decision component and the component identifier based on the upgrading mode, and determining the second version information of the decision component based on an upgrading result;
step 3: and carrying out association record on the first version information and the second version information of the decision-making component based on the component identification, and storing a record result to finish the version management of the decision-making component.
In this embodiment, the decision components are part of a decision engine, each of which belongs to only one and decision strategy.
In this embodiment, the first version information refers to a version corresponding to the decision component before upgrading, and is used to characterize the current version level of the decision component.
In this embodiment, the component identifier is a marking symbol for marking different decision components, the component identifier corresponding to each decision component is unique, and the component identifier of the decision component remains unchanged during the process of upgrading the decision component.
In this embodiment, the policy version upgrade instruction is sent by the user terminal, and is used to upgrade the decision component.
In this embodiment, the upgrade mode refers to an upgrade method of the current decision component, and specifically includes creating a new component in the upgrade process of the decision component, and assigning a unique component identifier to the new component, inheriting refers to inheriting the content of the current decision component, and inheriting refers to modifying the decision component based on inheriting the decision component.
In this embodiment, the second version information refers to current version information of the decision component obtained after the decision component is upgraded;
when the newly built component and the component inherited with the change are modified, only a new version is added, and a new component is not created;
inherited components, when modified, not only add a new version, but also create a new component, but the component identity is unchanged.
In this embodiment, the upgrade mode includes: newly built component, inheritance component and component inherited with change.
In this embodiment, the recording of the first version information and the second version information of the decision-making component based on the component identifier refers to recording versions before and after upgrading the decision-making component according to the component identifier, so as to facilitate determining a version association relationship between decision-making components.
The beneficial effects of the technical scheme are as follows: by upgrading the decision-making component in a corresponding upgrading mode according to the strategy version upgrading instruction, and simultaneously recording the second version information of the upgraded decision-making component and the first version information before upgrading, the user terminal can check the version condition and the association relation of the decision-making component in time, and can check the change condition of the decision-making component in time, thereby guaranteeing the effective management of the version information of the decision-making component in the upgrading process, improving the upgrading efficiency of the decision-making component, reducing a large number of repeated components and reducing the development and modification cost.
Example 2:
on the basis of embodiment 1, this embodiment provides a decision component version management method, as shown in fig. 2, in step 1, obtaining first version information and component identification of a decision component includes:
Acquiring an upgrading task of the decision component, and analyzing the upgrading task to obtain a target type of the decision component to be upgraded;
sending an access request to a preset server based on a target type, searching configuration files corresponding to decision-making components based on a search engine in the preset server when the preset server makes access permission feedback, and obtaining target configuration files corresponding to decision-making components to be upgraded based on search results;
extracting configuration content of the target configuration file to obtain document content of the target configuration file, and analyzing the document content to obtain first version information and component identification of the decision component.
In this embodiment, the upgrade task refers to a standard that requires upgrade of the decision component, a component type that requires upgrade, and the like.
In this embodiment, the target type refers to a component type of a decision component to be upgraded, which is included in the upgrade task, and is at least one type of decision component.
In this embodiment, the preset server is set in advance, and is used to store configuration files corresponding to different decision components.
In this embodiment, the configuration file is a creation parameter corresponding to each decision component at the time of creation, including a specification, a corresponding version model, and the like.
In this embodiment, the target configuration file refers to a configuration file corresponding to a decision component of a target type stored in a preset server.
The beneficial effects of the technical scheme are as follows: the method has the advantages that the type of the decision-making component to be upgraded is accurately and effectively confirmed by analyzing the upgrading task, the configuration files of the decision-making components stored in the preset server are retrieved according to the type of the decision-making component to be upgraded, and finally, the first version information of the decision-making component and the component identification are accurately and effectively obtained through the retrieved configuration files, so that convenience and basis are provided for accurately managing the version information of the decision-making component.
Example 3:
on the basis of embodiment 1, the present embodiment provides a decision component version management method, in step 1, determining an upgrade mode for a decision component based on a received policy version upgrade instruction, including:
acquiring a strategy version upgrading instruction sent by a user terminal, analyzing an upgrading request carried in the strategy version upgrading instruction, and determining a target requirement of the user terminal on an upgraded execution function of a decision component;
meanwhile, first version information of the decision-making component is acquired, and an initial execution function of the decision-making component is determined based on the first version information;
And determining target requirements of the upgraded execution function and a function difference of the initial execution function, and determining an upgrade mode of the decision component based on the function difference.
In this embodiment, the upgrade request is set by the user terminal when generating the policy version upgrade instruction, and is used to send the upgrade request to the device terminal required for the decision component upgrade through the policy version upgrade instruction.
In this embodiment, the execution function refers to the kind of function that the decision component needs to implement after upgrading.
In this embodiment, the target requirement refers to the final target that needs to be achieved in the execution process of different execution functions or the execution standard that needs to be achieved by each function type.
In this embodiment, the initial execution function refers to the type of the function that the decision component can execute before upgrading and the execution effect of the corresponding function.
In this embodiment, the difference of functions refers to the difference of types of the executed functions that the decision component needs to implement after and before upgrading, and the difference of the execution effects of the corresponding functions.
The beneficial effects of the technical scheme are as follows: the upgrade request of the decision component is accurately and effectively acquired by analyzing the upgrade instruction of the strategy version, the upgrade request is analyzed, the type of functions required to be executed by the decision component after upgrading and the corresponding target requirements are determined according to the analysis result, finally, the type of functions required to be executed after upgrading and the requirements are compared with the type of functions and the requirements which can be executed before upgrading, so that the upgrade mode of the decision component is determined according to the comparison result, the accurate and effective grasp of the version information of the decision component after upgrading according to the upgrade mode is ensured, a large number of repeated components are conveniently reduced, and development and modification costs are reduced.
Example 4:
on the basis of embodiment 3, this embodiment provides a decision component version management method, which determines an upgrade mode for a decision component based on a functional difference, including:
acquiring an upgrade mode corresponding to the decision-making component, acquiring a component identifier corresponding to the decision-making component, and determining a corresponding relation between the component identifier and the upgrade mode;
binding an upgrade mode of the decision-making component with the component identifier based on the corresponding relation, and generating a decision-making component upgrade mode record table based on a binding result;
extracting configuration parameters of a decision component upgrading mode record table, and determining a component name, a component identifier and a record format of an upgrading mode in the decision component upgrading mode record table based on the configuration parameters;
and recording and storing the component name, the component identification and the upgrade mode of the decision component in a decision component upgrade mode record table based on the record format.
In this embodiment, the correspondence refers to a comparison between the component identifier and the upgrade mode of the same decision component, that is, the upgrade mode and the component identifier included in one decision component are determined.
In this embodiment, the decision component upgrade mode record table is used for recording upgrade modes and component identifiers corresponding to decision components, the upgraded decision components are not unique, and one decision component corresponds to one component identifier and upgrade mode, so that references are provided for the upgrade process of the decision components when the decision components are upgraded.
In this embodiment, the configuration parameters refer to the length and width of the record table of the upgrade mode of the decision component, the distribution condition of Bai Shanyuan cells in the table, the number of blank cells, the format requirement of the blank cells on the parameters to be recorded, and the like.
In this embodiment, the component name is a name that is suitable for distinguishing between different decision component types, and is set in advance.
The beneficial effects of the technical scheme are as follows: by determining the corresponding relation between the component identification of the decision component and the upgrading mode and generating a decision component upgrading mode record table according to the corresponding relation, the accurate and effective record of the upgrading modes of different decision components is realized, convenience and guarantee are provided for realizing effective management of version information of the decision components, and meanwhile upgrading efficiency of the decision components is also improved.
Example 5:
on the basis of embodiment 1, this embodiment provides a decision component version management method, as shown in fig. 3, in step 2, upgrade a decision component according to first version information and component identification of the decision component based on an upgrade mode, and determine second version information of the decision component based on an upgrade result, including:
Step 201: acquiring first version information and a component identifier of a decision component, determining a storage directory of a script file corresponding to the first version information of the decision component based on the component identifier, and extracting the script file of the decision component based on the storage directory;
step 202: determining configuration information of source codes in a script file, determining association relations between the source codes based on the configuration information, analyzing the association relations between the source codes based on an upgrading target of a decision component, and determining parameter modification values and source code modification positions of the source codes;
step 203: and generating compiling configuration information based on the parameter modification value of the source code and the source code modification position, converting the script file into a compiling file based on the upgrading mode, recompiling the compiling file based on the compiling configuration information, and packaging the compiling file after compiling is finished to finish upgrading the decision component.
In this embodiment, the script file refers to specific content corresponding to the first version information of the decision component, and may specifically be a specification of the decision component of the first version information, a parameter during working, and the like.
In this embodiment, the storage directory refers to a location where the script file corresponding to the first version information of the decision component is stored.
In this embodiment, the source code refers to code recorded in the script file regarding the decision component execution steps and execution contents.
In this embodiment, the configuration information of the source codes refers to specific value conditions, corresponding numbers, association relations among the source codes, and the like corresponding to the source codes.
In this embodiment, the upgrade target refers to decision functions that can be implemented after upgrading the decision component and criteria of each function in the execution process.
In this embodiment, the parameter modification value refers to a specific size of the source code value to be modified, the number of modified source code types, and the like.
In this embodiment, the source code modification location refers to the location of the source code that needs to be modified in the script file.
In this embodiment, compiling configuration information refers to converting a parameter modification value and a source code modification position of source code into a format capable of being compiled, so as to correspond to a script file corresponding to a decision file, thereby modifying the script file corresponding to the decision component.
In this embodiment, compiling the file refers to converting the script file from the package state to the editable mode, so as to facilitate editing the script file corresponding to the decision component, thereby achieving the purpose of upgrading.
In this embodiment, packaging the compiled file after compiling is finished refers to repackaging the script file corresponding to the decision component into an application program or an application package after modification, so that the component is conveniently and effectively upgraded.
The beneficial effects of the technical scheme are as follows: according to the method, the script file of the decision component is accurately and effectively called according to the first version information and the component identification of the decision component, the modification parameters of source codes in the script file and the modification positions of the source codes are accurately and reliably confirmed according to the upgrading target of the decision component, finally, the parameter modification values of the script file and the source codes and the modification positions of the source codes are converted into editable files, so that the decision component is upgraded, the version information of the decision component in the upgrading process is effectively managed, the upgrading efficiency of the decision component is conveniently improved, and convenience and guarantee are provided for effectively managing the version of the decision component.
Example 6:
on the basis of embodiment 5, this embodiment provides a decision component version management method, after compiling is finished, packaging a compiled file to complete upgrading of a decision component, including:
Acquiring an upgraded decision component, and determining the dependency relationship between the upgraded decision component and other decision components based on the component identification of the decision component;
extracting the functional attribute of the updated decision-making component, and sending a data configuration request to the decision-making component to be configured, which has a dependency relationship with the updated decision-making component, based on the functional attribute;
setting parameter nodes for each decision component to be configured based on the data configuration request, determining target configuration parameters based on the updated decision components and function dependency attributes between the decision components to be configured, and issuing the target configuration parameters to the parameter nodes corresponding to the decision components to be configured to complete the adaptation of the decision components to be configured.
In this embodiment, the dependency relationship refers to an association relationship that the updated decision component and other decision components have an inter-call in the process of executing the function.
In this embodiment, the functional attribute refers to requirements that the upgraded decision component needs to meet when executing the corresponding function, and limitations on parameter types and values when executing the function, and the like.
In this embodiment, the decision component with configuration refers to at least one other decision component having a dependency relationship with the updated decision component.
In this embodiment, the data configuration request refers to sending a data configuration message to other decision components, so as to modify the configuration of the other decision components synchronously, thereby facilitating ensuring the smoothness of the upgraded decision components when executing the corresponding functions, and improving the compatibility degree between the decision components.
In this embodiment, a parameter node refers to an intermediary for receiving configuration parameters in order to provide parameter support to other decision-making components.
In this embodiment, the function dependency attribute refers to a relationship that when the updated decision component and the decision component having the dependency relationship therebetween perform an operation, the functions are called or matched with each other.
In this embodiment, the target configuration parameter refers to a parameter type and a corresponding value condition that need to be configured for the decision component to be configured.
The beneficial effects of the technical scheme are as follows: the decision-making component to be configured with the dependency relationship with the updated decision-making component is determined, and the target configuration parameter of the decision-making component to be configured is determined according to the functional attribute of the updated decision-making component, so that the decision-making component to be configured is correspondingly configured according to the target configuration parameter, normal operation of the decision-making component after the updating is ensured, the updating effect of the decision-making component is ensured, and meanwhile, effective management of version information of the updated decision-making component is facilitated.
Example 7:
on the basis of embodiment 5, the present embodiment provides a decision component version management method, which converts a script file into a compiled file based on an upgrade mode, and recompiles the compiled file based on compiling configuration information, including:
extracting attribute information of the upgrade mode, and determining a target type of the upgrade mode based on the attribute information;
when the target type is a newly built component, giving second version information to the newly built component based on a preset version setting rule;
when the target type is inheritance and the inheritance has change, determining the iteration times of the script file of the decision component, determining the change degree of the script file of the decision component based on the iteration times, and correcting the first version information of the decision component based on the change degree to obtain the second version information.
In this embodiment, the attribute information refers to parameters capable of characterizing the kind of upgrade mode and the specific upgrade operation.
In this embodiment, the target category refers to a manner or method of upgrading the decision component, and is one or more of a new component, a Chen Jicheng component, and an inherited change component.
In this embodiment, the preset version setting rule is set in advance, and is used to set a version number for a newly built component, which may specifically be 1.0.0 or the like.
In this embodiment, the iteration number refers to the number of times that the script file corresponding to the decision component is repeatedly modified.
In this embodiment, the degree of change refers to the kind of functional difference between the decision component after the upgrade and the decision component before the upgrade and the difference in execution effect between the functions.
In this embodiment, the modification of the first version information of the decision component based on the degree of modification may specifically be that if the version before the upgrade is 1.0.0, the version becomes 1.0.1 when the degree of modification is first level, the version becomes 1.1.0 when the degree of modification is second level, and the version becomes 2.0.0 when the degree of modification is third level.
In this embodiment, when the upgrade mode is inherited, the inherited component changes, all decision components inheriting the component are notified, and the decision component can choose whether to continue inheriting or not inheriting to create a new component according to the change condition.
The beneficial effects of the technical scheme are as follows: by determining the upgrade mode of the decision component and realizing accurate and effective confirmation of the version information of the upgraded decision component according to the upgrade mode, the version information of the decision component is convenient to accurately and effectively manage in time, and the management effect is improved.
Example 8:
on the basis of embodiment 1, the present embodiment provides a decision component version management method, in step 3, performing association recording on first version information and second version information of a decision component based on component identification, and saving a recording result, thereby completing version management of the decision component, including:
acquiring first version information and second version information of a decision component, and extracting vocabulary of the first version information and the second version information to obtain key fields in the first version information and the second version information;
normalizing the key field to obtain a field feature vector corresponding to the key field, and determining whether the second version information has a target file inheriting the first version information or not based on the field feature vector;
when the target file exists, determining a blood-edge relation between the second version information and the first version information based on the target file, and drawing a blood-edge map between the first version information and the second version information based on the blood-edge relation;
otherwise, judging that the second version information and the first version information have no blood relationship, and independently recording and storing the second version information and the first version information.
In this embodiment, vocabulary extraction refers to extracting keywords in the first version information and the second version information.
In this embodiment, the key field refers to a data segment in the first version information and the second version information, where the data segment can indicate the version condition of the decision component.
In this embodiment, the field feature vector refers to a specific parameter corresponding to the key field, so that the association relationship between the key fields is determined according to the field feature vector.
In this embodiment, the target file refers to the same parameter file as that in the first version information existing in the second version information.
In this embodiment, the blood-margin relationship is adapted to characterize the inheritance relationship between the second version information and the first version information of the decision component, and if the inheritance relationship exists between the second version information and the first version information, the blood-margin relationship is determined to exist between the second version information and the first version information.
In the embodiment, the blood-related map is used for marking the component versions of the decision components with inheritance relations in a graphical form, so that different version information of the decision components can be effectively managed.
In this embodiment, independently recording and storing refers to storing versions corresponding to decision components correspondingly when there is no inheritance relationship between versions of decision components, so as to facilitate determining versions corresponding to different decision components.
The beneficial effects of the technical scheme are as follows: by analyzing the first version information and the second version information of the decision component, the inheritance relationship between the first version information and the second version information of the decision component is accurately and effectively judged, then, according to the judgment result of the inheritance relationship, the blood-margin relationship between the first version information and the second version information of the decision component is effectively confirmed, and according to the confirmed blood-margin relationship, the version information of the decision component is drawn, the version information of the decision component is effectively managed according to the blood-margin map, a large number of repeated components are reduced, and development and modification costs are reduced.
Example 9:
on the basis of embodiment 1, the present embodiment provides a decision component version management method, in step 3, the record result is saved, and version management of the decision component is completed, including:
the method comprises the steps of obtaining a version viewing request submitted by a management terminal, analyzing the version viewing request and determining a target viewing component identifier;
matching the target view component identification with the stored component identifications of the components, determining a target decision component based on a matching result, and summarizing the target decision component and component versions with inheritance relation with the target decision component;
And transmitting the summarized results to the management terminal for display and viewing, and receiving an adjustment instruction of the management terminal to the component version in real time based on the viewing process and adjusting the component version based on the adjustment instruction, wherein the adjustment instruction comprises recovering the component version.
In this embodiment, the version viewing request refers to a decision component version information viewing instruction sent by the management terminal to the storage device, so as to view version information corresponding to the decision component.
In this embodiment, the target viewing component identifier refers to a component identifier corresponding to a decision component that needs to be viewed.
In this embodiment, the target decision component refers to a queried decision component corresponding to a target look-up component identifier carried in the version viewing request.
The beneficial effects of the technical scheme are as follows: the method has the advantages that the version checking request sent by the management terminal is analyzed, so that decision components to be checked are locked quickly and accurately, meanwhile, component versions of the decision components to be checked are summarized effectively, the management terminal can check and manage correspondingly, adjustment instructions sent by the management terminal can be received in real time, the version information of the decision components is adjusted accurately and reliably, and the management effect of the version information of the decision components is guaranteed.
Example 10:
on the basis of embodiment 1, the present embodiment provides a decision component version management method, in step 2, upgrading a decision component according to first version information and component identification of the decision component based on an upgrade mode, including:
obtaining an upgrading result of the decision-making assembly, and determining the repetition number of the decision-making assembly after upgrading and the decision-making assembly before upgrading based on the upgrading result;
calculating the repetition rate of the updated decision component and the decision component before updating based on the repetition number, and calculating the accuracy of the repeated decision component deletion based on the repetition rate, wherein the specific steps comprise:
calculating the repetition rate of the updated decision component and the decision component before updating according to the following formula:
wherein, the liquid crystal display device comprises a liquid crystal display device,
the repetition rate of the decision component after upgrading and the decision component before upgrading is represented, and the value range is [0,1 ]]The method comprises the steps of carrying out a first treatment on the surface of the Epsilon represents an error factor and has a value range of (0.02, 0.05); alpha represents the total data contained in the script file corresponding to the updated decision component; beta represents the total data contained in the script file corresponding to the decision component before upgrading; m represents the repetition number of the decision component after upgrading and the decision component before upgrading; s represents the number of decision components before upgrading, and the value is larger than M;
The accuracy of the duplicate decision component deletion is calculated according to the following formula:
wherein ω represents the accuracy of deleting the overlapping data and the value range is [0,1 ]]The method comprises the steps of carrying out a first treatment on the surface of the τ represents the specific gravity of the repeated decision component to the total decision component; ζ represents the number of deletions in the repeated decision component; m represents the repetition number of the decision component after upgrading and the decision component before upgrading; gamma represents the number of decision components contained in the deleted number that do not repeat; λ represents the erasure rate when the decision-repetition component is deleted, and the value range is (0.01,0.03);
the repetition rate of the decision component after upgrading and the decision component before upgrading is represented, and the value range is [0,1 ]]；
Comparing the accuracy of deleting the calculated repeated decision component with a preset accuracy threshold;
if the calculated accuracy of deleting the repeated decision-making component is greater than or equal to a preset accuracy threshold, completing deleting operation of the repeated decision-making component;
otherwise, restoring the deleted decision-making component, and deleting the repeated decision-making component again until the calculated accuracy of deleting the repeated decision-making component is greater than or equal to a preset accuracy threshold.
In this embodiment, the repeated decision component refers to a decision component having the same version and content after the upgrade as before the upgrade.
In this embodiment, the preset accuracy threshold is set in advance, and is used to measure whether the deletion accuracy of the repeated decision component meets the expected requirement.
The beneficial effects of the technical scheme are as follows: by calculating the repetition rate of the updated decision-making component and the decision-making component before updating, the effective calculation of the accuracy of repeated component deletion is realized, so that the repeated decision-making component can be deleted in time after being updated, the management efficiency of version information of the decision-making component is improved, and meanwhile, the updating efficiency of the decision-making component is also improved.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (10)
1. A decision component version management method, comprising:
step 1: acquiring first version information and component identification of a decision component, and determining an upgrade mode of the decision component based on a received strategy version upgrade instruction;
Step 2: upgrading the decision component according to the first version information of the decision component and the component identifier based on the upgrading mode, and determining the second version information of the decision component based on an upgrading result;
step 3: and carrying out association record on the first version information and the second version information of the decision-making component based on the component identification, and storing a record result to finish the version management of the decision-making component.
2. The method for managing version of decision component according to claim 1, wherein in step 1, obtaining the first version information and the component identifier of the decision component comprises:
acquiring an upgrading task of the decision component, and analyzing the upgrading task to obtain a target type of the decision component to be upgraded;
sending an access request to a preset server based on a target type, searching configuration files corresponding to decision-making components based on a search engine in the preset server when the preset server makes access permission feedback, and obtaining target configuration files corresponding to decision-making components to be upgraded based on search results;
extracting configuration content of the target configuration file to obtain document content of the target configuration file, and analyzing the document content to obtain first version information and component identification of the decision component.
3. The decision component version management method according to claim 1, wherein in step 1, determining an upgrade mode for the decision component based on the received policy version upgrade instruction comprises:
acquiring a strategy version upgrading instruction sent by a user terminal, analyzing an upgrading request carried in the strategy version upgrading instruction, and determining a target requirement of the user terminal on an upgraded execution function of a decision component;
meanwhile, first version information of the decision-making component is acquired, and an initial execution function of the decision-making component is determined based on the first version information;
and determining target requirements of the upgraded execution function and a function difference of the initial execution function, and determining an upgrade mode of the decision component based on the function difference.
4. A method of decision component version management as recited in claim 3 wherein the upgrade mode comprises: newly built component, inheritance component and component inherited with change.
5. A decision component version management method in accordance with claim 3 wherein determining an upgrade mode for a decision component based on a functional difference comprises:
acquiring an upgrade mode corresponding to the decision-making component, acquiring a component identifier corresponding to the decision-making component, and determining a corresponding relation between the component identifier and the upgrade mode;
Binding an upgrade mode of the decision-making component with the component identifier based on the corresponding relation, and generating a decision-making component upgrade mode record table based on a binding result;
extracting configuration parameters of a decision component upgrading mode record table, and determining a component name, a component identifier and a record format of an upgrading mode in the decision component upgrading mode record table based on the configuration parameters;
and recording and storing the component name, the component identification and the upgrade mode of the decision component in a decision component upgrade mode record table based on the record format.
6. The decision component version management method according to claim 1, wherein in step 2, updating the decision component according to the first version information and the component identification of the decision component based on the update mode, and determining the second version information of the decision component based on the update result comprises:
acquiring first version information and a component identifier of a decision component, determining a storage directory of a script file corresponding to the first version information of the decision component based on the component identifier, and extracting the script file of the decision component based on the storage directory;
determining configuration information of source codes in a script file, determining association relations between the source codes based on the configuration information, analyzing the association relations between the source codes based on an upgrading target of a decision component, and determining parameter modification values and source code modification positions of the source codes;
And generating compiling configuration information based on the parameter modification value of the source code and the source code modification position, converting the script file into a compiling file based on the upgrading mode, recompiling the compiling file based on the compiling configuration information, and packaging the compiling file after compiling is finished to finish upgrading the decision component.
7. The decision component version management method of claim 6, wherein packaging the compiled file after compiling is completed to complete upgrading of the decision component, comprising:
acquiring an upgraded decision component, and determining the dependency relationship between the upgraded decision component and other decision components based on the component identification of the decision component;
extracting the functional attribute of the updated decision-making component, and sending a data configuration request to the decision-making component to be configured, which has a dependency relationship with the updated decision-making component, based on the functional attribute;
setting parameter nodes for each decision component to be configured based on the data configuration request, determining target configuration parameters based on the updated decision components and function dependency attributes between the decision components to be configured, and issuing the target configuration parameters to the parameter nodes corresponding to the decision components to be configured to complete the adaptation of the decision components to be configured.
8. The decision component version management method of claim 6, wherein converting the script file into the compiled file based on the upgrade mode and recompiling the compiled file based on the compilation configuration information comprises:
extracting attribute information of the upgrade mode, and determining a target type of the upgrade mode based on the attribute information;
when the target type is a newly built component, giving second version information to the newly built component based on a preset version setting rule;
when the target type is inheritance and the inheritance has change, determining the iteration times of the script file of the decision component, determining the change degree of the script file of the decision component based on the iteration times, and correcting the first version information of the decision component based on the change degree to obtain the second version information.
9. The method of claim 1, wherein in step 3, the first version information and the second version information of the decision component are recorded in association based on the component identifier, and the recording result is saved, so as to complete the version management of the decision component, and the method comprises:
acquiring first version information and second version information of a decision component, and extracting vocabulary of the first version information and the second version information to obtain key fields in the first version information and the second version information;
Normalizing the key field to obtain a field feature vector corresponding to the key field, and determining whether the second version information has a target file inheriting the first version information or not based on the field feature vector;
when the target file exists, determining a blood-edge relation between the second version information and the first version information based on the target file, and drawing a blood-edge map between the first version information and the second version information based on the blood-edge relation;
otherwise, judging that the second version information and the first version information have no blood relationship, and independently recording and storing the second version information and the first version information.
10. The method for version management of a decision-making component according to claim 1, wherein in step 3, the record result is saved, and the version management of the decision-making component is completed, including:
the method comprises the steps of obtaining a version viewing request submitted by a management terminal, analyzing the version viewing request and determining a target viewing component identifier;
matching the target view component identification with the stored component identifications of the components, determining a target decision component based on a matching result, and summarizing the target decision component and component versions with inheritance relation with the target decision component;
And transmitting the summarized results to the management terminal for display and viewing, and receiving an adjustment instruction of the management terminal to the component version in real time based on the viewing process and adjusting the component version based on the adjustment instruction, wherein the adjustment instruction comprises recovering the component version.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310030062.6A CN116088926B (en) | 2023-01-10 | 2023-01-10 | Decision component version management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310030062.6A CN116088926B (en) | 2023-01-10 | 2023-01-10 | Decision component version management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116088926A true CN116088926A (en) | 2023-05-09 |
| CN116088926B CN116088926B (en) | 2023-10-20 |
Family
ID=86200457
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310030062.6A Active CN116088926B (en) | 2023-01-10 | 2023-01-10 | Decision component version management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116088926B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117112011A (en) * | 2023-08-16 | 2023-11-24 | 北京冠群信息技术股份有限公司 | Version management method and device |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2252463A1 (en) * | 1997-11-05 | 1999-05-05 | Makoto Imachi | Version and configuration management method and apparatus and computer readable recording medium for recording therein version and configuration management program |
| CN102622241A (en) * | 2011-01-26 | 2012-08-01 | 腾讯科技（深圳）有限公司 | Software upgrading method and software upgrading device |
| CN103544030A (en) * | 2013-07-04 | 2014-01-29 | Tcl集团股份有限公司 | Software upgrading method, software upgrading system and intelligent terminal |
| WO2014086311A1 (en) * | 2012-12-06 | 2014-06-12 | Tencent Technology (Shenzhen) Company Limited | Method and system for software upgrade |
| WO2016011607A1 (en) * | 2014-07-23 | 2016-01-28 | 华为技术有限公司 | Terminal upgrade method and related device |
| EP2993582A1 (en) * | 2014-09-05 | 2016-03-09 | Xiaomi Inc. | Method, apparatus and device for upgrading an operating system of a terminal device |
| CN106155651A (en) * | 2015-03-31 | 2016-11-23 | 广州四三九九信息科技有限公司 | The method and system that the automation of application version is issued and updated |
| CN106325901A (en) * | 2015-06-24 | 2017-01-11 | 南宁富桂精密工业有限公司 | Software version management method and system |
| US20170351507A1 (en) * | 2016-06-04 | 2017-12-07 | Airwatch Llc | Silent upgrade of software with dependencies |
| CN107688462A (en) * | 2017-04-10 | 2018-02-13 | 平安科技（深圳）有限公司 | Method for upgrading software and front-end server |
| CN107844313A (en) * | 2017-11-24 | 2018-03-27 | 武汉斗鱼网络科技有限公司 | SDK version upgrading methods and device in a kind of Android |
| CN108572838A (en) * | 2018-07-02 | 2018-09-25 | 北京航天数据股份有限公司 | The upgrade method of industrial software, apparatus and system |
| CN110333894A (en) * | 2019-07-10 | 2019-10-15 | 中国民航信息网络股份有限公司 | Method for upgrading system and device |
| CN110377321A (en) * | 2019-07-22 | 2019-10-25 | 平安科技（深圳）有限公司 | Method, apparatus, terminal and the storage medium of application program updating |
| CN111666074A (en) * | 2019-03-05 | 2020-09-15 | 华为技术有限公司 | Method, related device and system for customizing web application |
| CN111736875A (en) * | 2020-06-28 | 2020-10-02 | 深圳前海微众银行股份有限公司 | Version updating monitoring method, device, equipment and computer storage medium |
| CN112764792A (en) * | 2021-01-27 | 2021-05-07 | 上海淇玥信息技术有限公司 | Associated server version application upgrading method and device and electronic equipment |
| CN113810446A (en) * | 2020-06-16 | 2021-12-17 | 上海赫千电子科技有限公司 | Safety upgrading management method for ECU of vehicle-mounted network |
| CN113901021A (en) * | 2021-08-23 | 2022-01-07 | 恒生电子股份有限公司 | Method and device for generating upgrading script for multi-version database and electronic equipment |
-
2023
- 2023-01-10 CN CN202310030062.6A patent/CN116088926B/en active Active
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2252463A1 (en) * | 1997-11-05 | 1999-05-05 | Makoto Imachi | Version and configuration management method and apparatus and computer readable recording medium for recording therein version and configuration management program |
| CN102622241A (en) * | 2011-01-26 | 2012-08-01 | 腾讯科技（深圳）有限公司 | Software upgrading method and software upgrading device |
| WO2014086311A1 (en) * | 2012-12-06 | 2014-06-12 | Tencent Technology (Shenzhen) Company Limited | Method and system for software upgrade |
| CN103544030A (en) * | 2013-07-04 | 2014-01-29 | Tcl集团股份有限公司 | Software upgrading method, software upgrading system and intelligent terminal |
| WO2016011607A1 (en) * | 2014-07-23 | 2016-01-28 | 华为技术有限公司 | Terminal upgrade method and related device |
| EP2993582A1 (en) * | 2014-09-05 | 2016-03-09 | Xiaomi Inc. | Method, apparatus and device for upgrading an operating system of a terminal device |
| CN106155651A (en) * | 2015-03-31 | 2016-11-23 | 广州四三九九信息科技有限公司 | The method and system that the automation of application version is issued and updated |
| CN106325901A (en) * | 2015-06-24 | 2017-01-11 | 南宁富桂精密工业有限公司 | Software version management method and system |
| US20170351507A1 (en) * | 2016-06-04 | 2017-12-07 | Airwatch Llc | Silent upgrade of software with dependencies |
| CN107688462A (en) * | 2017-04-10 | 2018-02-13 | 平安科技（深圳）有限公司 | Method for upgrading software and front-end server |
| CN107844313A (en) * | 2017-11-24 | 2018-03-27 | 武汉斗鱼网络科技有限公司 | SDK version upgrading methods and device in a kind of Android |
| CN108572838A (en) * | 2018-07-02 | 2018-09-25 | 北京航天数据股份有限公司 | The upgrade method of industrial software, apparatus and system |
| CN111666074A (en) * | 2019-03-05 | 2020-09-15 | 华为技术有限公司 | Method, related device and system for customizing web application |
| CN110333894A (en) * | 2019-07-10 | 2019-10-15 | 中国民航信息网络股份有限公司 | Method for upgrading system and device |
| CN110377321A (en) * | 2019-07-22 | 2019-10-25 | 平安科技（深圳）有限公司 | Method, apparatus, terminal and the storage medium of application program updating |
| CN113810446A (en) * | 2020-06-16 | 2021-12-17 | 上海赫千电子科技有限公司 | Safety upgrading management method for ECU of vehicle-mounted network |
| CN111736875A (en) * | 2020-06-28 | 2020-10-02 | 深圳前海微众银行股份有限公司 | Version updating monitoring method, device, equipment and computer storage medium |
| CN112764792A (en) * | 2021-01-27 | 2021-05-07 | 上海淇玥信息技术有限公司 | Associated server version application upgrading method and device and electronic equipment |
| CN113901021A (en) * | 2021-08-23 | 2022-01-07 | 恒生电子股份有限公司 | Method and device for generating upgrading script for multi-version database and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 何保国;朱国宾;: "基于版本管理的多用户并发编辑控制策略研究", 地理空间信息, no. 04 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117112011A (en) * | 2023-08-16 | 2023-11-24 | 北京冠群信息技术股份有限公司 | Version management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116088926B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6651240B1 (en) | Object-oriented software development support apparatus and development support method | |
| US20070106629A1 (en) | System and method for accessing data | |
| CN103164334B (en) | Detect the system and method for the breakaway poing in web application automatic test case | |
| CN112394942B (en) | Distributed software development compiling method and software development platform based on cloud computing | |
| CN107506219A (en) | A kind of general version upgrade method based on android system | |
| US7363578B2 (en) | Method and apparatus for mapping a data model to a user interface model | |
| CN116088926B (en) | Decision component version management method | |
| CN111158741B (en) | Method and device for monitoring dependency relationship change of service module on third party class library | |
| US20110016451A1 (en) | Method and system for generating test cases for a software application | |
| US20070073724A1 (en) | System and method for automatic or semi-automatic software integration | |
| CN108614702B (en) | Byte code optimization method and device | |
| CN109445807A (en) | Realize the method, apparatus and computer readable storage medium of application program update | |
| CN108595187A (en) | Method, device and the storage medium of Android installation kit integrated software development kit | |
| CN112558946A (en) | Method, device and equipment for generating code and computer readable storage medium | |
| CN109032631A (en) | Application program service packs acquisition methods, device, computer equipment and storage medium | |
| CN107368513B (en) | Method and device for updating client database | |
| Khatchadourian et al. | Pointcut rejuvenation: Recovering pointcut expressions in evolving aspect-oriented software | |
| CN111552466B (en) | Project file generation method, system, computer equipment and storage medium | |
| US20070266367A1 (en) | Relationship Management For Data Modeling In An Integrated Development Environment | |
| US6343292B1 (en) | System and method for providing text descriptions to electronic databases | |
| CN111460779A (en) | Activiti-based flow form data rendering and accessing method | |
| CN109254774A (en) | The management method and device of code in software development system | |
| CN115291887A (en) | Code generation method, device, equipment and storage medium | |
| US11102280B1 (en) | Infrastructure imports for an information technology platform | |
| CN113791809A (en) | Application exception handling method and device and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |