Entity relation data change management and control method and device

Abstract

The invention discloses a change management and control method and device for entity relation data, relates to the technical field of data processing, and mainly aims to realize change management and control on the entity relation data so as to reduce the probability that the entity relation data is abnormal due to change. According to the main technical scheme, a change management and control system is used for maintaining entity relationship data, and the entity relationship data is used for describing multiple entities and dependency relationships among the multiple entities; if it is monitored that any first entity in the multiple entities needs to be changed, determining a second entity having a dependency relationship with the first entity in the multiple entities; and if an abnormal entity caused by the change of the first entity exists in the second entity, preventing the change of the first entity.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method and device for controlling changes in entity relationship data. Background Art

[0002] Entity-relationship data is data formed by abstracting real or virtual things into entities and abstracting the relationships between things into associations between entities (such as dependency relationships, correspondence relationships, etc.). Entity-relationship data is widely used because it conforms to human thinking habits and is easy to understand and use.

[0003] At present, in the process of entity relationship data application, the entity relationship data is often updated by changing the entity configuration data or association relationship of the entity itself in the entity relationship data, so as to achieve the purpose of continuously improving and enriching the entity relationship data. However, the association relationship between entities in the entity relationship data is intricate, and the change of one entity may cause other entities to fail to implement corresponding business and other anomalies. Therefore, how to achieve change control of entity relationship data to reduce the probability of anomalies due to changes in entity relationship data has become a problem that needs to be solved urgently. Summary of the invention

[0004] The present application proposes a method and device for change control of entity relationship data, the main purpose of which is to achieve change control of entity relationship data to reduce the probability of abnormalities in entity relationship data due to changes.

[0005] In order to achieve the above objectives, this application mainly provides the following technical solutions:

[0006] In a first aspect, the present application provides a change management method for entity relationship data, which is applied to a change management system, wherein the change management system is used to maintain entity relationship data, and the entity relationship data is used to describe multiple entities and dependencies between the multiple entities. The change management method for entity relationship data includes: if it is monitored that any first entity among the multiple entities needs to be changed, determining a second entity among the multiple entities that has a dependency relationship with the first entity; if there is an entity among the second entities that is abnormal due to a change to the first entity, preventing the first entity from being changed.

[0007] In some embodiments of the present application, determining a second entity among the multiple entities that has a dependency relationship with the first entity includes: determining an entity among the multiple entities that has a dependency relationship with the first entity based on the dependency relationship between the multiple entities maintained; and / or, through a first preset model, determining an entity among the multiple entities that has a hidden dependency relationship with the first entity based on change description data that needs to be changed for the first entity, entity configuration data for describing the maintained entities included in the entity relationship data, and dependency data for describing the dependency relationship between the maintained entities, wherein the hidden dependency relationship is a dependency relationship that does not exist in the dependency relationships maintained by the change management and control system and is identified by the first preset model based on the change description data of the first entity that needs to be changed; and determining the determined entity as the second entity among the multiple entities that has a dependency relationship with the first entity.

[0008] In some embodiments of the present application, determining that there is an entity in the second entity that has an abnormality due to a change in the first entity includes: pushing change description data that needs to be changed in the first entity and the dependency relationship between the second entity and the first entity to a target change approval terminal; if an approval failure instruction is received from the target change approval terminal, or the approval success instruction is not received within a first time period, then determining that there is an entity in the second entity that has an abnormality due to a change in the first entity.

[0009] In some embodiments of the present application, the change management method for entity relationship data provided in this embodiment may also include: through a second preset model, based on the change description data that needs to be changed for the first entity, the dependency relationship between the second entity and the first entity, the entity configuration data for describing the maintained entity and the dependency data for describing the dependency relationship between the maintained entities included in the entity relationship data, obtaining a change suggestion for the first entity that needs to be changed, the change suggestion being used to indicate the probability that the change to the first entity will cause an abnormality in the second entity; pushing the change suggestion to the target change approval terminal so that the approver can approve whether the first entity can be changed through the target change approval terminal based on the received change description data, the dependency relationship between the second entity and the first entity, and the change suggestion.

[0010] In some embodiments of the present application, the entity relationship data maintained by the change management and control system has corresponding projects, and the projects have different project stages, and different project stages have different approval personnel. Then, the change management and control method for entity relationship data provided in this embodiment may also include: determining the current project stage of the project corresponding to the entity relationship data; and determining the change approval terminal of the approval personnel corresponding to the project stage as the target change approval terminal.

[0011] In some embodiments of the present application, determining whether there are entities in the second entity that are abnormal due to changes in the first entity includes: predicting the probability of each of the second entities being abnormal due to changes in the first entity through a third preset model based on change description data that needs to be changed in the first entity, the dependency relationship between the second entity and the first entity, entity configuration data for describing the maintained entities included in the entity relationship data, and dependency data for describing the dependency relationship between the maintained entities; if there is at least one second entity whose probability reaches a preset probability threshold, determining that there are entities in the second entity that are abnormal due to changes in the first entity; if there is no second entity whose probability reaches the preset probability threshold, determining that there are no entities in the second entity that are abnormal due to changes in the first entity.

[0012] In some embodiments of the present application, the entity relationship data change management method provided in this embodiment may also include: if the change management system is required to maintain the entity relationship data of a specified type of entity of a specified project, then obtaining project data related to the specified type of entity in the specified project; extracting entities and entity dependency relationships from the project data through a target extraction method; setting entity relationship data based on the extracted entities and the dependency relationships between entities, and maintaining the set entity relationship data.

[0013] In some embodiments of the present application, the entity relationship data change management method provided in this embodiment may also include: if it is determined that there is no entity in the second entity that is abnormal due to the change of the first entity, performing the required changes on the first entity.

[0014] In some embodiments of the present application, each entity maintained by the change management system has corresponding change permissions, and the change permissions are applicable to corresponding roles. Then, the change management method for entity relationship data provided in this embodiment may also include: determining the role of the user who initiates the change to the first entity; determining whether the role has the corresponding change permissions for the first entity; if so, executing the step of determining the second entity among the multiple entities that has a dependency relationship with the first entity; if not, issuing an unchangeable warning for the first entity.

[0015] In some embodiments of the present application, the entity relationship data maintained by the change management and control system has corresponding projects, and the entity relationship data is obtained based on the project data of the corresponding projects. Then, the change management and control method for entity relationship data provided in this embodiment may also include: detecting whether the project data of the project corresponding to the entity relationship data is updated; if so, extracting entity configuration data used to describe the entity and dependency data used to describe the dependency relationship between entities from the updated project data; comparing the extracted entity configuration data and dependency data with the entity relationship data maintained by the change management and control system; if the comparison shows that any entity in the entity relationship data has a target situation, it is monitored that the entity needs to be changed; wherein the target situation includes at least one of the following: the entity configuration data of the entity in the entity relationship data is different from the extracted entity configuration data, and the dependency data of the entity in the entity relationship data is different from the extracted dependency data.

[0016] In some embodiments of the present application, the change management method of entity relationship data provided in this embodiment may also include: extracting hidden dependencies of the project data through a fourth preset model; adding the extracted hidden dependencies between entities to the dependencies between entities extracted by the target extraction method.

[0017] In some embodiments of the present application, the entity relationship data change management method provided in this embodiment may also include: providing the set entity relationship data to a review terminal so that reviewers can review the entities in the entity relationship data and the dependencies between entities through the review terminal; if a review pass instruction is received from the review terminal, then executing the step of maintaining the entity relationship data; if a review fail instruction is received from the review terminal, or the review pass instruction is not received within a second time period, then requesting change description data for changing the entities in the entity relationship data from the review terminal.

[0018] In a second aspect, the present application provides a change control device for entity relationship data, which is applied to a change control system, wherein the change control system is used to maintain entity relationship data, wherein the entity relationship data is used to describe multiple entities and dependencies between the multiple entities, and the change control device for entity relationship data includes:

[0019] a determination module, configured to determine a second entity in the plurality of entities that has a dependency relationship with the first entity if it is monitored that any first entity in the plurality of entities needs to be changed;

[0020] The blocking module is used to block the change of the first entity if there is an entity in the second entity that becomes abnormal due to the change of the first entity.

[0021] In a third aspect, the present application provides a computer-readable storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the entity relationship data change management method described in the first aspect.

[0022] In a fourth aspect, the present application provides an electronic device, comprising: a memory for storing a program; and a processor, coupled to the memory, for running the program to execute the entity relationship data change management method described in the first aspect.

[0023] The change control method and device for entity relationship data provided by the present application, when it is monitored that any first entity among the multiple entities included in the entity relationship data needs to be changed, determines the second entity among the multiple entities that has a dependent relationship with the first entity. If there is an entity in the second entity that has an abnormality due to the change of the first entity, the change of the first entity is blocked. It can be seen that the scheme provided by the present application does not directly change the entity when it is monitored that any entity in the entity relationship data needs to be changed, but first determines the entity in the entity relationship data that has a dependent relationship with the entity, and then determines whether the change of the entity will cause the determined entity with a dependent relationship to be abnormal, and as long as it is determined that an abnormality will occur, the entity change is blocked. In this way, the change control of entity relationship data can be implemented, thereby reducing the probability of abnormalities in entity relationship data due to changes.

[0024] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] Figure 1 A flow chart showing a method for controlling changes in entity relationship data provided by an embodiment of the present application is shown;

[0027] Figure 2 A schematic diagram of the architecture of a change management system provided by an embodiment of the present application is shown;

[0028] Figure 3A schematic diagram of the structure of a device for controlling changes in entity relationship data provided by an embodiment of the present application is shown;

[0029] Figure 4 A schematic diagram of the structure of a device for controlling changes in entity relationship data provided by another embodiment of the present application is shown. DETAILED DESCRIPTION

[0030] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0031] Entity relationship data is used to describe entities and the dependencies between entities. Currently, entity relationship data is often updated by changing the entity configuration data or dependencies of the entities in the entity relationship data. However, there are complex dependencies between entities in entity relationship data, and changes to one entity may cause abnormalities in other entities in the entity relationship data.

[0032] After research, it was found that if any entity in the monitored entity relationship data needs to be changed, the entity is not changed directly, but the entity with a dependent relationship with the entity in the entity relationship data is first determined, and then it is determined whether the change of the entity will cause an abnormality in the determined entity with a dependent relationship. If it is determined that an abnormality will occur, the entity change is blocked, and if it is determined that no abnormality will occur, the entity change is allowed. In this way, the change control of entity relationship data can be realized, thereby reducing the probability of abnormalities in entity relationship data due to changes.

[0033] Based on the above findings, this embodiment proposes a technical solution for change management of entity relationship data, specifically: if it is monitored that any first entity among multiple entities included in the entity relationship data needs to be changed, a second entity among the multiple entities that has a dependent relationship with the first entity is determined; if there is an entity among the second entities that is abnormal due to the change of the first entity, the change of the first entity is prevented.

[0034] The technical solution for change control of entity relationship data provided in this embodiment can be applied to any entity relationship data to implement change control of entity relationship data. This embodiment does not limit the type of entity in entity relationship data. For example, the type of entity can include but is not limited to any of the following: interface, database table, configuration center, MQ queue, service, component, etc.

[0035] Based on the above-mentioned technical solution for change control of entity relationship data, this embodiment specifically provides a method and device for change control of entity relationship data. The method and device for change control of entity relationship data provided in this embodiment are specifically described below.

[0036] like Figure 1 As shown, an embodiment of the present application provides a change control method for entity relationship data. The change control method for entity relationship data provided by this embodiment is applied to a change control system for maintaining entity relationship data. The change control method for entity relationship data provided by this embodiment includes at least the following steps 101 to 102.

[0037] 101. If it is monitored that any first entity among the multiple entities included in the entity relationship data needs to be changed, determine a second entity among the multiple entities that has a dependency relationship with the first entity.

[0038] The change control method for entity relationship data provided in this embodiment is applied to a change control system to perform change control on entity relationship data maintained by the change control system. Entity relationship data is used to describe multiple entities and dependencies between multiple entities. Change control of entity relationship data is performed when it is monitored that there are entities that need to be changed among the multiple entities included in the entity relationship data. Therefore, the change control method for entity relationship data provided in this embodiment also needs to include a process for determining entities that need to be changed in the entity relationship data, so as to perform change control on the entities that need to be changed in a timely manner. The process of determining entities that need to be changed in the entity relationship data can be achieved by the following two methods.

[0039] One is that the entity relationship data maintained by the change management and control system has a corresponding project, and the entity relationship data is obtained based on the project data of the corresponding project. Considering that the project data is usually updated with the progress of the project, the entities and entity dependencies may also change after the project data is updated. Therefore, in order to enable the entity relationship data to be updated as the project data is updated and to achieve consistency between the entity relationship data and the project data, the change management and control method for entity relationship data provided in this embodiment may also include the following steps: detecting whether the project data of the project corresponding to the entity relationship data is updated; if so, extracting the entity configuration data used to describe the entity and the dependency data used to describe the dependency relationship between the entities from the updated project data; comparing the extracted entity configuration data and dependency data with the entity relationship data maintained by the change management and control system; if the comparison shows that any entity in the entity relationship data has the target situation, it is monitored that the entity needs to be changed.

[0040] If it is detected that the project data of the project corresponding to the entity relationship data is updated, it means that the entity described by the entity relationship data or the dependency relationship between entities may change. Therefore, in order to ensure consistency between the entity relationship data and the project data, it is necessary to use an extraction method to extract the updated project data for describing the entity configuration data and the dependency data for describing the dependency relationship between entities, and compare the extracted entity configuration data and dependency data with the entity relationship data maintained by the change management system.

[0041] If the comparison shows that any entity has a target situation, it means that the entity relationship data is inconsistent with the updated project data, so the monitored entity needs to be changed, and the entity that needs to be changed is the first entity. If the comparison shows that no entity has a target situation, it means that the entity relationship data is inconsistent with the updated project data, so the monitored entity relationship data does not contain an entity that needs to be updated. In some embodiments, the target situation may include but is not limited to at least one of the following: the entity configuration data of the entity in the entity relationship data is different from the extracted entity configuration data, and the dependency data of the entity in the entity relationship data is different from the extracted dependency data.

[0042] If it is detected that the project data of the project corresponding to the entity relationship data has not been updated, it means that the entity relationship data and the project data remain inconsistent, and there is no entity that needs to be updated in the entity relationship data.

[0043] It should be noted that the entity configuration data is used to describe the entity's own configuration, which is related to the type of the entity. Exemplarily, if the entity type is a basic entity, the entity configuration data may include but is not limited to the following data: self-incrementing ID, entity code (unique, but not self-incrementing ID), entity type (interface, database, etc.), entity description (maintenance logic, etc.), maintenance party secondary department, maintenance party person in charge, maintenance party email, maintenance party R&D personnel, service code, test mark, deletion mark, creation time, creator, update time, updater, version number, etc. If the entity type is an interface, the entity configuration data may include but is not limited to the following data: URL, request method, request sample and description, response sample and description, etc. If the entity type is a database table, the entity configuration data may include but is not limited to the following data: database type, database address, database name, related table information, operation permissions. If the entity type is a configuration center, the entity configuration data may include but is not limited to the following data: subject, configuration name, sample and description. If the entity type is Redis, the entity configuration data may include but is not limited to the following data: cache service address, KEY-Value sample and description. If the entity type is MQ, the entity configuration data may include but is not limited to the following data: message service address, message configuration, message sample and description. If the entity type is a basic relationship, the entity configuration data may include but is not limited to the following data: auto-increment ID, entity type, entity code (unique, but not auto-increment ID), dependent entity type, dependent entity code (unique, but not auto-increment ID), dependency description, test mark, delete mark, creation time, creator, update time, updater, version number. Dependency data is used to describe the dependency relationship between entities.

[0044] Another is that, in order to enable users to change entity relationship data at any time based on business needs, the entity relationship data change control method provided in this embodiment may also include the following entity relationship data acquisition process, which may specifically include the following steps: monitoring whether a change instruction is received, the change instruction is used to specify the entity to be changed, and if received, the entity specified by the change instruction is determined as the entity to be changed. This embodiment opens the change instruction issuance authority to users, so that users can flexibly specify the entity to be changed through the change instruction based on their own change needs.

[0045] The above two processes for determining entities that need to be changed in entity relationship data can be used separately or in combination, and this embodiment does not limit this. In order to more clearly describe the change control process, the entity that needs to be changed determined in the above two processes is defined as the first entity in this embodiment.

[0046] In this embodiment, when any first entity among multiple entities in the entity relationship data needs to be changed, a second entity among the multiple entities that has a dependency relationship with the first entity is determined to evaluate whether the change of the first entity affects the second entity. The method of determining the second entity among multiple entities in the entity relationship data that has a dependency relationship with the first entity may include the following two methods:

[0047] First, the specific process of determining the second entity that has a dependency relationship with the first entity among the multiple entities in the entity relationship data may include the following steps: searching for the dependency relationship between the multiple entities described in the entity relationship data, and determining the entity that has a dependency relationship with the first entity described in the entity relationship data as the second entity that has a dependency relationship with the first entity. In this way, the second entity that has a dependency relationship with the first entity can be quickly determined based on the description of the dependency relationship in the entity relationship data;

[0048] Second, the specific process of determining a second entity that has a dependency relationship with a first entity among multiple entities in entity relationship data may include the following steps: determining an entity that has a dependency relationship with the first entity among multiple entities based on the dependency relationship between the multiple entities maintained; and / or, through a first preset model, determining an entity that has a hidden dependency relationship with the first entity among multiple entities based on change description data that needs to be changed in the first entity, entity configuration data for describing the maintained entity included in the entity relationship data, and dependency data for describing the dependency relationship between the maintained entities, wherein the hidden dependency relationship is a dependency relationship that does not exist in the dependency relationship maintained by the change management and control system and is identified by the first preset model based on the change description data of the first entity that needs to be changed; and determining the determined entity as the second entity that has a dependency relationship with the first entity among the multiple entities.

[0049] Taking into account the complexity of the dependencies between entities, there may be hidden dependencies between some entities, and the hidden dependencies may not be recorded in the entity relationship data. The hidden dependencies cannot be discovered by querying the dependencies between entities in the entity relationship data. Hidden dependencies are usually exposed when entities change. Therefore, this embodiment uses a first preset model to determine the entities among multiple entities that have hidden dependencies with the first entity based on the change description data that needs to be changed for the first entity, the entity configuration data included in the entity relationship data for describing the maintained entities, and the dependency data for describing the dependencies between the maintained entities.

[0050] The first preset model is a model for identifying hidden dependencies between entities, which is obtained by pre-training with multiple sets of data, each set of training data includes change description data that the entity needs to change, entity configuration data for describing the entity and dependency data for describing the dependency between entities, and corresponding hidden dependencies between entities. In some embodiments, the change description data may include but is not limited to at least one of the following: description data for modifying the entity configuration data of the entity, description data for modifying the dependency between entities. Exemplarily, the change description data includes data for indicating that the "entity code" in the entity configuration data of entity 1 is changed from "001" to "003", and data for indicating the deletion of the dependency between entity 1 and entity 3. In some embodiments, the type of the first preset model can be flexibly selected based on business needs, and this embodiment does not limit this. Exemplarily, the type of the first preset model may include but is not limited to at least one of the following: a convolutional neural network model, a recurrent neural network model, etc.

[0051] After the entities in the entity relationship data that have hidden dependencies with the first entity are determined by the first preset model, these entities and the entities that have dependencies with the first entity determined based on the dependencies between the multiple entities maintained are aggregated into second entities that have dependencies with the first entity. In this way, the second entities that have dependencies with the first entity can be discovered as much as possible to ensure the correctness of change control.

[0052] The above two methods for determining the second entity that has a dependency relationship with the first entity among multiple entities in entity relationship data can be flexibly selected based on business needs, and this embodiment does not limit this. For example, if it can be determined that the first entity does not have a hidden dependency relationship, the first method is used, and if it cannot be determined that the first entity does not have a hidden dependency relationship, the second method is used.

[0053] 102. If there is an entity in the second entity that becomes abnormal due to the change of the first entity, the change of the first entity is prevented.

[0054] After determining the second entity that has a dependency relationship with the first entity, it is necessary to determine whether there is an entity in the second entity that has an abnormality due to the change of the first entity, so as to clarify whether the change of the first entity is executable. The method of determining whether there is an entity in the second entity that has an abnormality due to the change of the first entity can include at least the following two methods.

[0055] First, the specific process of determining whether there is an entity in the second entity that is abnormal due to the change of the first entity may include the following steps 102A to 102C:

[0056] 102A. Push the change description data of the first entity that needs to be changed and the dependency relationship between the second entity and the first entity to the target change approval terminal.

[0057] In some embodiments, the entity relationship data maintained by the change management and control system has corresponding projects, and the projects have different project stages. Different project stages have different change approval terminals. After receiving the change description data that needs to be changed for the first entity and the dependency relationship between the second entity and the first entity, the change approval terminal approves whether the first entity can be changed in combination with the project stage.

[0058] Based on this, the change control of entity relationship data provided by this embodiment may also include the following steps: determining the current project stage of the project corresponding to the entity relationship data; determining the change approval terminal corresponding to the project stage as the target change approval terminal. In this way, the target change approval terminal corresponding to the project stage can be targeted to intervene in the approval process of entity changes, so that the target change approval terminal can accurately and targetedly approve whether the entity can be changed in combination with the project stage.

[0059] The change approval terminal is deployed with an evaluation model corresponding to the corresponding project stage. The evaluation model is used to predict the probability that a change to the first entity will cause an abnormality in the second entity in combination with the project stage, and the probability is positively correlated with the possibility of an abnormality in the second entity. The evaluation model is trained in advance based on multiple groups of data from the corresponding project stage, and each group of data includes change description data that requires changes to entities in the project stage, dependencies between entities and entities with which they have dependencies, and the probability that changes to entities will cause anomalies in entities with which they have dependencies. The type of evaluation model can be flexibly selected based on business needs, and this embodiment does not limit this. Exemplarily, the type of evaluation model may include, but is not limited to, at least one of the following: a convolutional neural network model, a recurrent neural network model, and the like.

[0060] After receiving the change description data that needs to be changed for the first entity and the dependency relationship between the second entity and the first entity, the target change approval terminal obtains the corresponding probability of each second entity based on the evaluation model.

[0061] If the target change approval terminal determines that there is a second entity whose probability reaches the first probability threshold, it is determined that there is an entity in the second entity that is abnormal due to the change of the first entity, so the target change approval terminal feeds back an approval failure instruction.

[0062] If the target change approval terminal determines that there is no second entity with a probability reaching the second probability threshold, it is determined that there is no entity in the second entity that is abnormal due to the change of the first entity. Therefore, the target change approval terminal feeds back an approval instruction, wherein the second probability threshold is less than the second probability threshold.

[0063] If the target change approval terminal determines that there is no second entity with a probability reaching the first probability threshold, but there is a second entity with a probability reaching the second probability threshold and not reaching the first probability threshold, it means that the probability obtained based on the evaluation model cannot clearly determine whether this part of the second entity with a probability reaching the second probability threshold and not reaching the first probability threshold will cause an abnormality due to the change of the first entity. At this time, it is necessary to execute a disposal process for this part of the second entity with a probability reaching the second probability threshold and not reaching the first probability threshold.

[0064] The disposal process may specifically be to provide the change description data of the first entity that needs to be changed, and the dependency relationship between the second entity and the first entity whose probability reaches the second probability threshold but does not reach the first probability threshold, to the corresponding approval personnel of the project stage. In this way, the approval personnel of the project stage are allowed to intervene in the approval process of entity changes, so that the approver can accurately and specifically approve whether the first entity can be changed in combination with the project stage. If the approval personnel intervene and confirm that the second entity whose probability reaches the second probability threshold but does not reach the first probability threshold will not be abnormal due to the change of the first entity, or that the abnormality caused by the second entity is acceptable, the approval personnel triggers the target change approval terminal to feedback the approval pass instruction. If the approval personnel intervene and confirm that the second entity whose probability reaches the second probability threshold but does not reach the first probability threshold will be abnormal due to the change of the first entity, and that the abnormality caused by the second entity is unacceptable, the approval personnel triggers the target change approval terminal to feedback the approval failure instruction.

[0065] 102B. If an approval instruction is received from the target change approval terminal, it is determined that there is no abnormal entity in the second entity due to the change of the first entity.

[0066] If an approval instruction is received from the target change approval terminal, it means that the target change approval terminal has evaluated that the change of the first entity will not cause an abnormality in the second entity, or that the abnormality caused by the second entity is acceptable. At this time, it is determined that there is no entity in the second entity that has an abnormality due to the change of the first entity.

[0067] 102C. If an approval failure instruction fed back by the target change approval terminal is received, or an approval failure instruction is not received within the first period of time, it is determined that an abnormal entity exists in the second entity due to the change of the first entity.

[0068] If an approval failure instruction is received from the target change approval terminal, or no approval success instruction is received within the first time period, it means that the target change approval terminal has assessed that the change of the first entity will cause an abnormality in the second entity, and the abnormality caused in the second entity is unacceptable. At this time, it is determined that there is an entity in the second entity that has an abnormality due to the change of the first entity.

[0069] Through steps 102A to 102C, the change approval terminal that is strongly related to the project stage can accurately and specifically approve whether the entity can be changed in combination with the project stage, so as to reduce the possibility of erroneous approval results. In addition, when the change approval terminal cannot clearly determine whether the second entity will be abnormal due to the change of the first entity, the approval personnel can be manually intervened to accurately approve the change based on the approval personnel's experience.

[0070] In some embodiments, in order to facilitate the approval of the approval personnel, change suggestions can also be provided to the approval personnel to reduce the approval difficulty of the approval personnel. Therefore, the change management of the entity relationship data provided in this embodiment can also include the following steps: through a second preset model, based on the change description data that needs to be changed for the first entity, the dependency relationship between the second entity and the first entity, the entity configuration data included in the entity relationship data for describing the maintained entity and the dependency data for describing the dependency relationship between the maintained entities, a change suggestion for the change that needs to be changed for the first entity is obtained, and the change suggestion is used to indicate the probability that the change of the first entity will cause an abnormality in the second entity; the change suggestion is pushed to the target change approval terminal, so that the approval personnel can approve whether the first entity can be changed through the target change approval terminal based on the received change description data, the dependency relationship between the second entity and the first entity, and the change suggestion.

[0071] The second preset model is a model for predicting the probability that a change to the first entity will cause an abnormality in the second entity. The model is trained in advance based on multiple groups of data, each group of data including change description data for the entity that needs to be changed, the dependency relationship between the entity and the entity with which it has a dependent relationship, entity relationship data including entity configuration data for describing the entity and dependency data for describing the dependency relationship between entities, and the probability that a change to an entity will cause an abnormality in the entity with which it has a dependent relationship.

[0072] In some embodiments, the content included in each group of data can be set based on business needs, and this embodiment does not limit this. The following is an example of a group of data, which may include: change description data indicating that the "entity code" in the entity configuration data of entity 1 is changed from "001" to "003", the dependency relationship between entity 1 and entity 2, the entity configuration data "entity code 001" used to describe entity 1, the dependency data used to describe the dependency relationship between entity configuration data 1 in entity 2 and entity code "001" of entity 1, and the probability "probability 1" that entity 2 will be abnormal when entity 1 is changed and the "entity code" is changed from "001" to "003". The probability of abnormality in entity 2 is specifically indicated.

[0073] In some embodiments, the type of the second preset model can be flexibly selected based on business needs, which is not limited in this embodiment. Exemplarily, the type of the second preset model can include but is not limited to at least one of the following: a convolutional neural network model, a recurrent neural network model, etc.

[0074] The probability that a change to the first entity will cause an abnormality in the second entity is pushed to the target change approval terminal, so that the approval personnel corresponding to the target change approval terminal can comprehensively evaluate whether the first entity can be changed based on the change description data that needs to be changed to the first entity, the dependency relationship between the second entity and the first entity, and the probability that a change to the first entity will cause an abnormality in the second entity.

[0075] The second method is to determine whether there is an entity in the second entity that has an abnormality due to a change in the first entity, including: using a third preset model, based on change description data that needs to be changed in the first entity, the dependency relationship between the second entity and the first entity, and the entity relationship data including entity configuration data for describing the maintained entities and dependency data for describing the dependency relationship between the maintained entities, predict the probability that the change to the first entity will cause an abnormality in each second entity; if there is at least one second entity with a probability reaching a preset probability threshold, it is determined that there is an entity in the second entity that has an abnormality due to a change in the first entity; if there is no second entity with a probability reaching the preset probability threshold, it is determined that there is no entity in the second entity that has an abnormality due to a change in the first entity.

[0076] In some embodiments, in order to improve the efficiency of change management and control and reduce manual intervention, a third preset model is used to predict the probability that a change to the first entity will cause an abnormality in each second entity, and whether the first entity can be changed is evaluated based on the probability.

[0077] The third preset model is a model for predicting the probability that a change in the first entity will cause an abnormality in the second entity. It is trained in advance based on multiple groups of data, each group of data includes change description data for the entity that needs to be changed, the dependency relationship between the entity and the entity with which it has a dependency relationship, entity relationship data including entity configuration data for describing the entity and dependency data for describing the dependency relationship between entities, and the probability that a change in the entity will cause an abnormality in the entity with which it has a dependency relationship. The type of the third preset model can be flexibly selected based on business needs, and this embodiment does not limit this. Exemplarily, the type of the third preset model may include, but is not limited to, at least one of the following: a convolutional neural network model, a recurrent neural network model, and the like.

[0078] If there is at least one second entity whose probability reaches the preset probability threshold, it means that the change of the first entity will cause the second entity whose probability reaches the preset probability threshold to become abnormal, so it is determined that there is an entity in the second entity that becomes abnormal due to the change of the first entity.

[0079] If there is no second entity whose probability reaches the preset probability threshold, it means that the change of the first entity will not cause any second entity to be abnormal, and it is determined that there is no second entity that is abnormal due to the change of the first entity.

[0080] The above two methods for determining whether there is an entity in the second entity that is abnormal due to a change in the first entity can be flexibly selected based on business needs, and this embodiment does not limit this.

[0081] Regardless of the above methods, if it is determined that there is an entity in the second entity that is abnormal due to the change of the first entity, it means that the change of the first entity is unacceptable, so the change of the first entity is blocked. If it is determined that there is no entity in the second entity that is abnormal due to the change of the first entity, it means that the change of the first entity is acceptable, so the required change is performed on the first entity.

[0082] If it is determined that there is an entity in the second entity that is abnormal due to the change of the first entity, it is explained that the change of the first entity is unacceptable, so the change of the first entity is blocked. In some embodiments, in order to make the user who initiates the change aware of the fact that the first entity cannot be changed, an unchangeable prompt is issued for the first entity.

[0083] When it is determined that there is no entity in the second entity that is abnormal due to the change of the first entity, it means that the change of the first entity is acceptable, so the required change is performed on the first entity.

[0084] The process of executing the required change on the first entity is related to the change description data of the change that needs to occur to the first entity. The change description data may include, but is not limited to, at least one of the following: description data for modifying the entity configuration data of the entity, description data for modifying the dependency relationship between entities. In the case where the change description data includes description data for modifying the entity configuration data of the entity, the entity configuration data of the first entity is modified based on the change description data. In the case where the change description data includes description data for modifying the dependency relationship between entities, the dependency relationship related to the first entity is modified based on the change description data. The modification of the dependency relationship may include any of the following: adding a new dependency relationship, modifying an existing dependency relationship, and modifying an existing dependency relationship to another dependency relationship, for example, changing the dependency relationship with entity 1 to the dependency relationship with entity 2.

[0085] It should be noted that after the required changes are performed on the first entity and the changes are completed, a change completion prompt may be issued to make it clear that the changes to the first entity have been completed.

[0086] The change control method of entity relationship data provided in the embodiment of the present application, when it is monitored that any first entity among the multiple entities included in the entity relationship data needs to be changed, determines the second entity among the multiple entities that has a dependency relationship with the first entity. If it is determined that there is an entity in the second entity that has an abnormality due to the change of the first entity, the change of the first entity is prevented. It can be seen that the scheme provided in the embodiment of the present application does not directly change the entity when it is monitored that any entity in the entity relationship data needs to be changed, but first determines the entity in the entity relationship data that has a dependency relationship with the entity, and then determines whether the change of the entity will cause the determined entity with a dependency relationship to be abnormal, and as long as it is determined that an abnormality will occur, the entity change is prevented. In this way, the change control of entity relationship data can be achieved, thereby reducing the probability of abnormalities in entity relationship data due to changes.

[0087] In some embodiments of the present application, each entity maintained by the change control system has corresponding change permissions, and the change permissions apply to corresponding roles. In order to more finely control the change of entity relationship data, this embodiment needs to combine change permissions to control the change of entity relationship data to reduce the possibility of illegal changes in entity relationship data. Based on this, the change control method for entity relationship data provided by this embodiment can also include the following steps: determining the role of the user who initiates the change of the first entity; determining whether the role has the corresponding change permission for the first entity; if so, executing the step of determining the second entity in multiple entities that has a dependency relationship with the first entity in step 101; if not, issuing an unchangeable warning for the first entity.

[0088] If it is determined that the role corresponding to the user has the corresponding modification authority for the first entity, it means that the first entity can be modified by the user, and thus the above step 101 of determining a second entity among multiple entities that has a dependency relationship with the first entity is executed.

[0089] If it is determined that the role corresponding to the user does not have the corresponding change authority for the first entity, it means that the user has no right to change the first entity, so an unchangeable warning is issued for the first entity to prompt that an illegal change has been initiated to the first entity.

[0090] In some embodiments of the present application, a change management system is used to maintain entity relationship data. In order to enable the change management system to obtain the entity relationship data that needs to be maintained, the change management method for entity relationship data provided in this embodiment may also include a process for obtaining entity relationship data, and the process may have the following two implementation methods.

[0091] First, for entities such as enterprises, a large number of projects will be launched internally, and each project will involve different types of entities. Therefore, in order to manage and use entities and dependencies between entities, entity relationship data can be set based on projects and types for maintenance. Therefore, the entity relationship data change control method provided in this embodiment can also include the following process of obtaining entity relationship data, which can include the following steps 1A to 1C:

[0092] 1A. If the entity relationship data of a specified type of entity of a specified project needs to be maintained by the change control system, the project data related to the specified type of entity in the specified project is obtained.

[0093] When the change control system needs to maintain the entity relationship data of a specified type for a specified project, an instruction carrying the specified project and the specified type can be sent to the change control system. When receiving the instruction, the change control system can determine that the entity relationship data of the specified type of entity of the specified project needs to be maintained, and obtain the project data related to the specified type of entity in the specified project, so as to set the entity relationship data based on the project data.

[0094] In this embodiment, both the designated project and the designated type can be flexibly selected based on business needs, and this embodiment does not limit this. For example, the designated project can include but is not limited to a software development project, and the designated type can include but is not limited to any of the following: an interface, a database table, a configuration center, an MQ queue, a service, a component, etc.

[0095] 1B. Extract entities and entity dependencies from project data through target extraction methods.

[0096] The target extraction method is a method for extracting entities and dependencies between entities from project data. You can select a target extraction method corresponding to the project type and entity type to extract entities and entity dependencies from project data to improve the accuracy of extracting entities and entity dependencies.

[0097] The target extraction method can be flexibly selected based on business needs. Exemplarily, the target extraction method may include but is not limited to any of the following: one is an extraction method that relies on an expert system or language rules preset by developers to identify entities in project data and dependencies between entities. These rules may include specific vocabulary, grammatical structures, and even specific punctuation marks in sentences; the other is a model for identifying entities and dependencies between entities obtained by training with manually annotated data sets.

[0098] 1C. Based on the extracted entities and the dependencies between entities, entity relationship data is set and the set entity relationship data is maintained.

[0099] In some embodiments, considering that if the target extraction method is not properly selected, some entities may be missed or the dependencies between entities cannot be extracted from the project data, the entity relationship data change control method provided by this implementation may also include the following steps: extracting hidden dependencies from the project data through the fourth preset model; adding the extracted hidden dependencies between entities to the dependencies between entities extracted by the target extraction method. The fourth preset model is a model for extracting hidden dependencies that are not easily extracted by the target extraction method, which is obtained by training multiple sets of data, each set of data including project data and hidden dependencies between entities corresponding to the project data.

[0100] The fourth preset model is essentially a supplementary extraction of the hidden dependencies of the target extraction method. Therefore, the corresponding fourth preset model can be preset for different extraction methods. After determining the target extraction method, the fourth preset model corresponding to the target extraction method is used to extract the hidden dependencies of the project data, so as to effectively supplement the extraction results of the target extraction method in a targeted manner.

[0101] After the hidden dependencies between entities are extracted through the fourth preset model, the hidden dependencies between entities are added to the dependencies between entities extracted through the target extraction method. It should be noted that when adding, in order to avoid duplication of dependencies, dependency deduplication processing is required. The specific process of this deduplication processing is to perform the following steps for each hidden dependency between entities extracted by the fourth preset model: detect whether the hidden dependency between the extracted entities already exists in the dependency between entities extracted by the target extraction method. If so, remove the hidden dependency between the extracted entities. If not, add the hidden dependency between the extracted entities to the dependency between entities extracted by the target extraction method to improve the dependency. In some embodiments, exemplarily, the dependency relationship between entities extracted by the fourth preset model includes the dependency relationship between entity 1 and entity 4. After detection, it is found that the dependency relationship between entity 1 and entity 4 already exists in the dependency relationship between entities extracted by the target extraction scheme. At this time, in order to avoid duplication, the dependency relationship between entity 1 and entity 4 extracted by the fourth preset model is eliminated so as not to summarize the dependency relationship between entity 1 and entity 4 extracted by the fourth preset model into the dependency relationship between entities extracted by the target extraction scheme. The dependency relationship between entities extracted by the fourth preset model includes the dependency relationship between entity 1 and entity 5. After detection, it is found that the dependency relationship between entity 1 and entity 5 does not exist in the dependency relationship between entities extracted by the target extraction scheme. At this time, the dependency relationship between entity 1 and entity 5 extracted by the fourth preset model is added to the dependency relationship between entities extracted by the target extraction method to improve the dependency relationship.

[0102] After adding the hidden dependencies between the extracted entities to the dependencies between the entities extracted by the target extraction method, the dependencies between the entities extracted from the project data are enriched and improved. At this point, the subsequent steps of setting entity relationship data can be performed based on the improved dependencies between the entities.

[0103] In some embodiments, after the entity relationship data is set, the change control system can maintain the entity relationship data. However, in some embodiments, in order to further ensure the correctness of the entity relationship data maintained by the change control system, the entity relationship data change control method provided in this embodiment may also include a review step for the entity relationship data, so that the change control system maintains the entity relationship data only after the set entity relationship data passes the review, thereby ensuring that the entity relationship data maintained by the change control system are all highly correct data.

[0104] In this embodiment, the review step of the entity relationship data may include: providing the set entity relationship data to the review terminal so that the reviewer can review the entities in the entity relationship data and the dependencies between the entities through the review terminal. If a review pass instruction is received from the review terminal, the step of maintaining the entity relationship data is performed. If a review failure instruction is received from the review terminal, or a review pass instruction is not received within the second time period, the review terminal is requested for change description data for changing the entities in the entity relationship data.

[0105] The entity relationship data set based on the entities extracted from the project data and the dependencies between the entities may contain errors or fail to meet business requirements. Therefore, before maintaining the set entity relationship data, the set entity relationship data is provided to the review terminal so that reviewers can review the entities and the dependencies between the entities in the entity relationship data through the review terminal. Reviewers are personnel with rich business experience and who are able to review the entities and the dependencies between the entities in the entity relationship data.

[0106] If a review pass instruction is received from the review terminal, it means that the reviewer has concluded that the entities in the entity relationship data and the dependencies between entities are correct and meet business needs. At this time, the step of maintaining the entity relationship data is executed to ensure that the change control system maintains the correct entity relationship data.

[0107] If the review terminal receives a review failure instruction, or does not receive a review pass instruction within the second time period, it means that the reviewer has a high probability of reviewing that the entities in the entity relationship data and the dependencies between the entities are wrong or do not meet business needs. At this time, the review terminal is requested to request change description data for changing the entities in the entity relationship data, so as to modify the entity relationship data based on the entity change description data, so that the entity relationship data is correct and meets business needs. The entity change description data may include but is not limited to the following: description data for modifying the entity configuration data of the entity, and description data for modifying the dependencies between entities. The entity change description data can be used to determine the entities that need to be changed in the set entity relationship data, and enable the change control system to modify the entities that need to be changed. After the change control system modifies the set entity relationship data, the modified entity relationship data is provided to the review terminal for the reviewer to review the entities in the entity relationship data and the dependencies between entities through the review terminal. Repeat the above process until the review pass instruction is received from the review terminal.

[0108] The second type is that for entities such as enterprises, they will pre-set a large amount of entity relationship data in advance, and they may only have the need for change control on some of the entity relationship data. Therefore, in order to flexibly meet the user's change control needs, the change control method of entity relationship data provided in this embodiment may also include the following entity relationship data acquisition process, which may specifically include the following steps: monitoring whether a control instruction is received, the control instruction is used to specify the entity relationship data that needs to be changed and controlled, and if received, the entity relationship data specified by the control instruction is obtained and maintained.

[0109] In this embodiment, the authority to issue control instructions is opened to users, so that users can flexibly specify the entity relationship data that needs to be changed and controlled through control instructions based on their own control needs, so that the change control system can maintain it. When a control instruction is received, it means that the user expects to change and control the entity relationship data specified by the control instruction. Therefore, the change control system obtains the entity relationship data specified by the control instruction and maintains it.

[0110] The above two methods for obtaining entity relationship data may be used alone or in combination, which is not limited in this embodiment.

[0111] In some embodiments of the present application, combined with the process of obtaining entity relationship data in the previous embodiment, a change control system applied to the change control method of entity relationship data provided in this embodiment has the following features: Figure 2 The architecture diagram of the change management system shown in Figure 1 is shown in Figure 2.

[0112] from Figure 2It can be seen that the change control system includes a data collection component, which performs data source management and API services. The data source management can provide project data for the data source of entity relationship data setting, and the API service is used to collect project data from the data source. The change control system includes a metadata maintenance component, which is used to extract entities and entity dependencies from the collected project data, and to extract hidden dependencies from the project data. The change control system includes a relationship maintenance component, which is used to set entity relationship data based on the extracted entities and entity dependencies, and to maintain them. The change control system includes a relationship application component, which is used to view entity relationship data, display icons, check points in the R&D process, and view, analyze and evaluate entity relationships. The change control system includes a general capability component, which is used to apply the change control method for entity relationship data provided in this embodiment to perform change control. In addition, the general capability component may also include alarms, link tracking, permission management and log management related to change control. It can be seen that the change control system used in the change control method for entity relationship data provided in this embodiment has the following advantages: First, by automatically and intelligently discovering and continuously maintaining the dependencies between entities, the impact of changes can be accurately evaluated and analyzed during changes, reducing the risks caused by omissions, automatically associating approval flows and notifications, and improving the controllability and security of changes. Second, by extracting and mining dependencies that combine automation and intelligence, manual labor can be greatly reduced and system operation and maintenance efficiency can be improved. Third, the scattered entity relationship knowledge can be uniformly maintained to avoid knowledge loss, which is conducive to the accumulation and inheritance of knowledge within the enterprise.

[0113] Furthermore, an embodiment of the present application also provides a device for controlling changes in entity relationship data, such as Figure 3 As shown, the entity relationship data change control device provided in this embodiment is applied to a change control system, and the change control system is used to maintain entity relationship data, and the entity relationship data is used to describe multiple entities and the dependency relationship between the multiple entities. Then, the entity relationship data change control device provided in this embodiment may include:

[0114] A determination module 21 is configured to determine a second entity in the plurality of entities that has a dependency relationship with the first entity if it is monitored that any first entity in the plurality of entities needs to be changed;

[0115] The blocking module 22 is configured to block the change of the first entity if there is an entity in the second entity that becomes abnormal due to the change of the first entity.

[0116] The change control device for entity relationship data provided in the embodiment of the present application, when it is monitored that any first entity among the multiple entities included in the entity relationship data needs to be changed, determines the second entity among the multiple entities that has a dependency relationship with the first entity. If there is an entity in the second entity that is abnormal due to the change of the first entity, the change of the first entity is prevented. It can be seen that the scheme provided in the embodiment of the present application does not directly change the entity when it is monitored that any entity in the entity relationship data needs to be changed, but first determines the entity in the entity relationship data that has a dependency relationship with the entity, and then determines whether the change of the entity will cause the determined entity with a dependency relationship to be abnormal, and as long as it is determined that an abnormality will occur, the entity change is prevented. In this way, the change control of entity relationship data can be achieved, thereby reducing the probability of abnormalities in entity relationship data due to changes.

[0117] In some embodiments of the present application, Figure 4 As shown, the determination module 21 is specifically used to determine, based on the dependency relationships between the multiple entities maintained, an entity among the multiple entities that has a dependency relationship with the first entity; and / or, through a first preset model, based on change description data that needs to be changed for the first entity, entity configuration data for describing the maintained entities included in the entity relationship data, and dependency data for describing the dependency relationships between the maintained entities, determine an entity among the multiple entities that has a hidden dependency relationship with the first entity, wherein the hidden dependency relationship is a dependency relationship that does not exist in the dependency relationships maintained by the change management and control system and is identified by the first preset model based on the change description data of the first entity that needs to be changed; and determine the determined entity as the second entity among the multiple entities that has a dependency relationship with the first entity.

[0118] In some embodiments of the present application, Figure 4 As shown, the entity relationship data change control device provided in this embodiment may also include:

[0119] A first push module 23 is used to push the change description data that needs to be changed in the first entity and the dependency relationship between the second entity and the first entity to a target change approval terminal;

[0120] The first determination module 24 is configured to determine that there is an entity in the second entity that is abnormal due to a change in the first entity if an approval failure instruction is received from the target change approval terminal or the approval instruction is not received within a first period of time.

[0121] In some embodiments of the present application, Figure 4 As shown, the entity relationship data change control device provided in this embodiment may also include:

[0122] The second push module 25 is used to obtain a change suggestion for the first entity that needs to be changed based on the change description data that needs to be changed in the first entity, the dependency relationship between the second entity and the first entity, the entity relationship data included in the entity configuration data for describing the maintained entity and the dependency data for describing the dependency relationship between the maintained entities through a second preset model, wherein the change suggestion is used to indicate the probability that the change to the first entity will cause an abnormality in the second entity; and push the change suggestion to the target change approval terminal so that the approver can approve whether the first entity can be changed based on the change description data pushed by the first push module 23, the dependency relationship between the second entity and the first entity, and the change suggestion.

[0123] In some embodiments of the present application, Figure 4 As shown, the entity relationship data maintained by the change control system has corresponding projects, and the projects have different project stages, and different project stages have different approval personnel. Then, the entity relationship data change control device provided in this embodiment may also include:

[0124] The selection module 26 is used to determine the current project stage of the project corresponding to the entity relationship data; and determine the change approval terminal of the approval personnel corresponding to the project stage as the target change approval terminal.

[0125] In some embodiments of the present application, Figure 4 As shown, the entity relationship data change control device provided in this embodiment may also include:

[0126] A prediction module 27, configured to predict, by a third preset model, the probability that a change to the first entity causes an abnormality in each of the second entities based on the change description data that needs to be changed to the first entity, the dependency relationship between the second entity and the first entity, the entity configuration data used to describe the maintained entities and the dependency data used to describe the dependency relationship between the maintained entities included in the entity relationship data;

[0127] The second determination module 28 is configured to determine that there is an entity in the second entity that is abnormal due to a change in the first entity, if there is at least one second entity whose probability reaches a preset probability threshold.

[0128] In some embodiments of the present application, Figure 4 As shown, the entity relationship data change control device provided in this embodiment may also include:

[0129] Maintenance module 29 is used to obtain project data related to entities of a specified type in a specified project if the change management system needs to maintain entity relationship data of entities of a specified type in the specified project; extract entities and entity dependency relationships from the project data through a target extraction method; set entity relationship data based on the extracted dependencies between entities, and maintain the set entity relationship data.

[0130] In some embodiments of the present application, Figure 4 As shown, the entity relationship data change control device provided in this embodiment may also include:

[0131] A change module 30, configured to perform a required change on the first entity if there is no entity in the second entity that is abnormal due to the change of the first entity;

[0132] In some embodiments of the present application, Figure 4 As shown, each entity maintained by the change control system has a corresponding change permission, and the change permission is applicable to a corresponding role. Then, the determination module 21 can also be used to determine the role of the user who initiates the change of the first entity; determine whether the role has the corresponding change permission of the first entity; if so, trigger the step of determining a second entity among the multiple entities that has a dependency relationship with the first entity; if not, trigger the warning module 31 to issue an unchangeable warning for the first entity;

[0133] In some embodiments of the present application, Figure 4 As shown, the entity relationship data maintained by the change control system has a corresponding project, and the entity relationship data is obtained based on the project data of the corresponding project. Then, the entity relationship data change control device provided in this embodiment may also include:

[0134] A detection module 32 is used to detect whether the project data of the project corresponding to the entity relationship data is updated; if so, entity configuration data for describing the entity and dependency data for describing the dependency relationship between entities are extracted from the updated project data; the extracted entity configuration data and dependency data are compared with the entity relationship data maintained by the change management and control system; if a target situation is found in any entity in the entity relationship data, the entity is monitored to need to be changed; wherein the target situation includes at least one of the following: the entity configuration data of the entity in the entity relationship data is different from the extracted entity configuration data, and the dependency data of the entity in the entity relationship data is different from the extracted dependency data.

[0135] In some embodiments of the present application, Figure 4As shown, the maintenance module 29 can also be used to extract hidden dependencies from the project data through a fourth preset model; and add the hidden dependencies extracted between entities to the dependencies between entities extracted by the target extraction method.

[0136] In some embodiments of the present application, Figure 4 As shown, the maintenance module 29 can also be used to provide the set entity relationship data to the review terminal, so that the reviewer can review the entities in the entity relationship data and the dependencies between the entities through the review terminal; if a review pass instruction is received from the review terminal, the step of maintaining the entity relationship data is executed; if a review fail instruction is received from the review terminal, or the review pass instruction is not received within the second time period, the review terminal is requested to provide change description data for changing the entities in the entity relationship data.

[0137] In the entity relationship data change control device provided in the embodiment of the present application, the detailed explanations used in the operation of each functional module can be found in the corresponding detailed explanations of the above-mentioned entity relationship data change control method embodiment, which will not be repeated here.

[0138] Furthermore, an embodiment of the present application also provides a computer-readable storage medium, wherein the storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the above-mentioned entity relationship data change management method.

[0139] Furthermore, an embodiment of the present application also provides an electronic device, comprising: a memory for storing a program; and a processor, coupled to the memory, for running the program to execute the above-mentioned entity relationship data change management method.

[0140] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0141] It is understandable that the related features in the above methods and devices can be referenced to each other. In addition, the "first", "second" and the like in the above embodiments are used to distinguish the embodiments, but do not represent the advantages and disadvantages of the embodiments.

[0142] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0143] The algorithm and display provided herein are not inherently related to any particular computer, virtual system or other device. Various general purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious to construct the structure required for this type of system. In addition, the application is not directed to any specific programming language either. It should be understood that various programming languages ​​can be utilized to realize the content of the application described herein, and the description of the above specific language is to disclose the preferred embodiment of the application.

[0144] In addition, the memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0145] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0146] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data cutover device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data cutover device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0147] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data switching device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0148] These computer program instructions can also be loaded onto a computer or other programmable data transfer device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0149] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0150] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0151] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0152] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0153] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0154] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for controlling changes in entity relationship data, characterized in that: Applied to a change management and control system, the change management and control system is used to maintain entity relationship data, the entity relationship data is used to describe multiple entities and dependencies between the multiple entities, the method includes: If it is monitored that any first entity among the multiple entities needs to be changed, determining a second entity among the multiple entities that has a dependency relationship with the first entity; If there is an entity in the second entity that becomes abnormal due to the change of the first entity, the change of the first entity is prevented.

2. The method according to claim 1, characterized in that Determining a second entity among the multiple entities that has a dependency relationship with the first entity includes: Based on the dependency relationships among the multiple entities maintained, determine the entities among the multiple entities that have a dependency relationship with the first entity; and / or, through a first preset model, based on the change description data that needs to be changed for the first entity, the entity configuration data for describing the maintained entities included in the entity relationship data, and the dependency data for describing the dependency relationships between the maintained entities, determine the entities among the multiple entities that have a hidden dependency relationship with the first entity, wherein the hidden dependency relationship is a dependency relationship that does not exist in the dependency relationships maintained by the change management and control system and is identified by the first preset model based on the change description data of the first entity that needs to be changed; The determined entity is determined as a second entity among the multiple entities that has a dependency relationship with the first entity.

3. The method according to claim 1, characterized in that Determining that there is an entity in the second entity that is abnormal due to a change in the first entity includes: Pushing the change description data that needs to be changed in the first entity and the dependency relationship between the second entity and the first entity to the target change approval terminal; If an approval failure instruction fed back by the target change approval terminal is received, or the approval instruction is not received within the first period of time, it is determined that an abnormal entity exists in the second entity due to the change of the first entity.

4. The method according to claim 3, characterized in that: The method further includes: obtaining a change suggestion for the first entity that needs to be changed based on the change description data of the first entity that needs to be changed, the dependency relationship between the second entity and the first entity, the entity configuration data for describing the maintained entity and the dependency data for describing the dependency relationship between the maintained entities included in the entity relationship data through a second preset model, wherein the change suggestion is used to indicate the probability that the second entity will be abnormal due to the change of the first entity; pushing the change suggestion to the target change approval terminal, so that the approver can approve whether the first entity can be changed based on the received change description data, the dependency relationship between the second entity and the first entity, and the change suggestion through the target change approval terminal; and / or, The entity relationship data maintained by the change management and control system has corresponding projects, and the projects have different project stages, and different project stages have different approval personnel. Then, the method also includes: determining the current project stage of the project corresponding to the entity relationship data; and determining the change approval terminal of the approval personnel corresponding to the project stage as the target change approval terminal.

5. The method according to claim 1, characterized in that Determining that there is an entity in the second entity that is abnormal due to a change in the first entity includes: Predicting, by a third preset model, the probability that a change to the first entity causes an abnormality in each of the second entities based on the change description data that needs to be changed to the first entity, the dependency relationship between the second entity and the first entity, the entity configuration data used to describe the maintained entities and the dependency data used to describe the dependency relationship between the maintained entities included in the entity relationship data; If there is at least one second entity whose probability reaches a preset probability threshold, it is determined that there is an entity in the second entity that is abnormal due to a change in the first entity.

6. The method according to any one of claims 1 to 5, characterized in that The method further includes: if the change control system is required to maintain entity relationship data of a specified type of entity of a specified project, obtaining project data related to the specified type of entity in the specified project; extracting entities and entity dependency relationships from the project data by a target extraction method; setting entity relationship data based on the extracted entities and dependency relationships between entities, and maintaining the set entity relationship data; and / or, The method further includes: if it is determined that there is no entity in the second entity that is abnormal due to the change of the first entity, executing the required change on the first entity; and / or, Each entity maintained by the change control system has a corresponding change permission, and the change permission is applicable to a corresponding role. Then, the method further includes: determining the role of the user who initiates the change of the first entity; determining whether the role has the corresponding change permission of the first entity; if so, executing the step of determining a second entity in the multiple entities that has a dependency relationship with the first entity; if not, issuing an unchangeable warning for the first entity; and / or, The entity relationship data maintained by the change management and control system has corresponding projects, and the entity relationship data is obtained based on the project data of the corresponding projects, then, the method also includes: detecting whether the project data of the project corresponding to the entity relationship data is updated; if so, extracting the entity configuration data used to describe the entity and the dependency data used to describe the dependency relationship between entities from the updated project data; comparing the extracted entity configuration data and dependency data with the entity relationship data maintained by the change management and control system; if the comparison shows that any entity in the entity relationship data has a target situation, it is monitored that the entity needs to be changed; wherein, the target situation includes at least one of the following: the entity configuration data of the entity in the entity relationship data is different from the extracted entity configuration data, and the dependency data of the entity in the entity relationship data is different from the extracted dependency data.

7. The method according to claim 6, characterized in that The method further includes: extracting hidden dependency relationships from the project data through a fourth preset model; adding the extracted hidden dependency relationships between entities to the dependency relationships between entities extracted through the target extraction method; and / or, The method also includes: providing the set entity relationship data to a review terminal so that reviewers can review the entities in the entity relationship data and the dependencies between the entities through the review terminal; if a review pass instruction is received from the review terminal, executing the step of maintaining the entity relationship data; if a review fail instruction is received from the review terminal, or the review pass instruction is not received within a second time period, requesting the review terminal for change description data for changing the entities in the entity relationship data.

8. A device for controlling changes in entity relationship data, characterized in that: Applied to a change control system, the change control system is used to maintain entity relationship data, the entity relationship data is used to describe multiple entities and dependencies between the multiple entities, the device includes: a determination module, configured to determine a second entity in the plurality of entities that has a dependency relationship with the first entity if it is monitored that any first entity in the plurality of entities needs to be changed; The blocking module is used to block the change of the first entity if there is an entity in the second entity that becomes abnormal due to the change of the first entity.

9. A computer-readable storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the entity relationship data change management method described in any one of claims 1 to claim 7.

10. An electronic device, characterized in that: The electronic device comprises: Memory, used to store programs; A processor, coupled to the memory, is used to run the program to execute the entity relationship data change management method described in any one of claims 1 to 7.

Images