Change scheme automatic generation method and related device

Abstract

The invention provides a change scheme automatic generation method and a related device, and the change scheme is automatically generated by adopting the change scheme automatic generation method instead of manually writing the change scheme. During automatic generation, data searching can be automatically carried out based on a software name and a change scheme template, change parameter information corresponding to the software name is obtained, and then target change parameter information is screened out from the change parameter information according to target change content needing to be changed; and a target change operation process is screened out from the change operation processes of the change contents, so that the final change data is only data related to the target change contents, and irrelevant data is eliminated. Then, the target change parameter information is added into the change scheme template, the change operation processes except the target change operation process in the change scheme template are deleted, the change scheme of the change software is automatically obtained, manpower is saved, and the generation efficiency of the change scheme is improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing, and more specifically, to a method for automatically generating a change plan and a related device. Background Art

[0002] The change plan plays an indispensable role in the change work of the civil aviation flight information system. It can serve as an operational guide during the change implementation process, standardize the change operation steps, record the operation details of each step, and effectively reduce the change failure caused by incorrect operation.

[0003] When civil aviation flight information system maintenance personnel complete system changes, they manually write change plans. When writing manually, they manually enter all the information and steps of the change plan, which consumes a lot of time and energy of maintenance personnel, making the efficiency of generating change plans low. Summary of the invention

[0004] This summary is provided to introduce concepts in a brief form that will be described in detail in the detailed description below. This summary is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] In view of this, the present invention provides a method for automatically generating a change plan and a related device to solve the problem of low efficiency in generating a change plan.

[0006] In order to solve the above technical problems, the present invention adopts the following technical solutions:

[0007] A method for automatically generating a change plan, comprising:

[0008] Acquire change plan configuration information; the change plan configuration information includes the software name of the change software, the target change content in the change software, and a change plan template; the change plan template includes the change operation process of each change content;

[0009] Based on the software name and the change plan template, obtaining change parameter information corresponding to the software name, the change parameter information including change work order information and change resource information;

[0010] Filtering out target change parameter information associated with the target change content from the change parameter information, and filtering out target change operation procedures corresponding to the target change content from the change operation procedures of each change content;

[0011] The target change parameter information is added to the change plan template, and the change operation process except the target change operation process in the change plan template is deleted to obtain the change plan of the changed software.

[0012] A device for automatically generating a change plan, comprising:

[0013] An information acquisition module, used to acquire change plan configuration information; the change plan configuration information includes the software name of the change software, the target change content in the change software, and a change plan template; the change plan template includes the change operation process of each change content;

[0014] A parameter acquisition module, used to acquire change parameter information corresponding to the software name based on the software name and the change plan template, wherein the change parameter information includes change work order information and change resource information;

[0015] A data screening module, used to screen out target change parameter information associated with the target change content from the change parameter information, and screen out target change operation procedures corresponding to the target change content from the change operation procedures of each change content;

[0016] The scheme generating module is used to add the target change parameter information to the change scheme template, and delete the change operation process except the target change operation process in the change scheme template, so as to obtain the change scheme of the change software.

[0017] A computer-readable storage medium stores at least one instruction, and when the at least one instruction is executed by a processor, the above-mentioned method for automatically generating a change plan is implemented.

[0018] An electronic device comprising: a memory and a processor;

[0019] Wherein, the memory is used to store programs;

[0020] The processor calls the program and is used to execute the above-mentioned method for automatically generating a change plan.

[0021] Compared with the prior art, the present invention has the following beneficial effects:

[0022] The present invention provides a method for automatically generating a change plan and a related device. In the present invention, the change plan is no longer manually written, but the change plan is automatically generated by the change plan automatic generation method. During the automatic generation, data search can be automatically performed based on the software name and the change plan template to obtain the change parameter information corresponding to the software name, and then the target change parameter information with an associated relationship with the target change content is screened out from the change parameter information for the target change content to be changed, and the target change operation process corresponding to the target change content is screened out from the change operation process of each change content, so that the final change data is only data related to the target change content, and irrelevant data is eliminated. Then, the target change parameter information is added to the change plan template, and the change operation process in the change plan template except the target change operation process is deleted, and the change plan of the changed software is automatically obtained, saving manpower and improving the generation efficiency of the change plan. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0024] Figure 1 A flowchart of a method for automatically generating a change plan provided by an embodiment of the present invention;

[0025] Figure 2 A flowchart of a method for obtaining change parameter information provided by an embodiment of the present invention;

[0026] Figure 3 A schematic diagram of a scenario of a method for obtaining change parameter information provided by an embodiment of the present invention;

[0027] Figure 4 A schematic diagram of a scenario of a method for adding template data provided by an embodiment of the present invention;

[0028] Figure 5 A schematic diagram of the structure of a device for automatically generating a change plan provided by an embodiment of the present invention;

[0029] Figure 6 A modification scheme provided in an embodiment of the present invention automatically generates an interaction diagram of internal components of a device;

[0030] Figure 7 A schematic diagram of the structure of a device for automatically generating a change plan provided by an embodiment of the present invention;

[0031] Figure 8A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0032] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain 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 construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0033] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0034] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0035] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0036] When civil aviation flight information system maintenance personnel complete system changes, they manually write change plans. When writing manually, they need to manually enter various information and steps of the change plan. This manual writing of change plans has the following disadvantages:

[0037] First, manually writing change plans takes a lot of time and effort. Maintenance personnel need to find the change information and enter it manually, and need to spend time checking the information to ensure the accuracy of the change plan. This will consume a lot of time and energy of maintenance personnel, resulting in low work efficiency. When faced with more frequent system changes, there may be problems such as insufficient preparation time.

[0038] Secondly, manual change plan writing is prone to errors and omissions. During the change plan writing process, maintenance personnel need to find and enter the change information by themselves. Due to manual operation, they may fill in the change information incorrectly or omit some important information during the writing process, which will lead to inaccurate change plans and increase the risks of system maintenance and change work.

[0039] In addition, manually written change plans usually lack structure and standardization. Different maintainers have different writing habits, and they also have different structures and styles when writing change plans, which will affect the readability of the change plan, making it difficult for other team members to learn and use it, and bringing inconvenience to subsequent system maintenance and change work.

[0040] In order to solve the problems of low efficiency, low accuracy, and lack of structure and standardization of the change plans caused by the above manual work, the change plans can be generated in an automated manner. However, the existing technology for automatically generating change plans is only applicable to open source software that is publicly available and well-known on the Internet. Since the operation steps and operation buttons of the self-developed application software are different from those of the open source software, the general automatic generation method of change plans is not applicable to the self-developed application software. Therefore, it is necessary to develop a unique automatic generation method of change plans for the application software within the enterprise in the present invention.

[0041] In this embodiment, the application software can be changed based on traditional server deployment platforms, cloud environment deployment platforms, etc. The traditional server deployment platform and the cloud environment deployment platform are both independently developed, and different platforms need to be used for different software and versions, and the change resources and change steps of different platforms are also different.

[0042] The traditional server deployment platform can deploy application software currently using jboss (an open source application server based on J2EE), tode and other servers. The cloud environment deployment platform deploys software and versions currently using the cloud environment.

[0043] When changing the application software deployed on traditional servers or cloud platforms, the present invention can pre-write multiple change plan templates according to the actual change requirements, including common tool change templates (managed by traditional server deployment platforms and cloud environment deployment platforms) and custom change templates (managed by custom tools), to ensure the standardization and scalability of the change plan. Then use the change plan generation tool to generate the change implementation plan and rollback plan, and finally synchronize and update the manually adjusted implementation plan to obtain the inspection plan and execution record document that meet the change requirements, ensuring the configurability of the automatic generation device and the flexibility during use.

[0044] In addition, the change plan template in the present invention pre-writes the change operation process of the change content corresponding to the application software, which can select the appropriate change operation process according to the independently developed application software, and can reduce the time for writing the change operation process when the change plan is generated, thereby improving the efficiency and accuracy of the change plan generation.

[0045] On the basis of the above content, an embodiment of the present invention provides a method for automatically generating a change plan and a related device. In the present invention, the change plan is no longer manually written, but the change plan is automatically generated by the change plan automatic generation method. During the automatic generation, it is possible to automatically search for data based on the software name and the change plan template, obtain the change parameter information corresponding to the software name, and then filter out the target change parameter information with an association relationship with the target change content from the change parameter information for the target change content to be changed, and filter out the target change operation process corresponding to the target change content from the change operation process of each change content, so that the final change data is only data related to the target change content, and irrelevant data is eliminated. Then, the target change parameter information is added to the change plan template, and the change operation process in the change plan template except the target change operation process is deleted, and the change plan of the changed software is automatically obtained, saving manpower and improving the generation efficiency of the change plan.

[0046] In one implementation of the present invention, a method for automatically generating a change plan is provided. Figure 1 , which may include:

[0047] S11. Obtain change plan configuration information.

[0048] The change plan configuration information includes the software name of the change software, the target change content in the change software, and the change plan template.

[0049] Specifically, if a certain application software needs to be changed, the software name of the changed software can be entered. Generally, if the changed software is an application software, the abbreviation of the software name of the application software needs to be entered, such as XXX application software.

[0050] In actual applications, when changing application software, it may be necessary to change only a part of the content, or the entire application software. Therefore, in order to be able to better generate change plans for the change content later, in this embodiment, the user is required to input the target change content in the change software, such as the target change content is a server or database.

[0051] In addition, the user also needs to select a change plan template. The user can manually enter the identification number of the change plan template, such as 001 or the template name, or select it through a drop-down menu.

[0052] For example, if the user needs to make general changes to the application software deployed on the traditional server, they can choose the change plan template for the traditional server deployment platform. If they need to make general changes to the application software deployed in the cloud environment, they can choose the change plan template for the cloud environment deployment platform. If they need to make personalized changes to the application software deployed on the traditional server deployment platform or the cloud environment deployment platform, they can choose the custom template in the customization tool. Custom templates are personalized templates that meet user needs and can be generated in advance.

[0053] In this embodiment, a front-end page can be pre-configured, and a change plan configuration interface is displayed in the front-end page. The user can enter the software name of the change software, the target change content in the change software, and the identification number of the change plan template in the change plan configuration interface or select through a drop-down menu. After the user clicks to confirm, the software name of the change software, the target change content in the change software, and the identification number of the change plan template entered by the user in the change plan configuration interface can be obtained, and then the change plan template corresponding to the identification number of the change plan template is determined. The change plan template can be stored in a database and can be obtained through the identification number.

[0054] In actual application, the change plan template includes the change operation process of each change content, that is, as long as the change operation process required for the change is involved, it can be queried in the change plan template.

[0055] For example, the change plan template of the traditional server deployment platform includes the change operation process when the application software deployed by the traditional server changes different contents, such as the change operation process when changing the first content, the change operation process when changing the second content, the change operation process when changing the third content...

[0056] S12: Based on the software name and the change plan template, obtain change parameter information corresponding to the software name.

[0057] In practical applications, the change parameter information mainly refers to some parameters used in this change, and the change parameter information includes change work order information and change resource information. The change work order information refers to the information related to the work order during the change process, and the change resource information refers to the information related to the resource during the change process.

[0058] The process of obtaining change work order information and change resource information is different. Figure 2 , which may include:

[0059] S21. Query the change work order information corresponding to the software name from the change management system.

[0060] In this embodiment, the change management system is responsible for managing the change process of the application software. The application software (or software) that needs to be changed needs to complete the approval, start, end and other processes in the change management system.

[0061] The change management system adopts a work order approach when managing application software, so the change work order information in the present invention can be queried and obtained from the change management system.

[0062] In actual applications, the change order information corresponding to the software name can be obtained from the change management system based on the software name. The change order information mainly includes the change order number, change title, changed software version (when the changed software is the system, it is the changed system version), change date, change executor and inspector, etc., and the extracted data is entered into the change information record document.

[0063] In actual applications, when acquiring data in the change management system, you need to log in using your login password, and then search the change management system for work orders whose change start time is within one month from today and whose status is non-terminated, and obtain the change work order information based on the software name filled in on the front-end page.

[0064] In order to enable the technicians in this embodiment to more clearly understand the specific implementation of step S21, an example is now given.

[0065] 1. Obtaining change work order information when the change plan is automatically generated based on the traditional server deployment platform:

[0066] The change data extraction operation requires you to enter the user name and password of the change management system in advance, and specify the software name of the application software for which the change plan needs to be generated. Then the change data extraction component extracts the change data from the change management system and enters it into the change information record document, as follows:

[0067] 1.1 Enter the change management system user name, password, and software name of the change software;

[0068] 1.2 Log in to the change management system and retrieve the application software change work order;

[0069] 1.3 Confirm the status of the change work order (find the work order whose change start time is within one month from today and whose status is not terminated);

[0070] 1.4 Extract the change work order information corresponding to the software name of the changed software;

[0071] 1.5 Write the change order information into the change information record document.

[0072] The parameters required for input in this method are shown in Table 1:

[0073] Table 1

[0074] Parameter name illustrate Login Information Username: user, password: password Change the software name of the software The name of the change software for which a change plan needs to be generated

[0075] The change work order information corresponding to the software name of the changed software can be extracted as shown in Table 2:

[0076] Table 2

[0077] Parameter name illustrate ID Change work order number TITLE Change Title SOFTWARE Change the application name SOFTWARE_VERSION Changing software version Expect_Starttime Change Date z Change Executor fhr Change Inspector

[0078] 2. Obtaining change work order information when the change plan is automatically generated based on the cloud environment deployment platform:

[0079] Similar to the automatic generation implementation example of change plans based on a traditional server deployment platform, in this implementation example, the operation of extracting change data requires the user name and password to be entered in advance, and the software name of the change software for which the change plan needs to be generated is specified, the change work order information is extracted from the change management system, and the change information record document is entered.

[0080] 3. Obtaining change work order information when a change plan based on a custom template is automatically generated:

[0081] Similar to the automatic generation implementation example of the change plan based on the traditional server deployment platform, the change data extraction operation extracts the change work order information from the change management system and enters the change information record document according to the input user name, password and software name of the changed software.

[0082] S22: Retrieve the change resource information corresponding to the software name, the changed software version and the change plan template in the resource database.

[0083] Specifically, the information stored in the resource database is all the resources of the flight information system, including different application software and different versions. The search needs to retrieve the corresponding resource information of the software and version that has been changed.

[0084] When searching in the resource database, the change information record document is read, and the corresponding resource database is searched according to the recorded software name and version of the changed software, as well as the selected change plan template, to obtain the change resource information required to generate the change plan, such as the change resource type, execution account, server IP (Internet Protocol), database IP and other information.

[0085] In this embodiment, the above three embodiments are still used for description.

[0086] 1. Retrieval of change resource information when automatically generating change plans based on traditional server deployment platforms:

[0087] Retrieving the changed resource information is to retrieve the data in the traditional server resource database according to the software name and version of the changed software, including the changed resource type, server IP, database IP, etc. At the same time, this step reads the specific parameters required by the template according to the deployment change template of the traditional server deployment platform, including pipeline name, online deployment name, rollback deployment name, etc., to find and filter out the resource information that may be needed to automatically generate the change plan from the resource database. Among them, the pipeline name and online deployment name can be obtained through Figure 3 The pipeline name extraction method and deployment name extraction method in are obtained.

[0088] The detailed operation process of the change resource retrieval component to retrieve the change resource information is as follows:

[0089] 2.1 Connect to the traditional server to change the resource database;

[0090] 2.2 Read the software name and version of the changed software;

[0091] 2.3 Retrieve and collect the changed resource data corresponding to the software name and changed software version of the changed software;

[0092] 2.4 Read the change plan template of the traditional server deployment platform;

[0093] 2.5 Retrieve and collect parameter information for specific parameters required in the change plan template.

[0094] The changed resource information may be as shown in Table 3, wherein Table 3 is only an example of partial changed resource information.

[0095] Table 3

[0096] Parameter name illustrate Pipeline Name Pipeline names in traditional server deployment platforms Online deployment name Online deployment name in traditional server deployment platform rollback deployment name Rollback deployment name in traditional server deployment platform

[0097] 2. Retrieval of change resource information when automatically generating change plans based on cloud environment deployment platforms:

[0098] Retrieving changed resources is to search the data in the resource library according to the software name of the changed software, the changed software version, and the change plan template of the cloud environment deployment platform. Specifically, the software name of the changed software and the specific parameters corresponding to the changed software version can be read according to the change plan template, including cluster grouping, application module, new version image, old version information, etc. Cluster grouping, application module, new version image, old version information can be obtained through Figure 3 The cluster grouping extraction method, application module extraction method and version information extraction method shown are implemented.

[0099] The detailed operation process of changing resource information retrieval is as follows:

[0100] 3.1 Connect to the cloud environment change resource database;

[0101] 3.2 Read the software name and version of the changed software;

[0102] 3.3 Read the change plan template of the cloud environment deployment platform;

[0103] 3.4 Retrieve and collect specific parameters required for the change plan template.

[0104] The changed resource information may be as shown in Table 4, wherein Table 4 is only an example of partial changed resource information.

[0105] Table 4

[0106] Parameter name illustrate Cluster Grouping Cluster group name Application Module Application module name New version image The name of the image to be launched Old version information Current application version information

[0107] 3. Retrieval of change resource information when a change plan is automatically generated based on a custom template:

[0108] Retrieving change resources is to search the data in the resource library according to the software name and version of the changed software, and read the parameters specified in the custom change plan template.

[0109] This method requires manual adjustment and generation of custom templates in advance, and Figure 3 The corresponding parameters are obtained by the custom parameter extraction method in , and the specific parameters can be found in Table 5.

[0110] Table 5

[0111] Parameter name illustrate Parameter 1 Custom parameters, the format is {key-value}, key allows customization ...

[0112] S13: Filter out target change parameter information associated with the target change content from the change parameter information, and filter out target change operation procedures corresponding to the target change content from the change operation procedures of the various change contents.

[0113] In actual applications, an application software can be divided into multiple parts. When making changes, there is a situation where only a certain part is changed. At this time, the change content may only be the content corresponding to the changed part in the application software. At this time, it may only involve part of the change work order information and change resource information obtained above. Therefore, it is necessary to screen the change work order information and change resource information again based on the target change content to remove the content that does not need to be changed this time.

[0114] During the screening, the target change parameter information that is associated with the target change content is screened out from the change parameter information. Specifically, the target change content is the specific content that needs to be changed, and the resource types involved, such as servers, databases, etc., can be analyzed from the specific content. Therefore, based on the target change content, the change work order information and the change resource information can be screened to obtain the target change parameter information.

[0115] For example, if the target change content is a server, the server IP, pipeline name, online deployment name, and rollback deployment name are filtered out from the change resource information.

[0116] The change parameter information screening process in this embodiment is the process of integrating the change data, and the above three scenarios are still used as examples for illustration.

[0117] 1. The process of integrating change data when automatically generating change plans based on traditional server deployment platforms:

[0118] The integrated change data component further screens the retrieved data according to the selected target change content and the change plan template of the traditional server deployment platform, obtains the work order information and resource information that meets the change requirements, completes the automatic matching of parameters and automatic integration of resources, and records them in the document to form the final change information record document.

[0119] The content of the change information record document includes the extracted change work order information and the retrieved change resource information. The main parameters are shown in Table 6:

[0120] Table 6

[0121] Parameter name illustrate ID 20230829XXXX TITLE <![CDATA[Change Title_XXX XXX XX]]> SOFTWARE XXXX System SOFTWARE_VERSION V1 Expect_Starttime 2023-08-30 z XXX fhr XXX Pipeline Name Universal bag change Online deployment name XXX deployment,... rollback deployment name XXX rolls back deployment,...

[0122] 2. The process of integrating change data when automatically generating change plans based on cloud environment deployment platforms:

[0123] The integrated change data component screens the data according to the target change content and the change plan template of the cloud environment deployment platform to form the final change information record document. The main parameters of the change information record document obtained in this step are shown in Table 7:

[0124] Table 7

[0125] Parameter name illustrate ID 20230905XXXX TITLE Change title_XXXX SOFTWARE XXXX System SOFTWARE_VERSION V2 Expect_Starttime 2023-09-06 z XXX fhr XXX Cluster Grouping Group 1, Group 2, Group 3, ... Application Module Module 1, Module 2, ... New version image Image Name Old version information Current version number

[0126] 3. The process of integrating change data when automatically generating change plans based on custom templates:

[0127] The integrated change data component screens the data according to the target change content and the custom change template, obtains the work order information and resource information that meet the change requirements, and forms the final change information record document. The main parameters of the change information record document obtained in this step are shown in Table 8:

[0128] Table 8

[0129] Parameter name illustrate ID 20230828XXXX TITLE Change title_XXXX SOFTWARE XXXX System SOFTWARE_VERSION V2 Expect_Starttime 2023-09-07 z XXX fhr XXX Parameter 1 Airline Name ...

[0130] In addition to screening the above-mentioned change parameter information, the change operation process of each change content in the change plan template also needs to be screened based on the target change content to obtain the target change operation process corresponding to the target change content.

[0131] During screening, the change operation process of each change content includes the change content and its corresponding change operation process. Therefore, the target change content can be found and the target change operation process corresponding to the target change content can be extracted.

[0132] S14: Add the target change parameter information to the change plan template, and delete the change operation process except the target change operation process in the change plan template to obtain the change plan of the changed software.

[0133] Specifically, through step S13, the main content of the change plan, namely the target change parameter information, and the target change operation process corresponding to the target change content have been obtained. The next step is to add the target change parameter information to the template and delete the redundant change operation processes to obtain the final change plan for the software.

[0134] When adding the target change parameter information to the change plan template, refer to Figure 4 , which may include:

[0135] S31. Match the target change parameter information with the field content in the change plan template to obtain a matching result.

[0136] In this embodiment, the change plan will use a table to represent the execution steps. After the target change parameter information of the change is screened out, the target change parameter information is compared and searched with the resource name or type in each step. The comparison and search is the matching process.

[0137] S32: Based on the matching result, add the target change parameter information to the change plan template.

[0138] Specifically, after the matching is completed, the target change parameter information is filled in the corresponding position, so as to achieve the purpose of adding the target change parameter information to the change plan template.

[0139] In addition to adding the target change parameter information, the change operation processes other than the target change operation process in the change plan template will be deleted, and only the target change operation process in the change plan template will be retained, and other change operation processes not related to this change will be eliminated.

[0140] It should be noted that if the user has additional special change steps that need to be added during this change process, the special change steps can be written in the change plan configuration interface. At this time, the change plan configuration information will also carry the special change steps. Then, when generating a change plan, in addition to deleting the change operation process other than the target change operation process in the change plan template, the special change steps also need to be added to the change plan template in order to obtain the change plan for the changed software.

[0141] In addition to generating a change plan, this embodiment also generates a change inspection plan and an execution record document that are associated with the change plan. According to the change requirements, the change inspection plan and the execution record document are different from the change plan only in the name of the operator, and the content in the document is the same, so they can be generated together with the change plan.

[0142] After the change plan is generated, the user can manually adjust the plan. If the user believes that a certain step can be optimized, the change plan can be optimized and adjusted. After the adjustment is completed, the save button can be clicked to save the user-adjusted change plan.

[0143] The change inspection scheme needs to be adjusted accordingly according to the change scheme that has been adjusted by the user. In order to save manpower, in this embodiment, the unadjusted change inspection scheme can be automatically adjusted according to the adjusted change scheme.

[0144] During automatic adjustment, it is necessary to obtain manual adjustment change information when manual adjustments are made to the change plan. For example, for the optimization process of a certain step, the manual adjustment change information may include the content before and after the adjustment of the step, or the adjustment process, such as adjusting the word "modify" to "adjust", that is, recording the correction process through manual adjustment change information.

[0145] After the change plan is manually adjusted, a synchronous update operation is performed on the change inspection plan associated with the change plan based on the manually adjusted change information.

[0146] For example, if the manually adjusted change information includes the content before and after the step is adjusted, then directly search for "the content before the step is adjusted" in the change check plan and replace it with "the content after the adjustment".

[0147] If the manual adjustment change information includes the adjustment process, the change check plan is adjusted according to the adjustment process, such as changing the word "modify" to "adjust". That is, when there is a manual adjustment, the change check plan is updated synchronously, and the execution record document needs to be updated synchronously to finally generate a change plan that conforms to the online content.

[0148] After obtaining the change plan of the changed software, or manually adjusting the change plan, and adaptively adjusting the change inspection plan and the execution record document, the change plan of the changed software can be pushed to the corresponding maintenance personnel.

[0149] At this time, it is necessary to obtain the correspondence between the change plan and the terminal, and which maintenance personnel is responsible for which change plan of the software can be pre-configured.

[0150] After the corresponding relationship is obtained, the target terminal corresponding to the change plan of the changed software can be obtained from the corresponding relationship, and then the change plan of the changed software can be output to the target terminal. When pushing, the application software message can be used to push, so that the maintenance personnel can understand the progress of the change plan generation in time, so that the change work of the changed software can be completed as soon as possible, and the change efficiency can be improved.

[0151] The generation of the change plan in this embodiment is still illustrated by taking the above three scenarios as examples.

[0152] 1. Change plan generation based on the traditional server deployment platform when the change plan is automatically generated:

[0153] According to the change information record document obtained above, combined with the specific content of the change plan template of the traditional server deployment platform, a change plan is automatically generated; if the generated change plan needs to be manually adjusted, the plan update operation is executed, and the change inspection plan and execution record document are updated synchronously, and finally a change plan that conforms to the online content is obtained.

[0154] The execution flow of this step is as follows:

[0155] 4.1 Read the change information record document and the change plan template of the traditional server deployment platform;

[0156] 4.2 Automatically generate change plans for application software;

[0157] 4.3 Manually adjust the change plan;

[0158] 4.4 Synchronously update the change inspection plan and execution record documents, etc.

[0159] 2. Change plan generation for automatic generation of change plans based on cloud environment deployment platforms:

[0160] According to the change information record document obtained above, a change plan that meets the requirements is generated in combination with the specific content of the change plan template of the cloud environment deployment platform. The specific change plan generation is the same as the change plan generation when the change plan is automatically generated based on the traditional server deployment platform.

[0161] 3. Change plan generation when change plans are automatically generated based on custom templates:

[0162] According to the change information record document obtained above, a change plan that meets the requirements is generated in combination with the specific content of the custom change plan template, which is the same as the change plan generation when the change plan is automatically generated based on the traditional server deployment platform.

[0163] In this embodiment, the change plan is no longer manually written, but the change plan is automatically generated by the change plan automatic generation method. During the automatic generation, it is possible to automatically search for data based on the software name and the change plan template, obtain the change parameter information corresponding to the software name, and then filter out the target change parameter information with a correlation relationship with the target change content from the change parameter information for the target change content to be changed, and filter out the target change operation process corresponding to the target change content from the change operation process of each change content, so that the final change data is only data related to the target change content, and irrelevant data is eliminated. Then, the target change parameter information is added to the change plan template, and the change operation process in the change plan template except the target change operation process is deleted, and the change plan of the changed software is automatically obtained, saving manpower and improving the generation efficiency of the change plan.

[0164] In addition, the present invention can complete the automatic generation of change plans of various template types. The present invention has the following advantages: First, it is reusable. The present invention proposes different change plan templates for existing application change tools, and supports the automatic generation of change plans for application software that uses the same tool for change; second, it is configurable. The present invention supports manual adjustment of change plans and synchronous update of other plans during the change plan generation process; third, it is extensible, that is, the change plan template can be flexibly modified and expanded to support the personalized change requirements of application software.

[0165] In order to realize the above-mentioned method for automatically generating a change plan, in another implementation of the present invention, the front-end page can allow the user to input the change plan configuration information, and then the change plan is automatically generated by the change plan automatic generation device. The change plan automatic generation device is the core part of the present invention, and the change plan automatic generation device is provided. Figure 5 , mainly includes four main components: data extraction, resource retrieval, data integration, and solution generation. Its functions are as follows:

[0166] Data extraction component: retrieves the change plan configuration information, extracts the change order information required to generate the change plan in the change management system, performs data matching and adds the required content to the change information record document. This module realizes the automatic acquisition of change order information and can perform data retrieval by entering the software name of the change software.

[0167] Resource retrieval component: This component automatically searches the database based on the software name and changed software version input by the front end, obtains resource information such as the changed resource type, server IP, database IP, etc., and obtains the required specific information through the selected change plan template to realize automatic retrieval and collection of changed resource information.

[0168] Data integration component: Filter the extracted and retrieved data according to the selected change plan template, complete automatic matching of parameters and automatic integration of resources, and enter all the information required to generate the change plan in the change information record document.

[0169] Plan generation component: automatically generates a change plan based on the details of the change information record document and the change plan template, and synchronously updates the change inspection plan and execution record document based on the manually adjusted change plan to achieve automatic generation of the change plan.

[0170] The main workflow reference for the four main components of data extraction, resource retrieval, data integration, and solution generation Figure 6 , the specific implementation process can refer to the above corresponding instructions.

[0171] This embodiment can reduce the time and energy investment of system maintenance personnel while ensuring the accuracy and standardization of the change plan, thereby providing convenience and security for system maintenance and change work.

[0172] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0173] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0174] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown, or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.

[0175] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0176] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0177] Based on the above-mentioned embodiment of the method for automatically generating a change plan, another embodiment of the present invention provides an automatic generation device for a change plan, referring to Figure 7 , which may include:

[0178] The information acquisition module 11 is used to acquire the change plan configuration information; the change plan configuration information includes the software name of the change software, the target change content in the change software, and the change plan template; the change plan template includes the change operation process of each change content;

[0179] A parameter acquisition module 12, configured to acquire change parameter information corresponding to the software name based on the software name and the change plan template, wherein the change parameter information includes change work order information and change resource information;

[0180] The data screening module 13 is used to screen out target change parameter information associated with the target change content from the change parameter information, and screen out target change operation procedures corresponding to the target change content from the change operation procedures of each change content;

[0181] The solution generation module 14 is used to add the target change parameter information to the change solution template, and delete the change operation process except the target change operation process in the change solution template to obtain the change solution of the change software.

[0182] Furthermore, the information acquisition module 11 is specifically used for:

[0183] The software name of the change software, the target change content in the change software, and the identification number of the change plan template input by the user in the change plan configuration interface are obtained; and the change plan template corresponding to the identification number of the change plan template is determined.

[0184] Further, the parameter acquisition module 12 includes:

[0185] A work order information acquisition submodule is used to query the change work order information corresponding to the software name from the change management system; the change work order information includes the changed software version of the changed software;

[0186] The resource information acquisition submodule is used to retrieve the changed resource information corresponding to the software name, the changed software version and the changed scheme template in the resource database.

[0187] Further, the solution generation module 14 includes:

[0188] A matching submodule, used for matching the target change parameter information with the field content in the change plan template to obtain a matching result;

[0189] The information adding submodule is used to add the target change parameter information to the change plan template based on the matching result.

[0190] Furthermore, when the change scheme configuration information further includes special change steps, the scheme generating module 14 is further configured to:

[0191] The special change steps are added to the change plan template to obtain the change plan for the changed software.

[0192] Furthermore, it also includes:

[0193] The adaptive adjustment module is used to obtain manual adjustment change information when the change plan is manually adjusted, and based on the manual adjustment change information, perform a synchronous update operation on the change inspection plan associated with the change plan.

[0194] Furthermore, it also includes:

[0195] A relationship search module, used to obtain a corresponding relationship between a change plan and a terminal, and obtain a target terminal corresponding to the change plan of the change software from the corresponding relationship;

[0196] The data output module is used to output the change plan of the changed software to the target terminal.

[0197] Automatically generate change plans. During automatic generation, it is possible to automatically search for data based on the software name and the change plan template, obtain the change parameter information corresponding to the software name, and then filter out the target change parameter information that has a correlation with the target change content from the change parameter information for the target change content that needs to be changed, and filter out the target change operation process corresponding to the target change content from the change operation process of each change content, so that the final change data is only data related to the target change content, and irrelevant data is eliminated. Then, the target change parameter information is added to the change plan template, and the change operation process in the change plan template except the target change operation process is deleted, and the change plan of the changed software is automatically obtained, saving manpower and improving the efficiency of generating change plans.

[0198] It should be noted that, for the working process of each module and sub-module in this embodiment, please refer to the corresponding description in the above embodiment, which will not be repeated here.

[0199] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0200] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0201] Based on the above-mentioned embodiments of the method and device for automatically generating a change plan, another embodiment of the present invention provides a computer-readable storage medium, which stores at least one instruction, and when the at least one instruction is executed by a processor, the above-mentioned method for automatically generating a change plan is implemented.

[0202] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0203] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0204] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0205] Based on the above embodiments of the method and apparatus for automatically generating a change plan, another embodiment of the present invention provides a computer program product, which, when executed on an electronic device, is suitable for implementing the above method for automatically generating a change plan.

[0206] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 609, or installed from a storage device 606, or installed from a ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0207] Based on the above-mentioned embodiment of the method and device for automatically generating a change plan, another embodiment of the present invention provides an electronic device, including: a memory and a processor;

[0208] Wherein, the memory is used to store programs;

[0209] The processor calls the program and is used to execute the above-mentioned method for automatically generating a change plan.

[0210] Reference below Figure 8 , which shows a schematic diagram of the structure of an electronic device 600 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0211] like Figure 8 As shown, the electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0212] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 8 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0213] According to one or more embodiments of the present disclosure, a method for automatically generating a change plan is provided, comprising:

[0214] Acquire change plan configuration information; the change plan configuration information includes the software name of the change software, the target change content in the change software, and a change plan template; the change plan template includes the change operation process of each change content;

[0215] Based on the software name and the change plan template, obtaining change parameter information corresponding to the software name, the change parameter information including change work order information and change resource information;

[0216] Filtering out target change parameter information associated with the target change content from the change parameter information, and filtering out target change operation procedures corresponding to the target change content from the change operation procedures of each change content;

[0217] The target change parameter information is added to the change plan template, and the change operation process except the target change operation process in the change plan template is deleted to obtain the change plan of the changed software.

[0218] Further, obtain the change plan configuration information, including:

[0219] Obtaining the software name of the change software, the target change content in the change software, and the identification number of the change plan template input by the user in the change plan configuration interface;

[0220] A change plan template corresponding to the identification number of the change plan template is determined.

[0221] Further, based on the software name and the change plan template, obtaining change parameter information corresponding to the software name includes:

[0222] Querying the change work order information corresponding to the software name from the change management system; the change work order information includes the changed software version of the changed software;

[0223] The changed resource information corresponding to the software name, the changed software version and the changed solution template is retrieved from a resource database.

[0224] Further, adding the target change parameter information to the change plan template includes:

[0225] Matching the target change parameter information with the field content in the change plan template to obtain a matching result;

[0226] Based on the matching result, the target change parameter information is added to the change plan template.

[0227] Furthermore, in the case where the change scheme configuration information also includes special change steps, after deleting the change operation process other than the target change operation process in the change scheme template, the method further includes:

[0228] The special change steps are added to the change plan template to obtain the change plan for the changed software.

[0229] Further, after adding the target change parameter information to the change plan template and deleting the change operation flow except the target change operation flow in the change plan template to obtain the change plan of the change software, the method further includes:

[0230] Obtaining manual adjustment change information when manually adjusting the change plan;

[0231] Based on the manually adjusted change information, a synchronous update operation is performed on a change inspection plan associated with the change plan.

[0232] Further, after obtaining the change plan of changing the software, it also includes:

[0233] Obtain the correspondence between the change plan and the terminal;

[0234] Acquire a target terminal corresponding to the change plan of the changed software from the corresponding relationship;

[0235] The change plan of the changed software is output to the target terminal.

[0236] According to one or more embodiments of the present disclosure, there is provided a device for automatically generating a change plan, comprising:

[0237] An information acquisition module, used to acquire change plan configuration information; the change plan configuration information includes the software name of the change software, the target change content in the change software, and a change plan template; the change plan template includes the change operation process of each change content;

[0238] A parameter acquisition module, used to acquire change parameter information corresponding to the software name based on the software name and the change plan template, wherein the change parameter information includes change work order information and change resource information;

[0239] A data screening module, used to screen out target change parameter information associated with the target change content from the change parameter information, and screen out target change operation procedures corresponding to the target change content from the change operation procedures of each change content;

[0240] The scheme generating module is used to add the target change parameter information to the change scheme template, and delete the change operation process except the target change operation process in the change scheme template, so as to obtain the change scheme of the change software.

[0241] According to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores at least one instruction, and when the at least one instruction is executed by a processor, the above-mentioned method for automatically generating a change plan is implemented.

[0242] According to one or more embodiments of the present disclosure, there is provided an electronic device, including: a memory and a processor;

[0243] Wherein, the memory is used to store programs;

[0244] The processor calls the program and is used to execute the above-mentioned method for automatically generating a change plan.

[0245] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

[0246] Although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Certain features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0247] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

Claims

1. A method for automatically generating a change plan, characterized in that: include: Get the configuration information of the change plan; The change plan configuration information includes the software name of the changed software, the target change content in the changed software, and the change plan template; The change plan template includes the change operation process of each change content; Based on the software name and the change plan template, obtaining change parameter information corresponding to the software name, the change parameter information including change work order information and change resource information; Filtering out target change parameter information associated with the target change content from the change parameter information, and filtering out target change operation procedures corresponding to the target change content from the change operation procedures of each change content; The target change parameter information is added to the change plan template, and the change operation process except the target change operation process in the change plan template is deleted to obtain the change plan of the changed software.

2. The method for automatically generating a change plan according to claim 1, characterized in that: Get the change plan configuration information, including: Obtaining the software name of the change software, the target change content in the change software, and the identification number of the change plan template input by the user in the change plan configuration interface; A change plan template corresponding to the identification number of the change plan template is determined.

3. The method for automatically generating a change plan according to claim 1, characterized in that: Based on the software name and the change plan template, obtaining change parameter information corresponding to the software name includes: Querying the change work order information corresponding to the software name from the change management system; the change work order information includes the changed software version of the changed software; The changed resource information corresponding to the software name, the changed software version and the changed solution template is retrieved from a resource database.

4. The method for automatically generating a change plan according to claim 1, characterized in that: Adding the target change parameter information to the change plan template includes: Matching the target change parameter information with the field content in the change plan template to obtain a matching result; Based on the matching result, the target change parameter information is added to the change plan template.

5. The method for automatically generating a change plan according to claim 1, characterized in that: In the case where the change scheme configuration information further includes special change steps, after deleting the change operation flow except the target change operation flow in the change scheme template, the following is further included: The special change steps are added to the change plan template to obtain the change plan for the changed software.

6. The method for automatically generating a change plan according to claim 1, characterized in that: After adding the target change parameter information to the change plan template and deleting the change operation flow except the target change operation flow in the change plan template to obtain the change plan of the changed software, the method further includes: Obtaining manual adjustment change information when manually adjusting the change plan; Based on the manually adjusted change information, a synchronous update operation is performed on a change inspection plan associated with the change plan.

7. The method for automatically generating a change plan according to claim 1, characterized in that: After obtaining the change plan for changing the software, the method further includes: Obtain the correspondence between the change plan and the terminal; Acquire a target terminal corresponding to the change plan of the changed software from the corresponding relationship; The change plan of the changed software is output to the target terminal.

8. A device for automatically generating a change plan, characterized in that: include: An information acquisition module is used to obtain configuration information of the change plan; The change plan configuration information includes the software name of the changed software, the target change content in the changed software, and the change plan template; The change plan template includes the change operation process of each change content; A parameter acquisition module, used to acquire change parameter information corresponding to the software name based on the software name and the change plan template, wherein the change parameter information includes change work order information and change resource information; A data screening module, used to screen out target change parameter information associated with the target change content from the change parameter information, and screen out target change operation procedures corresponding to the target change content from the change operation procedures of each change content; The scheme generating module is used to add the target change parameter information to the change scheme template, and delete the change operation process except the target change operation process in the change scheme template, so as to obtain the change scheme of the change software.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, and when the at least one instruction is executed by a processor, the method for automatically generating a change plan according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: include: Memory and processor; Wherein, the memory is used to store programs; The processor calls the program and is used to execute the method for automatically generating a change plan as described in any one of claims 1-7.

Images