CN114237689A - System version monitoring method and device, electronic equipment and readable storage medium - Google Patents

System version monitoring method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN114237689A
CN114237689A CN202111544160.9A CN202111544160A CN114237689A CN 114237689 A CN114237689 A CN 114237689A CN 202111544160 A CN202111544160 A CN 202111544160A CN 114237689 A CN114237689 A CN 114237689A
Authority
CN
China
Prior art keywords
subsystem
current version
version
service
dependent
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111544160.9A
Other languages
Chinese (zh)
Inventor
张波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Property and Casualty Insurance Company of China Ltd
Original Assignee
Ping An Property and Casualty Insurance Company of China Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Property and Casualty Insurance Company of China Ltd filed Critical Ping An Property and Casualty Insurance Company of China Ltd
Priority to CN202111544160.9A priority Critical patent/CN114237689A/en
Publication of CN114237689A publication Critical patent/CN114237689A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/368—Test management for test version control, e.g. updating test cases to a new software version

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention relates to a research and development management technology, and discloses a system version monitoring method, which comprises the following steps: acquiring a current version of a service subsystem to be subjected to version updating; performing acceptance test on the current version; when the acceptance test is passed, identifying a subsystem having a dependency relationship with the service subsystem to obtain a dependent subsystem; calculating the operation influence value of the current version on the dependent subsystem, and judging whether the current version of the service subsystem can influence the system operation of the dependent subsystem according to the operation influence value; if so, performing early warning processing on the current version of the service subsystem in the dependent subsystem; and if not, shielding the current version of the business subsystem in the dependent subsystem. In addition, the invention also relates to a block chain technology, and the service subsystem can be stored in a node of the block chain. The invention also provides a system version monitoring device, electronic equipment and a storage medium. The invention can improve the accuracy of the version monitoring of the service system.

Description

System version monitoring method and device, electronic equipment and readable storage medium
Technical Field
The present invention relates to the field of research and development management technologies, and in particular, to a method and an apparatus for monitoring system versions, an electronic device, and a computer-readable storage medium.
Background
The version monitoring refers to a process of checking and accepting the current version of the service system to be released by an operator before the release.
In the traditional version monitoring, whether the current version of a service system affects an associated system of the service system is monitored manually, for example, whether the current version of an order query subsystem in an order payment system affects an order generation subsystem in the order payment system is monitored, and the level of the impact is analyzed, judged, early warned and shielded. Manual monitoring generally generates an early warning only when the current version of the business system has a high level of influence on the associated systems of the business system, so that version monitoring is not accurate enough.
Disclosure of Invention
The invention provides a system version monitoring method and device, electronic equipment and a readable storage medium, and mainly aims to solve the problem of low accuracy of service system version monitoring.
In order to achieve the above object, the present invention provides a system version monitoring method, which includes:
acquiring a service subsystem to be subjected to version updating in a service system, and identifying the current version of the service subsystem;
performing acceptance test on the service subsystem of the current version;
when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
calculating the operation influence value of the current version on the dependent subsystem, and judging whether the current version of the service subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
if the current version of the business subsystem can influence the system operation of the dependent subsystem, early warning processing is carried out on the current version of the business subsystem in the dependent subsystem;
and if the current version of the service subsystem does not influence the system operation of the dependent subsystem, shielding the current version of the service subsystem in the dependent subsystem.
Optionally, the performing an acceptance test on the service subsystem of the current version includes:
extracting the overall source code of the business subsystem of the current version;
according to the function requirement of a service subsystem configured in advance, checking whether a source code block corresponding to the function requirement exists in the total source code;
when the source code block corresponding to any one of the functional requirements does not exist in the overall source code, terminating the acceptance test;
when the source code block corresponding to the function requirement exists in the overall source code, compiling the overall source code, and detecting whether the overall source code has a compiling error;
when the overall source code has a compiling error, the acceptance test is terminated;
and when the overall source code has no compiling error, completing the acceptance test.
Optionally, the identifying, from the service system, a subsystem having a dependency relationship with the service subsystem to obtain a dependent subsystem of the service subsystem includes:
acquiring a subsystem dependency relationship tree preset in the service system;
querying a dependency relationship tree node corresponding to the service subsystem in the subsystem dependency relationship tree;
and extracting the subsystem cluster in the dependency tree node to obtain the dependency subsystem.
Optionally, the calculating an operation influence value of the current version on the dependent subsystem, and determining whether the current version of the service subsystem may influence the system operation of the dependent subsystem according to the operation influence value includes:
calculating the operation influence value of the current version on the dependent subsystem by using a pre-constructed calculation formula of the operation influence value;
when the operation influence value is in a preset first influence degree interval or a preset second influence degree interval, judging that the current version of the service subsystem can influence the system operation of the dependent subsystem;
and when the operation influence value is in a preset third influence degree interval, judging that the current version of the service subsystem does not influence the system operation of the dependent subsystem.
Optionally, the calculating, by using a pre-constructed calculation formula of the operation impact value, an operation impact value of the current version on the dependent subsystem includes:
calculating the operation influence value of the current version on the dependent subsystem by using the following calculation formula of the operation influence value:
Figure BDA0003415281460000031
wherein n is the total number of version information items in the current version, xiFor the i-th one of the version information items, p (x)i) And H is the operation influence value, wherein the operation influence value is the probability that the ith version information item influences the operation of the system.
Optionally, the performing, in the dependent subsystem, an early warning process on the current version of the business subsystem includes:
judging the influence degree grade interval of the operation influence value according to the operation influence value;
when the operation influence value is in a preset first influence degree grade interval, executing first interval early warning on the current version, and reminding a user to process according to a preset first mode;
and when the operation influence value is in a preset second influence degree grade interval, executing second interval early warning on the current version, and reminding a user to process according to a preset second mode.
Optionally, the method further includes, according to the operation influence value, determining an influence degree level interval where the operation influence value is located, where the method further includes:
and when the operation influence value is in a preset third influence degree grade interval, judging that the current version of the business subsystem does not influence the system operation of the dependent subsystem, executing third interval shielding on the current version, and shielding the current version of the business subsystem in the dependent subsystem.
In order to solve the above problem, the present invention further provides a system version monitoring apparatus, including:
the system version acceptance testing module is used for acquiring a service subsystem to be subjected to version updating in a service system and identifying the current version of the service subsystem; performing acceptance test on the service subsystem of the current version; when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
the operation influence value calculation module is used for calculating the operation influence value of the current version on the dependent subsystem and judging whether the current version of the business subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
the system version early warning module is used for judging whether the current version of the business subsystem can influence the system operation of the dependency subsystem or not, and carrying out early warning processing on the current version of the business subsystem in the dependency subsystem;
and the system version shielding module is used for judging that the current version of the business subsystem is shielded in the dependent subsystem if the current version of the business subsystem does not influence the system operation of the dependent subsystem.
In order to solve the above problem, the present invention also provides an electronic device, including:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the system version monitoring method described above.
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, and the at least one computer program is executed by a processor in an electronic device to implement the system version monitoring method described above.
The embodiment of the invention utilizes the current version of the service subsystem which passes the version acceptance test as the updated version of the corresponding service subsystem in the service system, wherein, the operation problem of a single service subsystem can be effectively eliminated through the version acceptance test, in addition, the dependent subsystem related to the service subsystem is extracted according to the dependency relationship of each service subsystem in the service system, the operation detection of the dependent subsystem with stronger correlation to the service subsystem can be realized, the operation influence value of the current version of the service subsystem on the dependent subsystem is calculated by utilizing the pre-constructed operation influence value calculation formula, and the version shielding or the version early warning is executed on the current version of the service subsystem through the influence degree grade interval of the operation influence value, wherein, according to the different influence degree grade intervals of the operation influence value, the version shielding or version early warning is carried out on the current version, so that the version shielding or version early warning of the current version of the service subsystem can be more accurate. The scheme can improve the accuracy of the version monitoring of the service system.
Drawings
Fig. 1 is a schematic flow chart of a system version monitoring method according to an embodiment of the present invention;
fig. 2 is a functional block diagram of a system version monitoring apparatus according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device for implementing the system version monitoring method according to an embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The embodiment of the 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 electronic devices such as a server and a terminal that can be configured to execute the method provided by the embodiments of the present application. In other words, the system version monitoring method may be performed by software or hardware installed in the terminal device or the server device, and the software may be a block chain platform. The server includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, and the like. The server may be an independent server, or may be a cloud server that provides basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like.
Fig. 1 is a schematic flow chart of a system version monitoring method according to an embodiment of the present invention. In this embodiment, the system version monitoring method includes:
s1, acquiring a service subsystem to be version-updated in the service system, and identifying the current version of the service subsystem;
in the embodiment of the present invention, the service system may be a service system corresponding to each service line in an enterprise. For example, in the area of venture services, the business system can be a business system related to venture aspects.
In the embodiment of the present invention, the current version may be a to-be-checked version of the service subsystem obtained after a developer updates the function of the service subsystem according to a user requirement and a function requirement, where the to-be-checked version of the service subsystem includes a version time, a version contact, a grayscale test result, and the like of the service subsystem.
In detail, the embodiment of the present invention obtains the current version of the service subsystem according to the update request by responding to the update request of the service subsystem to be version-updated in the service system.
S2, performing acceptance test on the service subsystem of the current version;
in the embodiment of the invention, the acceptance test can be a series of acceptance test processes such as risk scanning, functional integrity acceptance and gray level test and the like which are required to be carried out on the business system when the business system is put into use. For example, in the embodiment of the present invention, when the service subsystem passes the acceptance test, it indicates that the user can use the service subsystem to complete a predetermined function and task.
In detail, the performing an acceptance test on the current version of the business subsystem includes:
extracting the overall source code of the business subsystem of the current version;
according to the function requirement of a service subsystem configured in advance, checking whether a source code block corresponding to the function requirement exists in the total source code;
when the source code block corresponding to any one of the functional requirements does not exist in the overall source code, terminating the acceptance test;
when the source code blocks corresponding to the function requirements all exist in the overall source code, compiling the overall source code, and detecting whether the overall source code has a compiling error;
when the overall source code has a compiling error, the acceptance test is terminated;
and when the overall source code has no compiling error, completing the acceptance test.
In the embodiment of the invention, the overall source code can be the code of the whole business system written when the business system is developed, and the acquisition of the overall source code can be provided by a development business worker.
S3, when the current version passes the acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
in this embodiment of the present invention, the dependency relationship may be an influence relationship in which a change of each part in the service system affects the whole. For example, in a sales business system, an order sub-payment system and an order generation subsystem are complementary, and the two subsystems have a dependency relationship, so that when the order generation subsystem generates a function error, the order generation subsystem is affected.
In the embodiment of the invention, the subsystem cluster which has mutual influence with the current subsystem can be obtained according to the dependency relationship. For example, in the order payment system, the order query system and the order generation system are complementary, and the order generation system and the order query system may be the dependent subsystems.
In detail, when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system, and obtaining a dependent subsystem of the service subsystem includes:
acquiring a subsystem dependency relationship tree preset in the service system;
querying a dependency relationship tree node corresponding to the service subsystem in the subsystem dependency relationship tree;
and extracting the subsystem cluster in the dependency tree node to obtain the dependency subsystem.
In the embodiment of the present invention, the subsystem dependency tree may be a tree structure constructed by service subsystems with different functions according to a dependency relationship. For example, a trading item selection system, a trading item order generation system, a trading payment system and a trading query system existing in the trading system may generate a trading system dependency tree according to the dependency relationship, and the structure of the trading system dependency tree may be represented by the following structure:
Figure BDA0003415281460000071
in the above embodiment, each subsystem existing in the transaction system dependency tree may characterize the dependent subsystem.
S4, calculating the operation influence value of the current version on the dependent subsystem, and judging whether the current version of the service subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
in this embodiment of the present invention, the operation impact value may be a degree value for evaluating an interaction of the current version of the service subsystem with each subsystem in the dependent subsystem.
In detail, in the embodiment of the present invention, the operation influence value of the current version on the dependent subsystem is calculated through a pre-constructed calculation formula of the operation influence value; when the operation influence value is in a preset first influence degree interval or a preset second influence degree interval, judging that the current version of the service subsystem can influence the system operation of the dependent subsystem; and when the operation influence value is in a preset third influence degree interval, judging that the current version of the service subsystem does not influence the system operation of the dependent subsystem.
In the embodiment of the invention, three influence degree grade intervals are preset to judge the influence degree of the operation influence value; the preset first influence degree grade interval is a first early warning interval, and the operation influence value is represented as an extremely important influence degree; the preset second influence degree interval is a second early warning interval, the operation influence value is represented as a main influence degree, and the two kinds of early warning need to be processed as soon as possible by a user; and the preset third influence degree grade interval is a third shielding interval, the operation influence value is represented as no influence, and the current version of the service subsystem is shielded in the dependence subsystem, wherein the first early warning interval, the second early warning interval and the third early warning interval are different intervals, are mutually independent and do not influence each other.
In the embodiment of the invention, the shielding treatment can be that the current version of the service subsystem which does not influence the normal operation of the dependent subsystem and the whole service system directly passes the version acceptance test and does not carry out early warning indication on the user.
Further, 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.
It should be understood that the red, orange and yellow colors are only indicative of the degree of influence and are not limited to the three colors described above.
Further, the operation influence value of the current version on the dependent subsystem is calculated by using the following calculation formula of the operation influence value:
Figure BDA0003415281460000081
wherein n is the total number of version information items in the current version, xiFor the i-th one of the version information items, p (x)i) And H is the probability that the ith item in the version information item influences the operation of the dependent subsystem, and H is the operation influence value.
S5, if the current version of the business subsystem can affect the system operation of the dependent subsystem, early warning processing is carried out on the current version of the business subsystem in the dependent subsystem;
in detail, according to the operation influence value, the embodiment of the present invention determines an influence degree grade interval where the operation influence value is located; when the operation influence value is in a preset first influence degree grade interval, executing first interval early warning on the current version, and reminding a user to process according to a preset first mode; and when the operation influence value is in a preset second influence degree grade interval, executing second interval early warning on the current version, and reminding a user to process according to a preset second mode.
In the embodiment of the present invention, the preset first mode may be a voice warning, for example, in a version acceptance process, a preset voice paging link or device is used to send a warning sound to remind a preset user to perform processing, and the preset second mode may be a text warning, for example, including but not limited to sending a warning signal text to the preset user for processing through a paging address or link.
And S6, if the current version of the business subsystem does not influence the system operation of the dependent subsystem, shielding the current version of the business subsystem in the dependent subsystem.
In the embodiment of the present invention, when the operation influence value is in a preset third influence degree level interval, it is determined that the current version of the business subsystem does not influence the system operation of the dependent subsystem, yellow interval shielding is performed on the current version, and shielding processing is performed on the current version of the business subsystem in the dependent subsystem.
The embodiment of the invention uses the current version of the service subsystem which passes the version acceptance test as the updated version of the service system, wherein the version acceptance test can effectively eliminate the operation problem of a single service subsystem, in addition, the dependent subsystem related to the service subsystem is extracted according to the dependent relation of each service subsystem in the service system, the size of the operation influence value is calculated by using a pre-constructed operation influence value calculation formula, and the version shielding or version early warning operation is executed on the current version of the service subsystem through the influence degree grade interval in which the size of the operation influence value is positioned. The scheme can accelerate the process of checking and accepting the version and improve the accuracy of monitoring the version of the service system.
Fig. 2 is a functional block diagram of a system version monitoring apparatus according to an embodiment of the present invention.
The system version monitoring apparatus 100 according to the present invention may be installed in an electronic device. According to the implemented functions, the system version monitoring apparatus 100 may include a system version acceptance test module 101, an operation influence value calculation module 102, a system version early warning module 103, and a system version shielding module 104. The module of the present invention, which may also be referred to as a unit, refers to a series of computer program segments that can be executed by a processor of an electronic device and that can perform a fixed function, and that are stored in a memory of the electronic device.
In the present embodiment, the functions regarding the respective modules/units are as follows:
the system version acceptance test module 101 is configured to acquire a service subsystem to be version-updated in a service system, and identify a current version of the service subsystem; performing acceptance test on the service subsystem of the current version; when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
in the embodiment of the present invention, the service system may be a service system corresponding to each service line in an enterprise. For example, in the area of venture services, the business system can be a business system related to venture aspects.
In the embodiment of the present invention, the current version may be a to-be-checked version of the service subsystem obtained after a developer updates the function of the service subsystem according to a user requirement and a function requirement, where the to-be-checked version of the service subsystem includes a version time, a version contact, a grayscale test result, and the like of the service subsystem.
In detail, the embodiment of the present invention obtains the current version of the service subsystem according to the update request by responding to the update request of the service subsystem to be version-updated in the service system.
In the embodiment of the invention, the acceptance test can be a series of acceptance test processes such as risk scanning, functional integrity acceptance and gray level test and the like which are required to be carried out on the business system when the business system is put into use. For example, in the embodiment of the present invention, when the service subsystem passes the acceptance test, it indicates that the user can use the service subsystem to complete a predetermined function and task.
In detail, the performing an acceptance test on the current version of the business subsystem includes:
extracting the overall source code of the business subsystem of the current version;
according to the function requirement of a service subsystem configured in advance, checking whether a source code block corresponding to the function requirement exists in the total source code;
when the source code block corresponding to any one of the functional requirements does not exist in the overall source code, terminating the acceptance test;
when the source code blocks corresponding to the function requirements all exist in the overall source code, compiling the overall source code, and detecting whether the overall source code has a compiling error;
when the overall source code has a compiling error, the acceptance test is terminated;
and when the overall source code has no compiling error, completing the acceptance test.
In the embodiment of the invention, the overall source code can be the code of the whole business system written when the business system is developed, and the acquisition of the overall source code can be provided by a development business worker.
In this embodiment of the present invention, the dependency relationship may be an influence relationship in which a change of each part in the service system affects the whole. For example, in a sales business system, an order sub-payment system and an order generation subsystem are complementary, and the two subsystems have a dependency relationship, so that when the order generation subsystem generates a function error, the order generation subsystem is affected.
In the embodiment of the invention, the subsystem cluster which has mutual influence with the current subsystem can be obtained according to the dependency relationship. For example, in the order payment system, the order query system and the order generation system are complementary, and the order generation system and the order query system may be the dependent subsystems.
In detail, when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system, and obtaining a dependent subsystem of the service subsystem includes:
acquiring a subsystem dependency relationship tree preset in the service system;
querying a dependency relationship tree node corresponding to the service subsystem in the subsystem dependency relationship tree;
and extracting the subsystem cluster in the dependency tree node to obtain the dependency subsystem.
In the embodiment of the present invention, the subsystem dependency tree may be a tree structure constructed by service subsystems with different functions according to a dependency relationship. For example, a trading item selection system, a trading item order generation system, a trading payment system and a trading query system existing in the trading system may generate a trading system dependency tree according to the dependency relationship, and the structure of the trading system dependency tree may be represented by the following structure:
Figure BDA0003415281460000111
in the above embodiment, each subsystem existing in the transaction system dependency tree may characterize the dependent subsystem.
The operation influence value calculation module 102 is configured to calculate an operation influence value of the current version on the dependent subsystem, and determine whether the current version of the service subsystem affects system operation of the dependent subsystem according to the operation influence value;
in this embodiment of the present invention, the operation impact value may be a degree value for evaluating an interaction of the current version of the service subsystem with each subsystem in the dependent subsystem.
In detail, in the embodiment of the present invention, the operation influence value of the current version on the dependent subsystem is calculated through a pre-constructed calculation formula of the operation influence value; when the operation influence value is in a preset first influence degree interval or a preset second influence degree interval, judging that the current version of the service subsystem can influence the system operation of the dependent subsystem; and when the operation influence value is in a preset third influence degree interval, judging that the current version of the service subsystem does not influence the system operation of the dependent subsystem.
In the embodiment of the invention, three influence degree grade intervals are preset to judge the influence degree of the operation influence value; the preset first influence degree grade interval is a first early warning interval, and the operation influence value is represented as an extremely important influence degree; the preset second influence degree interval is a second early warning interval, the operation influence value is represented as a main influence degree, and the two kinds of early warning need to be processed as soon as possible by a user; and the preset third influence degree grade interval is a third shielding interval, the operation influence value is represented as no influence, and the current version of the service subsystem is shielded in the dependence subsystem, wherein the first early warning interval, the second early warning interval and the third early warning interval are different intervals, are mutually independent and do not influence each other.
In the embodiment of the invention, the shielding treatment can be that the current version of the service subsystem which does not influence the normal operation of the dependent subsystem and the whole service system directly passes the version acceptance test and does not carry out early warning indication on the user.
Further, 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.
It should be understood that the red, orange and yellow colors are only indicative of the degree of influence and are not limited to the three colors described above.
Further, the operation influence value of the current version on the dependent subsystem is calculated by using the following calculation formula of the operation influence value:
Figure BDA0003415281460000121
wherein n is the total number of version information items in the current version, xiFor the i-th one of the version information items, p (x)i) And H is the probability that the ith item in the version information item influences the operation of the dependent subsystem, and H is the operation influence value.
The system version early warning module 103 is configured to determine that, if the current version of the service subsystem may affect the system operation of the dependent subsystem, perform early warning processing on the current version of the service subsystem in the dependent subsystem;
in detail, according to the operation influence value, the embodiment of the present invention determines an influence degree grade interval where the operation influence value is located; when the operation influence value is in a preset first influence degree grade interval, executing first interval early warning on the current version, and reminding a user to process according to a preset first mode; and when the operation influence value is in a preset second influence degree grade interval, executing second interval early warning on the current version, and reminding a user to process according to a preset second mode.
In the embodiment of the present invention, the preset first mode may be a voice warning, for example, in a version acceptance process, a preset voice paging link or device is used to send a warning sound to remind a preset user to perform processing, and the preset second mode may be a text warning, for example, including but not limited to sending a warning signal text to the preset user for processing through a paging address or link.
The system version shielding module 104 is configured to determine that, if the current version of the service subsystem does not affect the system operation of the dependent subsystem, shield the current version of the service subsystem in the dependent subsystem.
In the embodiment of the present invention, when the operation influence value is in a preset third influence degree level interval, it is determined that the current version of the business subsystem does not influence the system operation of the dependent subsystem, yellow interval shielding is performed on the current version, and shielding processing is performed on the current version of the business subsystem in the dependent subsystem.
The embodiment of the invention uses the current version of the service subsystem which passes the version acceptance test as the updated version of the service system, wherein the version acceptance test can effectively eliminate the operation problem of a single service subsystem, in addition, the dependent subsystem related to the service subsystem is extracted according to the dependent relation of each service subsystem in the service system, the size of the operation influence value is calculated by using a pre-constructed operation influence value calculation formula, and the version shielding or version early warning operation is executed on the current version of the service subsystem through the influence degree grade interval in which the size of the operation influence value is positioned. The scheme can accelerate the process of checking and accepting the version and improve the accuracy of monitoring the version of the service system.
Fig. 3 is a schematic structural diagram of an electronic device for implementing a system version monitoring method according to an embodiment of the present invention.
The electronic device 1 may comprise a processor 10, a memory 11, a communication bus 12 and a communication interface 13, and may further comprise a computer program, such as a system version monitoring program, stored in the memory 11 and executable on the processor 10.
In some embodiments, the processor 10 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or may be composed of a plurality of integrated circuits packaged with the same function or different functions, and includes one or more Central Processing Units (CPUs), a microprocessor, a digital Processing chip, a graphics processor, a combination of various control chips, and the like. The processor 10 is a Control Unit (Control Unit) of the electronic device, connects various components of the electronic device by using various interfaces and lines, and executes various functions and processes data of the electronic device by running or executing programs or modules (e.g., executing a system version monitoring program, etc.) stored in the memory 11 and calling data stored in the memory 11.
The memory 11 includes at least one type of readable storage medium including flash memory, removable hard disks, multimedia cards, card-type memory (e.g., SD or DX memory, etc.), magnetic memory, magnetic disks, optical disks, etc. The memory 11 may in some embodiments be an internal storage unit of the electronic device, for example a removable hard disk of the electronic device. The memory 11 may also be an external storage device of the electronic device in other embodiments, such as a plug-in mobile hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device. Further, the memory 11 may also include both an internal storage unit and an external storage device of the electronic device. The memory 11 may be used not only to store application software installed in the electronic device and various types of data, such as codes of a system version monitoring program, etc., but also to temporarily store data that has been output or will be output.
The communication bus 12 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. The bus is arranged to enable connection communication between the memory 11 and at least one processor 10 or the like.
The communication interface 13 is used for communication between the electronic device and other devices, and includes a network interface and a user interface. Optionally, the network interface may include a wired interface and/or a wireless interface (e.g., WI-FI interface, bluetooth interface, etc.), which are typically 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 a standard wired interface, a wireless interface. Alternatively, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, or the like. The display, which may also be referred to as a display screen or display unit, is suitable, among other things, for displaying information processed in the electronic device and for displaying a visualized user interface.
Fig. 3 shows only an electronic device with components, and it will be understood by those skilled in the art that the structure shown in fig. 3 does not constitute a limitation of the electronic device 1, and may comprise fewer or more components than those shown, or some components may be combined, or a different arrangement of components.
For example, although not shown, the electronic device may further include a power supply (such as a battery) for supplying power to each component, and preferably, the power supply may be logically connected to the at least one processor 10 through a power management device, so that functions of charge management, discharge management, power consumption management and the like are realized through the power management device. The power supply may also include any component of one or more dc or ac power sources, recharging devices, power failure detection circuitry, power converters or inverters, power status indicators, and the like. The electronic device may further include various sensors, a bluetooth module, a Wi-Fi module, and the like, which are not described herein again.
It is to be understood that the described embodiments are for purposes of illustration only and that the scope of the appended claims is not limited to such structures.
The system version monitoring program stored in the memory 11 of the electronic device 1 is a combination of instructions, which when executed in the processor 10, can implement:
acquiring a service subsystem to be subjected to version updating in a service system, and identifying the current version of the service subsystem;
performing acceptance test on the service subsystem of the current version;
when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
calculating the operation influence value of the current version on the dependent subsystem, and judging whether the current version of the service subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
if the current version of the business subsystem can influence the system operation of the dependent subsystem, early warning processing is carried out on the current version of the business subsystem in the dependent subsystem;
and if the current version of the service subsystem does not influence the system operation of the dependent subsystem, shielding the current version of the service subsystem in the dependent subsystem.
Specifically, the specific implementation method of the instruction by the processor 10 may refer to the description of the relevant steps in the embodiment corresponding to the drawings, which is not described herein again.
Further, the integrated modules/units of the electronic device 1, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. The computer readable storage medium may be volatile or non-volatile. For example, the computer-readable medium may include: any entity or device capable of carrying said computer program code, recording medium, U-disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM).
The present invention also provides a computer-readable storage medium, storing a computer program which, when executed by a processor of an electronic device, may implement:
acquiring a service subsystem to be subjected to version updating in a service system, and identifying the current version of the service subsystem;
performing acceptance test on the service subsystem of the current version;
when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
calculating the operation influence value of the current version on the dependent subsystem, and judging whether the current version of the service subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
if the current version of the business subsystem can influence the system operation of the dependent subsystem, early warning processing is carried out on the current version of the business subsystem in the dependent subsystem;
and if the current version of the service subsystem does not influence the system operation of the dependent subsystem, shielding the current version of the service subsystem in the dependent subsystem.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus, device and method can be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is only one logical functional division, and other divisions may be realized in practice.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional module.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof.
The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference signs in the claims shall not be construed as limiting the claim concerned.
The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
The embodiment of the application can acquire and process related data based on an artificial intelligence technology. Among them, Artificial Intelligence (AI) is a theory, method, technique and application system that simulates, extends and expands human Intelligence using a digital computer or a machine controlled by a digital computer, senses the environment, acquires knowledge and uses the knowledge to obtain the best result.
Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the system claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Finally, it should be noted that the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims (10)

1. A system version monitoring method, the method comprising:
acquiring a service subsystem to be subjected to version updating in a service system, and identifying the current version of the service subsystem;
performing acceptance test on the service subsystem of the current version;
when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
calculating the operation influence value of the current version on the dependent subsystem, and judging whether the current version of the service subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
if the current version of the business subsystem can influence the system operation of the dependent subsystem, early warning processing is carried out on the current version of the business subsystem in the dependent subsystem;
and if the current version of the service subsystem does not influence the system operation of the dependent subsystem, shielding the current version of the service subsystem in the dependent subsystem.
2. The system version monitoring method of claim 1, wherein the performing acceptance testing on the current version of the business subsystem comprises:
extracting the overall source code of the business subsystem of the current version;
according to the function requirement of a service subsystem configured in advance, checking whether a source code block corresponding to the function requirement exists in the total source code;
when the source code block corresponding to any one of the functional requirements does not exist in the overall source code, terminating the acceptance test;
when the source code blocks corresponding to the function requirements all exist in the overall source code, compiling the overall source code, and detecting whether the overall source code has a compiling error;
when the overall source code has a compiling error, the acceptance test is terminated;
and when the general source code has no compiling error, judging that the current version passes an acceptance test.
3. The system version monitoring method of, wherein said identifying a subsystem having a dependency relationship with said business subsystem from said business system, obtaining a dependent subsystem of said business subsystem, comprises:
acquiring a subsystem dependency relationship tree preset in the service system;
querying a dependency relationship tree node corresponding to the service subsystem in the subsystem dependency relationship tree;
and extracting the subsystem cluster in the dependency tree node to obtain the dependency subsystem.
4. The system version monitoring method according to claim 1, wherein the calculating an operation influence value of the current version on the dependent subsystem and determining whether the current version of the business subsystem may influence the system operation of the dependent subsystem according to the operation influence value comprises:
calculating the operation influence value of the current version on the dependent subsystem by using a pre-constructed calculation formula of the operation influence value;
when the operation influence value is in a preset first influence degree interval or a preset second influence degree interval, judging that the current version of the service subsystem can influence the system operation of the dependent subsystem;
and when the operation influence value is in a preset third influence degree interval, judging that the current version of the service subsystem does not influence the system operation of the dependent subsystem.
5. The system version monitoring method of claim 4, wherein the calculating the operational impact value of the current version on the dependent subsystem using a pre-constructed operational impact value calculation formula comprises:
calculating the operation influence value of the current version on the dependent subsystem by using the following calculation formula of the operation influence value:
Figure FDA0003415281450000021
wherein n is the total number of version information items in the current version, xiFor the i-th one of the version information items, p (x)i) And H is the probability that the ith item in the version information item influences the operation of the dependent subsystem, and H is the operation influence value.
6. The system version monitoring method of claim 1, wherein the performing of the early warning process on the current version of the business subsystem in the dependent subsystem comprises:
judging the influence degree grade interval of the operation influence value according to the operation influence value;
when the operation influence value is in a preset first influence degree grade interval, executing first interval early warning on the current version, and reminding a user to process according to a preset first mode;
and when the operation influence value is in a preset second influence degree grade interval, executing second interval early warning on the current version, and reminding a user to process according to a preset second mode.
7. The system version monitoring method according to claim 6, wherein if the current version of the service subsystem does not affect the system operation of the dependent subsystem, performing a masking process on the current version of the service subsystem in the dependent subsystem includes:
and when the operation influence value is in a preset third influence degree grade interval, judging that the current version of the service subsystem does not influence the system operation of the dependent subsystem, and shielding the current version of the service subsystem in the dependent subsystem.
8. A system version monitoring apparatus, the apparatus comprising:
the system version acceptance testing module is used for acquiring a service subsystem to be subjected to version updating in a service system and identifying the current version of the service subsystem; performing acceptance test on the service subsystem of the current version; when the current version passes an acceptance test, identifying a subsystem having a dependency relationship with the service subsystem from the service system to obtain a dependent subsystem of the service subsystem;
the operation influence value calculation module is used for calculating the operation influence value of the current version on the dependent subsystem and judging whether the current version of the business subsystem can influence the system operation of the dependent subsystem according to the operation influence value;
the system version early warning module is used for judging whether the current version of the business subsystem can influence the system operation of the dependency subsystem or not, and carrying out early warning processing on the current version of the business subsystem in the dependency subsystem;
and the system version shielding module is used for judging that the current version of the business subsystem is shielded in the dependent subsystem if the current version of the business subsystem does not influence the system operation of the dependent subsystem.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the system version monitoring method of any one of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out a system version monitoring method according to any one of claims 1 to 7.
CN202111544160.9A 2021-12-16 2021-12-16 System version monitoring method and device, electronic equipment and readable storage medium Pending CN114237689A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111544160.9A CN114237689A (en) 2021-12-16 2021-12-16 System version monitoring method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111544160.9A CN114237689A (en) 2021-12-16 2021-12-16 System version monitoring method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN114237689A true CN114237689A (en) 2022-03-25

Family

ID=80757131

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111544160.9A Pending CN114237689A (en) 2021-12-16 2021-12-16 System version monitoring method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN114237689A (en)

Similar Documents

Publication Publication Date Title
CN112115145A (en) Data acquisition method and device, electronic equipment and storage medium
CN114881616A (en) Business process execution method and device, electronic equipment and storage medium
CN113468049A (en) Test method, device, equipment and medium based on configurable interface
CN113504935A (en) Software development quality evaluation method and device, electronic equipment and readable storage medium
CN111950621A (en) Target data detection method, device, equipment and medium based on artificial intelligence
CN113139743A (en) Sewage discharge index analysis method and device, electronic equipment and storage medium
CN112463530A (en) Anomaly detection method and device for micro-service system, electronic equipment and storage medium
CN111985545A (en) Target data detection method, device, equipment and medium based on artificial intelligence
CN115081016A (en) Log desensitization method and device, electronic equipment and storage medium
CN112486957A (en) Database migration detection method, device, equipment and storage medium
CN112579475A (en) Code testing method, device, equipment and readable storage medium
CN112288371A (en) Customs clearance inspection method and device, electronic equipment and computer readable storage medium
CN114896164A (en) Interface optimization method and device, electronic equipment and storage medium
CN114237689A (en) System version monitoring method and device, electronic equipment and readable storage medium
CN115033489A (en) Code resource detection method and device, electronic equipment and storage medium
CN115221171A (en) Abnormal data intelligent monitoring method and device, electronic equipment and storage medium
CN113469649A (en) Project progress analysis method and device, electronic equipment and storage medium
CN114662005A (en) Message pushing method, device, equipment and storage medium for user behavior track
CN113392090A (en) Data verification method, device, equipment and medium based on database migration
CN113240351A (en) Business data consistency checking method and device, electronic equipment and medium
CN114185776A (en) Big data point burying method, device, equipment and medium for application program
CN113051171A (en) Interface test method, device, equipment and storage medium
CN112667244A (en) Data verification method and device, electronic equipment and computer readable storage medium
CN113419916B (en) Wind control inspection program uninterrupted operation method, device, equipment and storage medium
CN117290257B (en) Software lifecycle standardization management method and system based on plug-in call

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination