System version monitoring method, device, electronic device and readable storage medium
Through the system version monitoring method, including acceptance testing and dependency analysis, calculation of operation impact values, the problem of low accuracy of traditional version monitoring is solved, the accurate impact evaluation and processing of business system version is achieved, and the accuracy of version monitoring is improved. and efficiency.
Patent Information
- Application Number
- CN202111544160.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-16
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-12-16
AI Technical Summary
Traditional version monitoring methods rely on manual judgment, with low accuracy, and cannot effectively monitor the impact of business system version on the associated system, resulting in inaccurate version monitoring.
Through the system version monitoring method, the business subsystem to be updated in the business system is obtained, acceptance tests are carried out, dependencies are identified, the operation impact value is calculated, and whether it has an impact on the dependency subsystem is determined based on the impact value is determined, and early warning or blocking are performed.
It improves the accuracy of business system version monitoring, ensures that version updates will not affect the normal operation of the dependent subsystem, and enhances the accuracy and efficiency of version acceptance.
Smart Images

Figure CN114237689B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of research and development management, and in particular to a system version monitoring method, device, electronic equipment and computer-readable storage medium. Background Art
[0002] Version monitoring refers to the process of having the current version of the business system to be released be accepted by operations personnel before release.
[0003] Traditional version monitoring is to manually monitor whether the current version of the business system has an impact on the associated systems of the business system, such as whether the current version of the order query subsystem in the order payment system will have an impact on the order generation subsystem in the order payment system, and analyze, judge, warn and block the impact level. Manual monitoring generally only generates a warning when the current version of the business system has a high impact level on the associated systems of the business system, making version monitoring inaccurate. Summary of the invention
[0004] The present invention provides a system version monitoring method, device, electronic device and readable storage medium, the main purpose of which is to solve the problem of low accuracy in business system version monitoring.
[0005] To achieve the above object, the present invention provides a system version monitoring method, comprising:
[0006] Obtaining a business subsystem to be updated in the business system, and identifying the current version of the business subsystem;
[0007] Perform acceptance testing on the current version of the business subsystem;
[0008] When the current version passes the acceptance test, a subsystem having a dependency relationship with the business subsystem is identified from the business system to obtain a dependent subsystem of the business subsystem;
[0009] Calculating the operation impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value;
[0010] If the current version of the business subsystem will affect the system operation of the dependent subsystem, then an early warning process is performed on the current version of the business subsystem in the dependent subsystem;
[0011] If the current version of the business subsystem will not affect the system operation of the dependent subsystem, the current version of the business subsystem is shielded in the dependent subsystem.
[0012] Optionally, the acceptance test of the current version of the business subsystem includes:
[0013] Extracting the overall source code of the current version of the business subsystem;
[0014] According to the functional requirements of the pre-configured business subsystem, checking whether the source code block corresponding to the functional requirements exists in the overall source code;
[0015] When the source code block corresponding to any one of the functional requirements does not exist in the overall source code, the acceptance test is terminated;
[0016] When the source code block corresponding to the functional requirement exists in the overall source code, compile the overall source code to detect whether there is a compilation error in the overall source code;
[0017] When there is a compilation error in the overall source code, the acceptance test is terminated;
[0018] When there is no compilation error in the overall source code, the acceptance test is completed.
[0019] Optionally, the identifying a subsystem having a dependency relationship with the business subsystem from the business system to obtain a dependent subsystem of the business subsystem includes:
[0020] Obtaining a subsystem dependency tree preset in the business system;
[0021] Querying the dependency tree node corresponding to the business subsystem in the subsystem dependency tree;
[0022] The subsystem cluster in the dependency tree node is extracted to obtain the dependent subsystem.
[0023] Optionally, calculating the operation impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value, includes:
[0024] Calculate the operational impact value of the current version on the dependent subsystem using a pre-built operational impact value calculation formula;
[0025] When the operation impact value is in the preset first impact degree interval or the preset second impact degree interval, it is determined that the current version of the business subsystem will affect the system operation of the dependent subsystem;
[0026] When the operation impact value is within a preset third impact degree interval, it is determined that the current version of the business subsystem will not affect the system operation of the dependent subsystem.
[0027] Optionally, the calculating the operation impact value of the current version on the dependent subsystem by using a pre-built operation impact value calculation formula includes:
[0028] The operation impact value of the current version on the dependent subsystem is calculated using the following operation impact value calculation formula:
[0029]
[0030] Where n is the total number of version information items in the current version, x i is the i-th version information item in the version information item, p(x i ) is the probability that the ith version information item affects the system operation, and H is the operation impact value.
[0031] Optionally, the performing early warning processing on the current version of the business subsystem in the dependent subsystem includes:
[0032] According to the operation impact value, determining the impact level interval in which the operation impact value is located;
[0033] When the operation impact value is within a preset first impact level interval, the current version is warned to execute the first interval, and the user is reminded to handle the problem in a preset first manner;
[0034] When the operation impact value is within a preset second impact level interval, the current version executes a second interval warning, and reminds the user to handle the problem in a preset second manner.
[0035] Optionally, the method further comprises: determining, according to the operation impact value, a range of impact levels in which the operation impact value is located;
[0036] When the operation impact value is in the preset third impact level interval, it is determined that the current version of the business subsystem will not affect the system operation of the dependent subsystem, and the current version is shielded in the third interval, and the current version of the business subsystem is shielded in the dependent subsystem.
[0037] In order to solve the above problem, the present invention further provides a system version monitoring device, the device comprising:
[0038] The system version acceptance test module is used to obtain the business subsystem to be updated in the business system, and identify the current version of the business subsystem; perform acceptance test on the business subsystem of the current version; when the current version passes the acceptance test, identify the subsystem that has a dependency relationship with the business subsystem from the business system, and obtain the dependent subsystem of the business subsystem;
[0039] An operation impact value calculation module, used to calculate the operation impact value of the current version on the dependent subsystem, and determine whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value;
[0040] A system version warning module, used to determine if the current version of the business subsystem will affect the system operation of the dependent subsystem, and then perform warning processing on the current version of the business subsystem in the dependent subsystem;
[0041] The system version shielding module is used to determine if the current version of the business subsystem will not affect the system operation of the dependent subsystem, and then shield the current version of the business subsystem in the dependent subsystem.
[0042] In order to solve the above problem, the present invention further provides an electronic device, the electronic device comprising:
[0043] at least one processor; and,
[0044] a memory communicatively connected to the at least one processor; wherein,
[0045] The memory stores a computer program that can be executed by the at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the system version monitoring method described above.
[0046] In order to solve the above problem, the present invention also provides a computer-readable storage medium, in which at least one computer program is stored. The at least one computer program is executed by a processor in an electronic device to implement the system version monitoring method described above.
[0047] The embodiment of the present invention uses the current version of the business subsystem that has passed the version acceptance test as the updated version of the corresponding business subsystem in the business system, wherein the version acceptance test can effectively eliminate the operation problems of a single business subsystem, and in addition, according to the dependency relationship of each business subsystem in the business system, the dependent subsystem related to the business subsystem is extracted, and the operation detection of the dependent subsystem with strong correlation with the business subsystem can be realized, and then the pre-constructed operation impact value calculation formula is used to calculate the size of the operation impact value of the current version of the business subsystem on the dependent subsystem, and the current version of the business subsystem is shielded or warned according to the impact level interval where the operation impact value is located, wherein the current version is shielded or warned according to the different impact level intervals where the operation impact value is located, so that the version shielding or warning of the current version of the business subsystem can be made more accurate. This solution can improve the accuracy of business system version monitoring. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] Figure 1 A flowchart of a system version monitoring method provided by an embodiment of the present invention;
[0049] Figure 2 A functional module diagram of a system version monitoring device provided by an embodiment of the present invention;
[0050] Figure 3 A schematic diagram of the structure of an electronic device for implementing the system version monitoring method provided by an embodiment of the present invention.
[0051] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0052] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.
[0053] The embodiment of the present application provides a system version monitoring method. The execution subject of the system version monitoring method includes but is not limited to at least one of the electronic devices such as a server, a terminal, etc. that can be configured to execute the method provided by the embodiment of the present application. In other words, the system version monitoring method can be executed by software or hardware installed on a terminal device or a server device, and the software can be a blockchain platform. The server includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, etc. The server can be an independent server, or it can be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms.
[0054] Reference Figure 1 FIG. 1 is a flow chart of a system version monitoring method provided by an embodiment of the present invention. In this embodiment, the system version monitoring method includes:
[0055] S1. Obtain a business subsystem to be updated in a business system, and identify the current version of the business subsystem;
[0056] In the embodiment of the present invention, the business system may be a business system corresponding to each business line in the enterprise. For example, in the field of property insurance business, the business system may be a business system related to property insurance.
[0057] In an embodiment of the present invention, the current version may be a pending acceptance version of the business subsystem obtained after developers perform functional updates to the business subsystem based on user requirements and functional requirements, wherein the pending acceptance version of the business subsystem includes the version time, version contact person, and grayscale test results of the business subsystem.
[0058] In detail, the embodiment of the present invention responds to an update request of a business subsystem to be updated in the business system, and obtains the current version of the business subsystem according to the update request.
[0059] S2. Perform acceptance testing on the business subsystem of the current version;
[0060] In the embodiment of the present invention, the acceptance test may be a series of acceptance test processes such as risk scanning, functional integrity acceptance, and grayscale testing that need to be performed on the business system before the business system is put into use. For example, in the embodiment of the present invention, when the business subsystem passes the acceptance test, it indicates that the user can use the business subsystem to complete the established functions and tasks.
[0061] In detail, the acceptance test of the current version of the business subsystem includes:
[0062] Extracting the overall source code of the current version of the business subsystem;
[0063] According to the functional requirements of the pre-configured business subsystem, checking whether the source code block corresponding to the functional requirements exists in the overall source code;
[0064] When the source code block corresponding to any one of the functional requirements does not exist in the overall source code, the acceptance test is terminated;
[0065] When all source code blocks corresponding to the functional requirements exist in the overall source code, compile the overall source code to detect whether there is a compilation error in the overall source code;
[0066] When there is a compilation error in the overall source code, the acceptance test is terminated;
[0067] When there is no compilation error in the overall source code, the acceptance test is completed.
[0068] In the embodiment of the present invention, the overall source code may be the code of the entire business system written when the business system is developed, and the overall source code may be obtained by business development personnel.
[0069] S3. When the current version passes the acceptance test, identify a subsystem in the business system that has a dependency relationship with the business subsystem, and obtain a dependent subsystem of the business subsystem;
[0070] In the embodiment of the present invention, the dependency relationship may be an influence relationship in which changes in each part of the business system will affect the whole. For example, in the sales business system, the order payment subsystem and the order generation subsystem complement each other, and there is a dependency relationship between the two subsystems. When the order generation subsystem generates a functional error, it will affect the order payment subsystem.
[0071] In the embodiment of the present invention, a subsystem cluster that has mutual influence with the current subsystem can be obtained according to the dependency relationship. For example, in an order payment system, the order payment system, the order query system and the order generation system are complementary to each other, and the order generation system and the order query system can be the dependent subsystems.
[0072] In detail, when the current version passes the acceptance test, a subsystem having a dependency relationship with the business subsystem is identified from the business system to obtain the dependent subsystem of the business subsystem, including:
[0073] Obtaining a subsystem dependency tree preset in the business system;
[0074] Querying the dependency tree node corresponding to the business subsystem in the subsystem dependency tree;
[0075] The subsystem cluster in the dependency tree node is extracted to obtain the dependent subsystem.
[0076] In the embodiment of the present invention, the subsystem dependency tree can be a tree structure constructed by business subsystems with different functions according to dependency relationships. For example, the transaction item selection system, transaction item order generation system, transaction payment system and transaction query system in the transaction system can generate a transaction system dependency tree according to the subordinate relationship. The structure of the transaction system dependency tree can be represented by the following structure:
[0077]
[0078] In the above embodiment, each subsystem existing in the transaction system dependency tree can represent the dependent subsystem.
[0079] S4, calculating the operation impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value;
[0080] In the embodiment of the present invention, the operation impact value may be a value for evaluating the degree of mutual impact of the current version of the business subsystem on each subsystem in the dependent subsystem.
[0081] In detail, the embodiment of the present invention calculates the operational impact value of the current version on the dependent subsystem through a pre-constructed operational impact value calculation formula; when the operational impact value is in a preset first impact degree interval or a preset second impact degree interval, it is judged that the current version of the business subsystem will affect the system operation of the dependent subsystem; when the operational impact value is in a preset third impact degree interval, it is judged that the current version of the business subsystem will not affect the system operation of the dependent subsystem.
[0082] In an embodiment of the present invention, three impact level intervals are preset to determine the impact level of the operation impact value; the preset first impact level interval is the first warning interval, which indicates that the operation impact value is of extremely important impact level; the preset second impact level interval is the second warning interval, which indicates that the operation impact value is of major impact level, and both of the above warnings require users to handle them as soon as possible; the preset third impact level interval is the third shielding interval, which indicates that the operation impact value has no impact, and the current version of the business subsystem is shielded in the dependent subsystem, wherein the first warning interval, the second warning interval and the third warning interval are different intervals, which are independent of each other and do not affect each other.
[0083] In the embodiment of the present invention, the shielding process may be to allow the current version of the business subsystem that does not affect the normal operation of the dependent subsystem and the overall business system to directly pass the version acceptance test without issuing a warning indication to the user.
[0084] Furthermore, in one embodiment of the present invention, the first warning interval may be represented by red, the second warning interval may be represented by orange, and the third shielding interval may be represented by yellow.
[0085] It should be understood that the red, orange and yellow colors only indicate the degree of impact and are not limited to the above three colors.
[0086] Furthermore, the operation impact value of the current version on the dependent subsystem is calculated using the following operation impact value calculation formula:
[0087]
[0088] Where n is the total number of version information items in the current version, x i is the i-th version information item in the version information item, p(x i ) is the probability that the i-th item in the version information item affects the operation of the dependent subsystem, and H is the operation impact value.
[0089] S5. If the current version of the business subsystem will affect the system operation of the dependent subsystem, then an early warning process is performed on the current version of the business subsystem in the dependent subsystem;
[0090] In detail, an embodiment of the present invention determines the impact level interval of the operation impact value based on the operation impact value; when the operation impact value is in the preset first impact level interval, the current version executes the first interval warning, and reminds the user to handle it in a preset first way; when the operation impact value is in the preset second impact level interval, the current version executes the second interval warning, and reminds the user to handle it in a preset second way.
[0091] In an embodiment of the present invention, the preset first method may be a voice warning. For example, during the version acceptance process, a warning sound is issued through a preset voice paging link or device to remind a preset user to handle the situation. The preset second method may be a text warning, for example, including but not limited to sending a warning signal text to a preset user for processing via a paging address or link.
[0092] S6. If the current version of the business subsystem does not affect the system operation of the dependent subsystem, the current version of the business subsystem is shielded in the dependent subsystem.
[0093] In an embodiment of the present invention, when the operation impact value is in the preset third impact level interval, it is determined that the current version of the business subsystem will not affect the system operation of the dependent subsystem, and the current version is shielded in the yellow interval, and the current version of the business subsystem is shielded in the dependent subsystem.
[0094] The embodiment of the present invention uses the current version of the business subsystem that has passed the version acceptance test as the updated version of the business system, wherein the version acceptance test can effectively eliminate the operation problems of a single business subsystem. In addition, according to the dependency relationship of each business subsystem in the business system, the dependent subsystem related to the business subsystem is extracted, and the size of the operation impact value is calculated using a pre-built operation impact value calculation formula, and the current version of the business subsystem is shielded or warned according to the impact level interval of the size of the operation impact value. This solution can speed up the process of version acceptance and improve the accuracy of business system version monitoring.
[0095] like Figure 2 , which is a functional module diagram of a system version monitoring device provided by an embodiment of the present invention.
[0096] The system version monitoring device 100 of the present invention can be installed in an electronic device. According to the functions to be implemented, the system version monitoring device 100 can include a system version acceptance test module 101, an operation impact value calculation module 102, a system version early warning module 103 and a system version shielding module 104. The module of the present invention can also be called a unit, which refers to a series of computer program segments that can be executed by an electronic device processor and can complete fixed functions, which are stored in the memory of the electronic device.
[0097] In this embodiment, the functions of each module / unit are as follows:
[0098] The system version acceptance test module 101 is used to obtain a business subsystem to be updated in the business system, and identify the current version of the business subsystem; perform acceptance testing on the business subsystem of the current version; when the current version passes the acceptance test, identify a subsystem in the business system that has a dependency relationship with the business subsystem, and obtain the dependent subsystem of the business subsystem;
[0099] In the embodiment of the present invention, the business system may be a business system corresponding to each business line in the enterprise. For example, in the field of property insurance business, the business system may be a business system related to property insurance.
[0100] In an embodiment of the present invention, the current version may be a pending acceptance version of the business subsystem obtained after developers perform functional updates to the business subsystem based on user requirements and functional requirements, wherein the pending acceptance version of the business subsystem includes the version time, version contact person, and grayscale test results of the business subsystem.
[0101] In detail, the embodiment of the present invention responds to an update request of a business subsystem to be updated in the business system, and obtains the current version of the business subsystem according to the update request.
[0102] In the embodiment of the present invention, the acceptance test may be a series of acceptance test processes such as risk scanning, functional integrity acceptance, and grayscale testing that need to be performed on the business system before the business system is put into use. For example, in the embodiment of the present invention, when the business subsystem passes the acceptance test, it indicates that the user can use the business subsystem to complete the established functions and tasks.
[0103] In detail, the acceptance test of the current version of the business subsystem includes:
[0104] Extracting the overall source code of the current version of the business subsystem;
[0105] According to the functional requirements of the pre-configured business subsystem, checking whether the source code block corresponding to the functional requirements exists in the overall source code;
[0106] When the source code block corresponding to any one of the functional requirements does not exist in the overall source code, the acceptance test is terminated;
[0107] When all source code blocks corresponding to the functional requirements exist in the overall source code, compile the overall source code to detect whether there is a compilation error in the overall source code;
[0108] When there is a compilation error in the overall source code, the acceptance test is terminated;
[0109] When there is no compilation error in the overall source code, the acceptance test is completed.
[0110] In the embodiment of the present invention, the overall source code may be the code of the entire business system written when the business system is developed, and the overall source code may be obtained by business development personnel.
[0111] In the embodiment of the present invention, the dependency relationship may be an influence relationship in which changes in each part of the business system will affect the whole. For example, in the sales business system, the order payment subsystem and the order generation subsystem complement each other, and there is a dependency relationship between the two subsystems. When the order generation subsystem generates a functional error, it will affect the order payment subsystem.
[0112] In the embodiment of the present invention, a subsystem cluster that has mutual influence with the current subsystem can be obtained according to the dependency relationship. For example, in an order payment system, the order payment system, the order query system and the order generation system are complementary to each other, and the order generation system and the order query system can be the dependent subsystems.
[0113] In detail, when the current version passes the acceptance test, a subsystem having a dependency relationship with the business subsystem is identified from the business system to obtain the dependent subsystem of the business subsystem, including:
[0114] Obtaining a subsystem dependency tree preset in the business system;
[0115] Querying the dependency tree node corresponding to the business subsystem in the subsystem dependency tree;
[0116] The subsystem cluster in the dependency tree node is extracted to obtain the dependent subsystem.
[0117] In the embodiment of the present invention, the subsystem dependency tree can be a tree structure constructed by business subsystems with different functions according to dependency relationships. For example, the transaction item selection system, transaction item order generation system, transaction payment system and transaction query system in the transaction system can generate a transaction system dependency tree according to the subordinate relationship. The structure of the transaction system dependency tree can be represented by the following structure:
[0118]
[0119] In the above embodiment, each subsystem existing in the transaction system dependency tree can represent the dependent subsystem.
[0120] The operation impact value calculation module 102 is used to calculate the operation impact value of the current version on the dependent subsystem, and determine whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value;
[0121] In the embodiment of the present invention, the operation impact value may be a value for evaluating the degree of mutual impact of the current version of the business subsystem on each subsystem in the dependent subsystem.
[0122] In detail, the embodiment of the present invention calculates the operational impact value of the current version on the dependent subsystem through a pre-constructed operational impact value calculation formula; when the operational impact value is in a preset first impact degree interval or a preset second impact degree interval, it is judged that the current version of the business subsystem will affect the system operation of the dependent subsystem; when the operational impact value is in a preset third impact degree interval, it is judged that the current version of the business subsystem will not affect the system operation of the dependent subsystem.
[0123] In an embodiment of the present invention, three impact level intervals are preset to determine the impact level of the operation impact value; the preset first impact level interval is the first warning interval, which indicates that the operation impact value is of extremely important impact level; the preset second impact level interval is the second warning interval, which indicates that the operation impact value is of major impact level, and both of the above warnings require users to handle them as soon as possible; the preset third impact level interval is the third shielding interval, which indicates that the operation impact value has no impact, and the current version of the business subsystem is shielded in the dependent subsystem, wherein the first warning interval, the second warning interval and the third warning interval are different intervals, which are independent of each other and do not affect each other.
[0124] In the embodiment of the present invention, the shielding process may be to allow the current version of the business subsystem that does not affect the normal operation of the dependent subsystem and the overall business system to directly pass the version acceptance test without issuing a warning indication to the user.
[0125] Furthermore, in one embodiment of the present invention, the first warning interval may be represented by red, the second warning interval may be represented by orange, and the third shielding interval may be represented by yellow.
[0126] It should be understood that the red, orange and yellow colors only indicate the degree of impact and are not limited to the above three colors.
[0127] Furthermore, the operation impact value of the current version on the dependent subsystem is calculated using the following operation impact value calculation formula:
[0128]
[0129] Where n is the total number of version information items in the current version, x i is the i-th version information item in the version information item, p(x i ) is the probability that the i-th item in the version information item affects the operation of the dependent subsystem, and H is the operation impact value.
[0130] The system version warning module 103 is used to determine if the current version of the business subsystem will affect the system operation of the dependent subsystem, and then perform warning processing on the current version of the business subsystem in the dependent subsystem;
[0131] In detail, an embodiment of the present invention determines the impact level interval of the operation impact value based on the operation impact value; when the operation impact value is in the preset first impact level interval, the current version executes the first interval warning, and reminds the user to handle it in a preset first way; when the operation impact value is in the preset second impact level interval, the current version executes the second interval warning, and reminds the user to handle it in a preset second way.
[0132] In an embodiment of the present invention, the preset first method may be a voice warning. For example, during the version acceptance process, a warning sound is issued through a preset voice paging link or device to remind a preset user to handle the situation. The preset second method may be a text warning, for example, including but not limited to sending a warning signal text to a preset user for processing via a paging address or link.
[0133] The system version shielding module 104 is used to determine if the current version of the business subsystem will not affect the system operation of the dependent subsystem, and then shield the current version of the business subsystem in the dependent subsystem.
[0134] In an embodiment of the present invention, when the operation impact value is in the preset third impact level interval, it is determined that the current version of the business subsystem will not affect the system operation of the dependent subsystem, and the current version is shielded in the yellow interval, and the current version of the business subsystem is shielded in the dependent subsystem.
[0135] The embodiment of the present invention uses the current version of the business subsystem that has passed the version acceptance test as the updated version of the business system, wherein the version acceptance test can effectively eliminate the operation problems of a single business subsystem. In addition, according to the dependency relationship of each business subsystem in the business system, the dependent subsystem related to the business subsystem is extracted, and the size of the operation impact value is calculated using a pre-built operation impact value calculation formula, and the current version of the business subsystem is shielded or warned according to the impact level interval of the size of the operation impact value. This solution can speed up the process of version acceptance and improve the accuracy of business system version monitoring.
[0136] like Figure 3 FIG. 1 is a schematic diagram of the structure of an electronic device for implementing a system version monitoring method provided by an embodiment of the present invention.
[0137] The electronic device 1 may include a processor 10 , a memory 11 , a communication bus 12 , and a communication interface 13 , and may also include a computer program stored in the memory 11 and executable on the processor 10 , such as a system version monitoring program.
[0138] In some embodiments, the processor 10 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips. The processor 10 is the control core (ControlUnit) of the electronic device, and uses various interfaces and lines to connect various components of the entire electronic device, and executes or executes programs or modules stored in the memory 11 (for example, executing a system version monitoring program, etc.), and calls data stored in the memory 11 to execute various functions of the electronic device and process data.
[0139] The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a mobile hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a magnetic memory, a disk, an optical disk, etc. In some embodiments, the memory 11 may be an internal storage unit of an electronic device, such as a mobile hard disk of the electronic device. In other embodiments, the memory 11 may also be an external storage device of an electronic device, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Further, the memory 11 may also include both an internal storage unit of the electronic device and an external storage device. The memory 11 can be used not only to store application software and various types of data installed in the electronic device, such as the code of the system version monitoring program, but also to temporarily store data that has been output or is to be output.
[0140] The communication bus 12 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. The bus is configured to realize connection and communication between the memory 11 and at least one processor 10, etc.
[0141] The communication interface 13 is used for communication between the above-mentioned electronic device and other devices, including a network interface and a user interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is generally used to establish a communication connection between the electronic device and other electronic devices. The user interface may be a display (Display), an input unit (such as a keyboard (Keyboard)), and optionally, the user interface may also be a standard wired interface, a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device, etc. Among them, the display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the electronic device and to display a visual user interface.
[0142] Figure 3 Only an electronic device with components is shown, and those skilled in the art will understand that Figure 3The structure shown does not constitute a limitation on the electronic device 1, and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.
[0143] For example, although not shown, the electronic device may also include a power source (such as a battery) for supplying power to each component. Preferably, the power source may be logically connected to the at least one processor 10 through a power management device, so that the power management device can realize functions such as charging management, discharging management, and power consumption management. The power source may also include one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device may also include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.
[0144] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited to this structure.
[0145] The system version monitoring program stored in the memory 11 of the electronic device 1 is a combination of multiple instructions. When running in the processor 10, it can achieve:
[0146] Obtaining a business subsystem to be updated in the business system, and identifying the current version of the business subsystem;
[0147] Perform acceptance testing on the current version of the business subsystem;
[0148] When the current version passes the acceptance test, a subsystem having a dependency relationship with the business subsystem is identified from the business system to obtain a dependent subsystem of the business subsystem;
[0149] Calculating the operation impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value;
[0150] If the current version of the business subsystem will affect the system operation of the dependent subsystem, then an early warning process is performed on the current version of the business subsystem in the dependent subsystem;
[0151] If the current version of the business subsystem will not affect the system operation of the dependent subsystem, the current version of the business subsystem is shielded in the dependent subsystem.
[0152] Specifically, the specific implementation method of the processor 10 for the above instructions can refer to the description of the relevant steps in the corresponding embodiment of the accompanying drawings, which will not be repeated here.
[0153] Furthermore, if the module / unit integrated in the electronic device 1 is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile. For example, the computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, and a read-only memory (ROM).
[0154] The present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor of an electronic device, the computer program can implement:
[0155] Obtaining a business subsystem to be updated in the business system, and identifying the current version of the business subsystem;
[0156] Perform acceptance testing on the current version of the business subsystem;
[0157] When the current version passes the acceptance test, a subsystem having a dependency relationship with the business subsystem is identified from the business system to obtain a dependent subsystem of the business subsystem;
[0158] Calculating the operation impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value;
[0159] If the current version of the business subsystem will affect the system operation of the dependent subsystem, then an early warning process is performed on the current version of the business subsystem in the dependent subsystem;
[0160] If the current version of the business subsystem will not affect the system operation of the dependent subsystem, the current version of the business subsystem is shielded in the dependent subsystem.
[0161] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.
[0162] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0163] In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional modules.
[0164] It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.
[0165] Therefore, no matter from which point of view, the embodiments should be regarded as illustrative and non-restrictive, and the scope of the present invention is limited by the appended claims rather than the above description, so it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims are included in the present invention. Any attached figure mark in the claims should not be regarded as limiting the claims involved.
[0166] The blockchain referred to in this invention is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.
[0167] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.
[0168] In addition, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the system claim can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.
[0169] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solution of the present invention can be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present invention.
Claims
1. A system version monitoring method, characterized in that: The method comprises: Obtaining a business subsystem to be updated in the business system, and identifying the current version of the business subsystem; Perform acceptance testing on the current version of the business subsystem; When the current version passes the acceptance test, a subsystem having a dependency relationship with the business subsystem is identified from the business system to obtain a dependent subsystem of the business subsystem; Calculating the operation impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value; If the current version of the business subsystem will affect the system operation of the dependent subsystem, then an early warning process is performed on the current version of the business subsystem in the dependent subsystem; If the current version of the business subsystem will not affect the system operation of the dependent subsystem, shielding the current version of the business subsystem in the dependent subsystem; The acceptance test of the business subsystem of the current version includes: extracting the overall source code of the business subsystem of the current version; checking whether the source code blocks corresponding to the functional requirements of the pre-configured business subsystem exist in the overall source code according to the functional requirements; when any source code block corresponding to the functional requirements does not exist in the overall source code, the acceptance test is terminated; when all the source code blocks corresponding to the functional requirements exist in the overall source code, compiling the overall source code and detecting whether there are compilation errors in the overall source code; when there are compilation errors in the overall source code, the acceptance test is terminated; when there are no compilation errors in the overall source code, it is determined that the current version passes the acceptance test; The calculating the operational impact value of the current version on the dependent subsystem, and judging whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operational impact value, comprises: calculating the operational impact value of the current version on the dependent subsystem using a pre-built operational impact value calculation formula; when the operational impact value is in a preset first impact degree interval or a preset second impact degree interval, judging that the current version of the business subsystem will affect the system operation of the dependent subsystem; and when the operational impact value is in a preset third impact degree interval, judging that the current version of the business subsystem will not affect the system operation of the dependent subsystem.
2. The system version monitoring method according to claim 1, characterized in that: The step of identifying a subsystem having a dependency relationship with the business subsystem from the business system to obtain a dependent subsystem of the business subsystem includes: Obtaining a subsystem dependency tree preset in the business system; Querying the dependency tree node corresponding to the business subsystem in the subsystem dependency tree; The subsystem cluster in the dependency tree node is extracted to obtain the dependent subsystem.
3. The system version monitoring method according to claim 1, characterized in that: The calculating the operation impact value of the current version on the dependent subsystem by using the pre-built operation impact value calculation formula includes: The operation impact value of the current version on the dependent subsystem is calculated using the following operation impact value calculation formula: ; in, is the total number of version information items in the current version, The version information item Item version information item, The version information item The probability that the term affects the operation of the dependent subsystem, is the operation impact value.
4. The system version monitoring method according to claim 1, characterized in that: The performing early warning processing on the current version of the business subsystem in the dependent subsystem includes: According to the operation impact value, determining the impact level interval in which the operation impact value is located; When the operation impact value is within a preset first impact level interval, the current version is warned to execute the first interval, and the user is reminded to handle the problem in a preset first manner; When the operation impact value is within a preset second impact level interval, the current version executes a second interval warning, and reminds the user to handle the problem in a preset second manner.
5. The system version monitoring method according to claim 4, characterized in that: If the current version of the business subsystem does not affect the system operation of the dependent subsystem, shielding the current version of the business subsystem in the dependent subsystem includes: When the operation impact value is in the preset third impact level interval, it is determined that the current version of the business subsystem does not affect the system operation of the dependent subsystem, and the current version of the business subsystem is shielded in the dependent subsystem.
6. A system version monitoring device, used to implement the system version monitoring method according to any one of claims 1 to 5, characterized in that: The device comprises: The system version acceptance test module is used to obtain the business subsystem to be updated in the business system, and identify the current version of the business subsystem; perform acceptance test on the business subsystem of the current version; when the current version passes the acceptance test, identify the subsystem that has a dependency relationship with the business subsystem from the business system, and obtain the dependent subsystem of the business subsystem; An operation impact value calculation module, used to calculate the operation impact value of the current version on the dependent subsystem, and determine whether the current version of the business subsystem will affect the system operation of the dependent subsystem according to the operation impact value; A system version warning module, used to determine if the current version of the business subsystem will affect the system operation of the dependent subsystem, and then perform warning processing on the current version of the business subsystem in the dependent subsystem; The system version shielding module is used to determine if the current version of the business subsystem will not affect the system operation of the dependent subsystem, and then shield the current version of the business subsystem in the dependent subsystem.
7. An electronic device, characterized in that: The electronic device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the system version monitoring method as described in any one of claims 1 to 5.
8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the system version monitoring method according to any one of claims 1 to 5 is implemented.
