System change processing method and device

Abstract

The invention discloses a system change processing method and device, and relates to the technical field of information management. A specific embodiment of the method comprises the steps of receiving a change application and a change file for a target system, and determining a target auditing node for auditing according to feature information in the change application; if the audit is passed, determining a change type according to the content in the change file, and determining a change list template corresponding to the change type; obtaining a field in the change list template, extracting a field value corresponding to the field from the change application and the change file, inputting the field value into the change list template, and generating a change list; and determining the change classification to which the change type belongs, sending the change list to the corresponding change processing node for auditing, extracting operation steps related to change execution from the change list after the auditing is passed, and executing the change operation on the target system. According to the implementation mode, multi-role cooperative auditing and multi-level auditing are achieved, the efficiency and quality of change management are remarkably improved, and smooth proceeding of the system change process is ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of information management, and in particular to a system change processing method and device. Background Art

[0002] As enterprise information systems become increasingly complex, the need for system changes and upgrades is increasing. Traditional system change management processes often use a single-line communication and single review mechanism, which has many shortcomings, such as low review efficiency, concentrated risks, and insufficient reviews, which can easily lead to production accidents and system instability. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a system change processing method and device, which can at least solve the problems of low audit efficiency, concentrated risks and insufficient review in the traditional system change management process in the prior art.

[0004] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present invention, a system change processing method is provided, including: receiving a change application and a change file for a target system transmitted by a system manager, determining a target review node according to characteristic information in the change application, and sending the change application to the target review node for review; in response to a pass in the review result, determining a change type according to the content in the change file, and determining a change order template corresponding to the change type from a preset change order template library; obtaining fields in the change order template, extracting field values ​​corresponding to the fields from the change application and the change file, and inputting the field values ​​into the change order template to generate a change order; determining a change category to which the change type belongs, and sending the change order to a change processing node corresponding to the change category for review, and in response to a pass in the review result, extracting operation steps related to executing the change from the change order to execute the change operation on the target system.

[0005] Optionally, a change application is generated based on system change information. The system change information and change files are set by the system administrator according to change requirements, and the change requirements are set by the system user. The process of setting the system change information and change files is as follows: the receiving system administrator selects the target system from all associated systems, and the receiving system administrator selects the version of the target system for this change from the version repository; the change application interface is displayed, and the system change information and uploaded change files entered by the receiving system administrator in the change application interface are received.

[0006] Optionally, determining the target review node based on the characteristic information in the change application includes: in response to the characteristic information including a version number and operation and maintenance information, determining a version review node and an operation and maintenance review node; wherein the operation and maintenance review node is located after and adjacent to the version review node; sending the change application to the target review node for review includes: sending the change application to the version review node for version review, and in response to the version review result being passed, sending the change application and the change file to the operation and maintenance review node for operation and maintenance review.

[0007] Optionally, the sending of the change order to the change processing node corresponding to the change classification for review includes: submitting the change order to the first-level change processing node for review, and when the review result is passed and the change classification is a standard change, determining the review result to be passed; when the review result is passed and the change classification is an emergency change, submitting the change order to the second-level emergency change processing node to obtain the review result; when the review result is passed and the change classification is a regular change or a major change, submitting the change order to the second-level regular change and major change processing node to obtain the review result.

[0008] Optionally, after executing the change operation on the target system, the method further includes: recording the change operation log, submitting the change operation log and the operation steps to the change review node for review; in response to the review result being passed, performing performance verification on the changed target system, and if the verification result is passed, closing the change order; if the verification result is failed, using the rollback plan in the change order to roll back the changed target system to the target system before the change.

[0009] Optionally, the method further includes: determining a change processing sequence and change processing content, and assembling the change processing content according to the change processing sequence to generate a change process record.

[0010] To achieve the above-mentioned purpose, according to another aspect of an embodiment of the present invention, a system change processing device is provided, including: an audit module, which is used to receive a change application and a change file for a target system transmitted by a system manager, determine a target audit node according to characteristic information in the change application, and send the change application to the target audit node for audit; a change order module, which is used to determine a change type according to the content in the change file in response to a pass in the audit result, determine a change order template corresponding to the change type from a preset change order template library; obtain fields in the change order template, extract field values ​​corresponding to the fields from the change application and the change file, and input the field values ​​into the change order template to generate a change order; an implementation module, which is used to determine the change category to which the change type belongs, send the change order to a change processing node corresponding to the change category for audit, and extract operation steps related to executing the change from the change order in response to a pass in the audit result, so as to execute the change operation on the target system.

[0011] Optionally, a change application is generated based on system change information. The system change information and change files are set by the system administrator according to change requirements, and the change requirements are set by the system user. The process of setting the system change information and change files is as follows: the receiving system administrator selects the target system from all associated systems, and the receiving system administrator selects the version of the target system for this change from the version repository; the change application interface is displayed, and the system change information and uploaded change files entered by the receiving system administrator in the change application interface are received.

[0012] Optionally, the review module is used to: determine the version review node and the operation and maintenance review node in response to characteristic information including a version number and operation and maintenance information; wherein the operation and maintenance review node is located after and adjacent to the version review node; send the change application to the version review node for version review, and in response to the version review result being passed, send the change application and the change file to the operation and maintenance review node for operation and maintenance review.

[0013] Optionally, the implementation module is used to: submit the change order to the first-level change processing node for review, and if the review result is passed and the change classification is a standard change, determine that the review result is passed; if the review result is passed and the change classification is an emergency change, submit the change order to the second-level emergency change processing node to obtain the review result; if the review result is passed and the change classification is a regular change or a major change, submit the change order to the second-level regular change and major change processing node to obtain the review result.

[0014] Optionally, the device also includes a review module, which is used to: record the change operation log, submit the change operation log and operation steps to the change review node for review; in response to the review result being passed, perform performance verification on the changed target system, and if the verification result is passed, close the change order; if the verification result is failed, use the rollback plan in the change order to roll back the changed target system to the target system before the change.

[0015] Optionally, the device further comprises a recording module, which is used to: determine a change processing sequence and change processing content, and assemble the change processing content according to the change processing sequence to generate a change process record.

[0016] To achieve the above objective, according to another aspect of an embodiment of the present invention, a system change processing electronic device is provided.

[0017] The electronic device of an embodiment of the present invention includes: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement any of the system change processing methods described above.

[0018] To achieve the above objective, according to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, any of the above-mentioned system change processing methods is implemented.

[0019] To achieve the above object, according to another aspect of an embodiment of the present invention, a computer program product is provided. A computer program product of an embodiment of the present invention includes a computer program, and when the program is executed by a processor, the system change processing method provided by the embodiment of the present invention is implemented.

[0020] According to the solution provided by the present invention, an embodiment of the above invention has the following advantages or beneficial effects: by constructing a change management method based on role collaboration, multi-role collaborative review and multi-level review process are realized, ensuring that changes can undergo detailed review at different levels and different roles, thereby improving the accuracy, efficiency and security of the review, and effectively avoiding the risk of production accidents caused by insufficient review.

[0021] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0023] Figure 1is a main flow chart of a system change processing method according to an embodiment of the present invention;

[0024] Figure 2 is a flowchart of an optional system change processing method according to an embodiment of the present invention;

[0025] Figure 3 is a flowchart of a specific system change processing method according to an embodiment of the present invention;

[0026] Figure 4 is a schematic diagram of main modules of a system change processing device according to an embodiment of the present invention;

[0027] Figure 5 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0028] Figure 6 It is a schematic diagram of the structure of a computer system of a mobile device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0030] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0031] In the absence of conflict, the embodiments and features of the embodiments of the present invention can be combined with each other. The acquisition, transmission, storage, use, and processing of data in the technical solution of the present invention are in compliance with the relevant provisions of national laws and regulations, and are used for legal and reasonable purposes, and are not shared, disclosed, or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities.

[0032] For user information, necessary measures should be taken to prevent illegal access to such personal information data, ensure that persons who have access to personal information data comply with relevant laws and regulations, and ensure the security of user personal information. Once such user personal information data is no longer needed, risks should be minimized by limiting or even prohibiting data collection and / or deleting data. When applicable, including in certain relevant applications, protect user privacy by de-identifying data, such as by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the specific address level), controlling how data is stored, and / or other methods of de-identification.

[0033] Change management process: a management mechanism to ensure that the IT system can still operate normally, safely and efficiently after the change. It mainly includes: change request submission, change assessment, change order submission, change approval, change implementation and verification, change review, and change closure. Change management is a key link to ensure stability and security during system updates, maintenance and upgrades.

[0034] The existing change management process usually adopts a more traditional single-line communication and single review mechanism: 1) Requirements: The developer or project team proposes the change requirements, which are usually submitted in the form of documents to a single person or team responsible for review. 2) Preliminary review: The designated reviewer conducts a preliminary review of the change requirements to evaluate the necessity and feasibility of the change. 3) Review decision: The reviewer makes a decision to approve or reject the change based on the preliminary review results. 4) Change implementation: If the change is approved, the developer executes the change operation. 5) Result recording: After the change is implemented, the change results are recorded for subsequent reference.

[0035] The existing change methods have the following shortcomings: 1) Single communication path: The change process requires different positions to evaluate the change content from multiple perspectives to reduce the risk of change. The existing change requirements and review process are mainly carried out through a single communication channel, lacking the participation and collaboration of multiple roles. 2) High audit risk: The audit power is concentrated in the hands of a few people, which may lead to a single audit perspective and increase the risk of insufficient review. 3) Low audit efficiency: The audit process may involve multiple departments or levels, but there is a lack of effective coordination mechanism, resulting in low audit efficiency. 4) Insufficient transparency and traceability: The records of the change process may not be detailed enough, making it difficult to track the complete history of the change and the allocation of responsibilities.

[0036] The present invention belongs to the field of information technology, and in particular to system change management. In order to improve the efficiency and security of change management and reduce the risk of production accidents caused by insufficient review, the present invention proposes a change management method based on role collaboration. By introducing multi-role collaborative review and multi-level approval mechanism, the method optimizes the change management process, significantly improves the approval efficiency and accuracy, and enhances the security and effectiveness of change management.

[0037] See also Figure 1 , which shows a main flow chart of a system change processing method provided by an embodiment of the present invention, including the following steps:

[0038] S101: receiving a change application and a change file for a target system transmitted by a system manager, determining a target review node according to characteristic information in the change application, and sending the change application to the target review node for review;

[0039] S102: In response to the audit result being passed, determining the change type according to the content in the change file, and determining a change order template corresponding to the change type from a preset change order template library;

[0040] S103: Obtaining fields in the change order template, extracting field values ​​corresponding to the fields from the change application and the change file, and inputting the field values ​​into the change order template to generate a change order;

[0041] S104: Determine the change category to which the change type belongs, send the change order to the change processing node corresponding to the change category for review, and in response to the review result being passed, extract the operation steps related to executing the change from the change order to execute the change operation on the target system.

[0042] In the above implementation, this solution can be applied to a variety of system change management scenarios. For example, due to system vulnerabilities, the project team needs to fix the vulnerabilities and update the system version of the production environment. The system here refers to the business system that Party A (i.e., the system user) is using. The business system is customized and developed for Party A by Party B (i.e., the system manager) and needs to be maintained by Party B.

[0043] For step S101, when the system is abnormal or there is a new business demand, Party A can propose a change request to Party B. Party A can submit the change request through formal documents, emails or a dedicated demand management system to ensure that the information is clearly transmitted and recorded. After receiving the change request, Party B first needs to conduct a detailed analysis of the demand and evaluate the scope of impact, required resources and technical feasibility of the change. After completing the preliminary assessment, Party B should communicate with Party A to confirm the details of the demand, including priority, schedule and expected results. After confirming the demand, Party B needs to formulate a detailed change implementation plan, including but not limited to technical solutions, development cycle, test plan and online strategy. The change plan should be as detailed as possible so that both parties can clearly understand the timetable and key milestones of the entire change process. According to the change plan, Party B starts development work to fix vulnerabilities or implement new functions. During the development process, Party B should communicate with Party A on the progress regularly to ensure that Party A can keep up to date with the latest status of the project.

[0044] After the development is completed, Party B needs to conduct comprehensive testing to ensure that the new function or the repaired system can run normally without introducing new problems. This solution sets up a system change module for Party A. One Party B may serve multiple Party A. For example, Party B develops system X, and Party A ABC uses system X. Considering that Party A basically uses system X internally, a system change module can be built for each Party A, and the system change modules of different Party A are independent of each other. Party B can log in to Party A's system change module, or Party B goes to Party A's computer room and can log in or not. It only needs to store the version of system X to be released in Party A's version warehouse, and then manually select the version of system X. In the case of login, all systems deployed by Party B on Party A can be queried based on Party B's user name. This is because Party A may use multiple systems developed by Party B, so it is necessary to filter by user name to improve the screening efficiency.

[0045] Assume that the original version of system X is 0.1, and the changed version is 0.2. Party B selects version 0.2 of system X from Party A's version repository. Party B then clicks to start the change application interface to enter the system change information for version 0.2 of system X and upload the change file. System change information includes but is not limited to change time, version, configuration, and dependencies. This information is mainly entered or selected manually, such as change time: Party B selects a suitable change time based on Party A's business situation, usually during the off-peak period of business to reduce the impact. Version information: Clearly fill in the changed version number, such as 0.2. Configuration modification: List all configuration parameters that need to be modified and their specific values. Dependencies: List the dependent libraries or service versions required for the changed system X to ensure compatibility and stability.

[0046] System X is maintained by Party B. When the version of System X is updated, Party B, as the production applicant, submits a change application through Party A's system change module and submits it to Party A for review. After Party A obtains the change application, it can determine which review node the change application belongs to based on the characteristic information corresponding to the review node in the change application. For example, if the change application contains the "change object" field, such as "database structure" and "front-end interface", the "database structure" is automatically assigned to the "database administrator" for review, while the "front-end interface" is assigned to the "front-end development team leader" for review. For example, if the change application contains the "scope of impact" field, such as "only affects internal users" and "affects all users", the process can be simplified for "only affects internal users" and submitted directly to the "internal system administrator" for review, while the changes that "affect all users" must be reviewed and approved by the "senior project manager" and the "chief information security officer".

[0047] This solution can also consider feature information and operation and maintenance information. First, the change application is submitted to Party A's version review node for version review. The staff of the version review node here usually understands development knowledge, so they can be responsible for technical review of the change content. Version review is to ensure the quality, consistency and security of the code through some methods. After the review is passed, Party A's version review node will send the change application and change files to Party A's operation and maintenance review node for version, configuration, dependencies and other operation and maintenance reviews.

[0048] Among them, version review: confirm whether the changed version number (such as 0.2) complies with the established version plan, check the differences between versions, and ensure that the new version solves known problems or implements expected new functions. Configuration review: review all configuration modifications involved in the change to ensure that they comply with security standards and best practices, and confirm that configuration modifications will not cause system instability or other potential problems. Dependency review: check whether the external library or service version on which the new version depends is correct. Security review: conduct a security assessment of the changed content to ensure that no new security risks are introduced, including but not limited to code audits, security vulnerability scans, etc. Document review: confirm that the change document is complete, including change instructions, operation guides, rollback plans, etc. The document should be clear and easy to understand for subsequent maintenance and support. If there are any problems, they need to be returned to Party B for correction. Through the above steps, it can be ensured that the changes are fully considered and reviewed at the operation and maintenance level, thereby improving the success rate of the changes and the stability of the system.

[0049] For steps S102 and S103, after the Party A operation and maintenance review node passes the review, it can enter the next link, such as manually clicking to display the change order generation interface, or the system can respond to Party A's operation and maintenance review node selection or input of review pass information, automatically triggering the display of the change order generation interface to generate a change order based on the system change information.

[0050] The staff at the operation and maintenance review node or Party A automatically determines the change type based on the content in the change file, such as adding new functions, modifying functions, deleting functions, changing functions such as database structure modification, front-end interface adjustment, etc., which can be supplemented, changed, and deleted according to actual needs. Change files usually include detailed change descriptions, technical components involved, scope of change and other information. Here, text parsing tools or automated scripts can be used to extract key information, and then match the corresponding change type based on key information (such as "database structure modification" and "front-end interface adjustment"). For example, if the change file mentions "changes in the database table structure", it will match the "database structure modification" type.

[0051] This solution pre-sets a change order template library, which can store multiple change order templates written and reviewed by the change implementation personnel. Each change type corresponds to one or more change order templates. According to the determined change type, select the corresponding template from the change order template library. For example, the "database structure modification" type corresponds to the "database change order template". Each change order template contains multiple fields, such as "change description", "scope of impact", "urgency", etc. Therefore, it is necessary to extract the values ​​corresponding to the fields from the change application and change file. For example, the "change description" field can be extracted from the "change description" part of the change file. Then fill the extracted field value into the corresponding change order template, for example, fill the "change description" field value into the corresponding position in the change order template. To generate a change order.

[0052] Suppose there is a change application and a change file (actually, only the change file can be considered, because the change file is similar to the development document and is more comprehensive) as follows: 1. Change description: modify the field age of the database table user in the system to nullable; 2. Change scope: core functional module; 3. Impact scope: all users; 4. Urgency: medium. Extract keywords from "Modify the field age of the database table user to nullable" and match it to the change type of "Database structure modification". According to this type, select "Database change order template". The template includes the fields of change description, change scope, impact scope and urgency, so extract the field values ​​from it and enter the template. Through the above steps, the corresponding change order can be effectively generated according to the content of the change application and change file. After the change order is generated, the review information and operation information will be added to the change order during the circulation process.

[0053] Regarding step S104, the change type and change classification are different in concept, but they are closely related. The specific differences and connections between the two are as follows:

[0054] 1) Change type refers to the category of specific change operations, usually used to describe the specific content and technical details of the change. Common change types include: database structure modification, front-end interface adjustment, back-end logic update, security configuration change, network architecture adjustment;

[0055] 2) Change classification refers to the overall classification of changes or the classification at the management level, which is usually used to describe the scope of impact, importance and management process of changes. This plan mainly includes: Regular changes: changes implemented in non-important information systems and changes to important information systems with business impact of less than 30 minutes; the urgency level is "non-urgent". Standard changes: standardize changes so that they have standard implementation steps and have been successfully implemented and verified in the production environment, and are implemented manually or automatically without interrupting business; the urgency level is "non-urgent". Emergency changes: changes that must be implemented immediately to solve production incidents to ensure the normal operation of the information system or meet business needs. Emergency changes can be implemented outside the change window; the urgency level is the highest. Major changes: changes that affect important business in one (or more) business hours for 30 minutes (or more), or changes that have a greater potential impact on the availability, integrity and security of important business operations and important information systems; the urgency level is "non-urgent".

[0056] In actual applications, change types and change classifications are usually used in combination, forming a parent-child relationship. For example: Change type: database structure modification, belongs to change classification: emergency change. In this case, the priority and management process can be determined according to the change classification to ensure the efficiency and standardization of the change process. Different change classifications correspond to different change processing nodes and processes. For example, a first-level change processing node is set, and all change orders are first sent to the first-level change processing node. When the review result of the first-level change processing node is passed and the change classification is a standard change, the pass instruction is directly returned to the system change personnel. In the case of other types of change classifications, the change order needs to be sent to the second-level change processing node for processing, such as the second-level emergency change processing node, the second-level regular change, and the major change processing node, so as to obtain the review result.

[0057] After obtaining the change approval, key data related to the execution of the change needs to be extracted from the change order, preferably from the change document. This operation helps to ensure the accuracy and traceability of the change process. Assume that there is a change order as follows:

[0058] Change description: Modify the age field of the database table user to nullable

[0059] Change type: Database structure modification

[0060] Scope of change: Core functional modules

[0061] Impact: All users

[0062] Urgency: High

[0063] Change time: 2023-10-15 14:00

[0064] Person in charge: Zhang San

[0065] Rollback plan: If the change fails, restore the original database table structure

[0066] Test plan: Verify the changed functionality in the test environment

[0067] Risk Assessment: Changes may result in data loss

[0068] Related documents: Change file.pdf

[0069] The extracted operation steps include: 1. Log in to the database management system; 2. Back up the current database table user; 3. Modify the field age of the table user to nullable; 4. Verify the changed function in the test environment; 5. If the test passes, apply the change to the production environment; 6. If the test fails, restore the original database table structure.

[0070] According to the operation steps, perform the change operation on system X: 1. Log in to the database management system; 2. Execute the backup command to back up the current database table user; 3. Execute the SQL statement to modify the field age of the table user to nullable; 4. Deploy the changed database table in the test environment and verify whether the function is normal, such as creating test data, executing query operations, and checking whether the results are correct; 5. If the test passes, apply the change to the production environment and execute the same SQL statement in the production environment. If the test fails, restore the original database table structure. Through these specific operation steps, the accuracy and reliability of the change process can be ensured, thereby improving the success rate and security of the change.

[0071] Change the system X according to the specific change operation steps. The contents included in the change order are provided by the production applicant Party B. The "specific change time" needs to be changed according to the version day specified by Party A (such as Tuesday and Thursday every week) during the business trough period of the version day (usually after 9 pm, which is the business off-peak period). The production applicant needs to provide specific change implementation steps for the "operation steps"; the production applicant needs to provide some conditions that may arise during the implementation process for the "change risks"; the production applicant needs to provide a "verification plan" on how to verify whether the change is successful after the change is completed; the production applicant needs to provide a "rollback plan" on how to roll back to the previous version if there is a problem with the change.

[0072] Party A's change implementer performs the change operation on System X according to the operation steps at the above change time. The change implementers in this solution are all Party A's operation and maintenance personnel. Party A stipulates that all changes can only be performed by Party A's operation and maintenance personnel, and the content of all change orders shall be provided by the production applicant. This solution determines the change processing sequence and change processing content, assembles the change processing content according to the change processing sequence, and generates a change process record, which solves the existing problem that "the record of the change process may not be detailed enough, making it difficult to track the complete history of the change and the allocation of responsibilities".

[0073] The method provided in the above embodiment clarifies the responsibilities of the system user and the system manager, ensures the accurate communication of change requirements and the accurate generation of system change information; reduces the risks caused by insufficient review through multi-level review, and improves the quality of change applications; determines the change type according to the change document, and then determines the change classification to automatically determine the change processing node, realizes the automation and standardization of the process, reduces manual errors, and improves the review efficiency. Perform the change operation according to the operating steps in the change order to ensure the consistency and accuracy of the change process. Through the above-mentioned clear responsibilities, structured processes, automated processing, strict review and detailed records, the efficiency and safety of change management are effectively improved, and the risk of production accidents is reduced.

[0074] See also Figure 2 , shows a schematic flow chart of an optional system change processing method according to an embodiment of the present invention, including the following steps:

[0075] S201: Record the change operation log, and submit the change operation log and operation steps to the change review node for review;

[0076] S202: In response to the review result being passed, a performance verification is performed on the target system after the change, and if the verification result is passed, the change order is closed;

[0077] S203: When the verification result is a failure, the rollback plan in the change order is used to roll back the changed target system to the target system before the change.

[0078] In the above implementation, after obtaining the change approval, the change implementer of Party A performs the change operation on System X according to the specific change operation steps, and the secondary person in charge of the system (i.e. the staff of the review node) reviews all operations to ensure that all operations are correct. Here, a change operation log can be generated during the change process of System X to record the operation content, and then the change operation log and operation steps are sent to the secondary person in charge for review.

[0079] If the review is passed, business verification and technical verification are carried out. Business verification: confirm whether the change meets the business needs and expected effects, and whether it has a positive impact on the business process and user experience. Let the business personnel of Party A use the system normally to determine whether it meets their workflow and needs. Technical verification: observe whether the system has downtime, observe the system's detection indicators, and whether its stability and performance have declined. After passing the verification, the change order can be closed. At this point, the entire change process for System X is over. However, if the verification fails, you need to use the rollback plan in the change order to roll back to the previous version 0.1.

[0080] In addition, in order to solve the problem that the existing technical change process records may not be detailed enough and it is difficult to track the complete history of the change and the allocation of responsibilities, this solution records the review order, review content, processing order and processing content, and verification content during the entire change process of system X to generate an audit process record. This operation can ensure that each change operation has a detailed operation record, including operation time, operator, operation content, etc. The audit process records should be properly preserved and support on-demand query to facilitate subsequent audits and problem tracing. This solution can also record the status of the change order, such as under review, under implementation, under review, under verification, and rolled back. It can also provide a visual representation of the audit process so that Party A personnel can view the current processing progress.

[0081] In order to improve the security and reliability of change implementation, the method provided in the above embodiment records the specific content of each step of the operation in detail during the change implementation process, including but not limited to the configuration and parameter modification before and after the change. A two-person review mechanism is set up during the change implementation stage. After the change operation is completed, the secondary person in charge will review and confirm to ensure the correctness and completeness of the change operation. In addition, the operation log recording function is implemented to facilitate subsequent review and problem tracing. Through these measures, the traceability and correctness of the change operation can be ensured, the risks caused by operational errors can be reduced, and the overall quality and security of change management can be improved.

[0082] See also Figure 3 , shows a schematic flow chart of a specific system change processing method according to an embodiment of the present invention, comprising the following steps:

[0083] 1. Party A proposes a change request for the target system and sends the change request to Party B;

[0084] 2. Party B stores the new version of the target system in Party A's version warehouse, selects the target system and the new version, enters the system change information such as change time, version, configuration, dependencies, etc. in the change application interface, and uploads the change file;

[0085] 3. After Party A receives the system change information and change files, if the system change information includes the version number, it will send the system change information to the version review node (such as the development supervisor) for version review;

[0086] 4. The version review node conducts a technical review of the system change information. After the review is passed, if the system change information includes operation and maintenance information, the system change information and change files will be submitted to the operation and maintenance review node (such as the application manager) for operation and maintenance review;

[0087] 5. The operation and maintenance review node conducts an audit of the version, configuration, dependencies and other aspects of operation and maintenance. After the audit is passed, the change type is automatically determined based on the content in the change file, and the change order template corresponding to the change type is determined from the preset change order template library;

[0088] 6. Get the fields in the change order template, extract the field values ​​corresponding to the fields from the change application and change file, and enter the field values ​​into the change order template to generate the change order. Information such as version, configuration, and dependencies can be used by all reviewers. Maybe everyone only needs part of the information and only needs to review the information within their own responsibilities according to their role positioning.

[0089] Therefore, this solution also developed a role-based access control (RBAC, full name Role-Based Access Control) system, which can implement role management functions on the platform, including role creation, permission allocation and access control. The platform can configure corresponding audit permissions and operation interfaces for different roles to ensure that users can only access corresponding functions and data. The user refers to all people who use the system, who can be Party A or Party B, and different permissions are assigned according to the positioning of different people.

[0090] 7. The operation and maintenance review node submits the change order to Party A's first-level change processing node (such as the operation and maintenance team leader). Party A's operation and maintenance team leader reviews the detailed change content such as the time, operation steps, change risks, verification plan, and rollback plan of the specific change, and directly agrees to make the change or submits it to the next stage of review based on the change classification;

[0091] 8. When the change is classified as an emergency change, the second-level emergency change processing node (such as the center manager) needs to give a review opinion; when it is a regular change and a major change, it needs to go through the second-level regular change and major change processing node (such as CAB) review meeting to give a review opinion to decide whether it can be implemented. In the field of IT service management, CAB usually refers to the Change Approval Board, which is a group responsible for evaluating, approving or rejecting change requests. This group ensures that the changes comply with the organization's service management strategy and service level agreement (SLA) and minimize the impact on the production environment. Both Party A and Party B must participate in the CAB review meeting. During the review process, Party A and Party B can ask questions, request additional materials or feedback in real time. This instant interaction function is usually not available in existing technologies.

[0092] 9. If the review opinion is passed, the change approval is returned to Party A's operation and maintenance personnel, who extract the change operation steps from the change order and perform the change operation on the target system used by Party A; the secondary person in charge of the system (i.e. the change review node) reviews all operations to ensure that all operations are correct;

[0093] 10. After executing all the change operations, business verification and technical verification are carried out. After passing the verification, the change order can be closed. At this point, the entire change process is over. If the verification fails, it is necessary to roll back to the target system version before the change;

[0094] 11. After verification succeeds or fails, determine the audit order and audit content of each node, generate an audit chain based on the node order, add the audit content to the audit chain, and obtain the audit process record.

[0095] The main drawback of the traditional method is the lack of multi-role collaboration and multi-level approval mechanism, which limits the comprehensiveness and efficiency of the approval process. This invention significantly improves the change management process through the design of multi-role and multi-level review process, operation and maintenance review and feedback mechanism, change application and review, and life cycle management of change orders:

[0096] 1. Role coordination mechanism: including version review node, operation and maintenance review node, change processing node, and review node. Different change types have different change classifications, and the corresponding change processing nodes and review processes are also different. This method changes the traditional model of a single reviewer being responsible. By allowing different roles to participate in the change management process, the approval process is diversified and comprehensive, and the comprehensiveness and accuracy of decision-making are improved.

[0097] 2. Multi-level review process: ensure that change applications can be carefully reviewed by different levels and roles, thereby improving the accuracy and security of approval and reducing the risk of single approval;

[0098] 3. Interactive collaboration platform: For the review process, an interactive collaboration platform is established to achieve instant information sharing and communication, improve approval efficiency, reduce communication costs, and enhance process transparency. It provides a change application interface, a change form filling and submission and review interface, and achieves real-time update of the review status to ensure the continuity of the review process.

[0099] 4. Change application and audit traceability. The system change application submitted by Party B can be quickly reviewed by Party A internally, and the audit process and audit history of the change application can be recorded to provide a visual representation of the audit process. A two-person review mechanism is set up for change implementation to ensure the correctness of the change operation, which is an improvement over the single-person execution of the change operation in the existing technology. After the change is completed, business verification and technical verification are carried out to ensure the effectiveness of the change, which is a link that may be overlooked in the existing technology. Recording the audit process records enables instant information sharing and communication, improves approval efficiency, reduces communication costs, and enhances the transparency of the process.

[0100] 5. The operation and maintenance review and feedback mechanism clarifies the responsible persons at each stage of the change management process through role setting, improving the traceability and responsibility clarity of the process. During the review process, problems and work order circulation are recorded to ensure that review opinions can be responded to and processed in a timely manner.

[0101] 6. Lifecycle management of change orders: From change application to change completion, the entire life cycle of change orders is managed, including recording, approval, implementation and verification steps, which improves the systematicness and standardization of the process.

[0102] See also Figure 4 , which shows a schematic diagram of main modules of a system change processing device 400 provided in an embodiment of the present invention, including:

[0103] The review module 401 is used to receive the change application and change file of the target system transmitted by the system manager, determine the target review node according to the characteristic information in the change application, and send the change application to the target review node for review;

[0104] The change order module 402 is used to determine the change type according to the content in the change file in response to the audit result being passed, and determine the change order template corresponding to the change type from the preset change order template library; obtain the field in the change order template, extract the field value corresponding to the field from the change application and the change file, and input the field value into the change order template to generate a change order;

[0105] Implementation module 403 is used to determine the change category to which the change type belongs, and send the change order to the change processing node corresponding to the change category for review. In response to the review result being passed, the operation steps related to executing the change are extracted from the change order to execute the change operation on the target system.

[0106] In the implementation device of the present invention, the change application is generated based on the system change information. The system change information and the change file are set by the system management party according to the change requirements, and the change requirements are set by the system user. The setting process of the system change information and the change file is as follows:

[0107] The receiving system manager selects the target system from all associated systems, and the receiving system manager selects the version of the target system for this change from the version repository;

[0108] The change application interface is displayed to receive the system change information entered by the system administrator and the uploaded change files.

[0109] In the implementation device of the present invention, the audit module 401 is used to:

[0110] In response to the feature information including the version number and the operation and maintenance information, a version review node and an operation and maintenance review node are determined; wherein the operation and maintenance review node is located after and adjacent to the version review node;

[0111] The change application is sent to the version review node for version review. In response to the version review result being passed, the change application and change file are sent to the operation and maintenance review node for operation and maintenance review.

[0112] In the implementation device of the present invention, the implementation module 403 is used to:

[0113] Submit the change order to the first-level change processing node for review. If the review result is passed and the change classification is a standard change, the review result is determined to be passed;

[0114] If the review result is passed and the change is classified as an emergency change, the change order is submitted to the secondary emergency change processing node to obtain the review result;

[0115] If the audit result is passed and the change is classified as a regular change or a major change, the change order will be submitted to the second-level regular change and major change processing node to obtain the audit result.

[0116] The implementation device of the present invention also includes a review module, which is used to:

[0117] Record the change operation log, and submit the change operation log and operation steps to the change review node for review;

[0118] In response to the review result being passed, the performance of the target system after the change is verified, and if the verification result is passed, the change order is closed;

[0119] If the verification result is a failure, use the rollback plan in the change order to roll back the changed target system to the target system before the change.

[0120] The implementation device of the present invention also includes a recording module, which is used to:

[0121] Determine the change processing sequence and change processing content, and assemble the change processing content according to the change processing sequence to generate a change process record.

[0122] In addition, the specific implementation content of the device described in the embodiment of the present invention has been described in detail in the method described above, so the repeated content will not be described again here.

[0123] Figure 5 An exemplary system architecture 500 to which embodiments of the present invention may be applied is shown, including terminal devices 501 , 502 , 503 , a network 504 and a server 505 (only an example).

[0124] Terminal devices 501, 502, 503 can be various electronic devices with display screens and supporting web browsing, and various communication client applications are installed. Users can use terminal devices 501, 502, 503 to interact with server 505 through network 504 to receive or send messages, etc.

[0125] The network 504 is used to provide a medium for communication links between the terminal devices 501, 502, 503 and the server 505. The network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables.

[0126] The server 505 may be a server that provides various services, such as a backend management server that provides support for shopping websites browsed by users using terminal devices 501, 502, and 503 (only as an example). The backend management server may analyze and process the received data such as product information query requests, and feed back the processing results (such as target push information, product information - only as an example) to the terminal device. It should be noted that the method provided in the embodiment of the present invention is generally executed by the server 505, and accordingly, the device is generally set in the server 505.

[0127] It should be understood that Figure 5 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0128] Reference below Figure 6, which shows a schematic diagram of the structure of a computer system 600 of a terminal device suitable for implementing an embodiment of the present invention. Figure 6 The terminal 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 invention.

[0129] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 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 part 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0130] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage section 608 as needed.

[0131] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a 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 the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present invention are executed.

[0132] It should be noted that the computer-readable medium shown in the present invention 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 invention, 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 invention, 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 electromagnetic signals, optical signals, 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: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0133] 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 invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two 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 box in the block diagram or flow chart, and the combination of the boxes in the block diagram 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.

[0134] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor. For example, they may be described as follows: a processor includes an audit module, a change order module, and an implementation module. The names of these modules do not, in some cases, constitute limitations on the modules themselves. For example, the implementation module may also be described as a "processing module."

[0135] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device executes any of the above system change processing methods.

[0136] The computer program product of the present invention includes a computer program, and when the computer program is executed by a processor, the system change processing method in the embodiment of the present invention is implemented.

[0137] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A system change processing method, characterized in that: include: Receive the change application and change file for the target system transmitted by the system manager, determine the target review node according to the characteristic information in the change application, and send the change application to the target review node for review; In response to the audit result being passed, determining the change type according to the content in the change file, and determining a change order template corresponding to the change type from a preset change order template library; Get the fields in the change order template, extract the field values ​​corresponding to the fields from the change request and the change document, and input the field values ​​into the change order template to generate the change order; Determine the change category to which the change type belongs, send the change order to the change processing node corresponding to the change category for review, and in response to the review result being passed, extract the operation steps related to executing the change from the change order to execute the change operation on the target system.

2. The method according to claim 1, characterized in that Change applications are generated based on system change information. System change information and change files are set by the system manager according to change requirements, and change requirements are set by the system user. The process of setting system change information and change files is as follows: The receiving system manager selects the target system from all associated systems, and the receiving system manager selects the version of the target system for this change from the version repository; The change application interface is displayed to receive the system change information entered by the system administrator and the uploaded change files.

3. The method according to claim 1, characterized in that Determining the target review node according to the characteristic information in the change application includes: In response to the feature information including the version number and the operation and maintenance information, a version review node and an operation and maintenance review node are determined; wherein the operation and maintenance review node is located after and adjacent to the version review node; The sending of the change application to the target review node for review includes: The change application is sent to the version review node for version review. In response to the version review result being passed, the change application and change file are sent to the operation and maintenance review node for operation and maintenance review.

4. The method according to claim 1, characterized in that: The sending of the change order to the change processing node corresponding to the change classification for review includes: Submit the change order to the first-level change processing node for review. If the review result is passed and the change classification is a standard change, the review result is determined to be passed; If the review result is passed and the change is classified as an emergency change, the change order is submitted to the secondary emergency change processing node to obtain the review result; If the audit result is passed and the change is classified as a regular change or a major change, the change order will be submitted to the second-level regular change and major change processing node to obtain the audit result.

5. The method according to claim 1, characterized in that After performing the change operation on the target system, the method further includes: Record the change operation log, and submit the change operation log and operation steps to the change review node for review; In response to the review result being passed, the performance of the target system after the change is verified, and if the verification result is passed, the change order is closed; If the verification result is a failure, use the rollback plan in the change order to roll back the changed target system to the target system before the change.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Determine the change processing sequence and change processing content, and assemble the change processing content according to the change processing sequence to generate a change process record.

7. A system change processing device, characterized in that: include: The audit module is used to receive the change application and change file of the target system transmitted by the system manager, determine the target audit node according to the characteristic information in the change application, and send the change application to the target audit node for audit; A change order module, for determining a change type according to the content in the change file in response to a review result of passing, and determining a change order template corresponding to the change type from a preset change order template library; Get the fields in the change order template, extract the field values ​​corresponding to the fields from the change request and the change document, and input the field values ​​into the change order template to generate the change order; The implementation module is used to determine the change category to which the change type belongs, and send the change order to the change processing node corresponding to the change category for review. In response to the review result being passed, the operation steps related to executing the change are extracted from the change order to execute the change operation on the target system.

8. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

9. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images