CN114035835A - System backspacing risk assessment method - Google Patents
System backspacing risk assessment method Download PDFInfo
- Publication number
- CN114035835A CN114035835A CN202111223962.XA CN202111223962A CN114035835A CN 114035835 A CN114035835 A CN 114035835A CN 202111223962 A CN202111223962 A CN 202111223962A CN 114035835 A CN114035835 A CN 114035835A
- Authority
- CN
- China
- Prior art keywords
- rollback
- backspacing
- systems
- relation
- risk
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 23
- 238000012502 risk assessment Methods 0.000 title claims abstract description 22
- 238000011156 evaluation Methods 0.000 claims abstract description 18
- 238000004519 manufacturing process Methods 0.000 claims description 26
- 230000008859 change Effects 0.000 claims description 11
- 238000003860 storage Methods 0.000 claims description 7
- 238000002790 cross-validation Methods 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000012552 review Methods 0.000 description 6
- 238000005096 rolling process Methods 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 238000011867 re-evaluation Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2291—User-Defined Types; Storage management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a system backspacing risk assessment method, belonging to the technical field of risk assessment of computer technology, and the technical scheme comprises the following steps: standardizing and warehousing names and codes of all systems; step 2: filling in system backspacing risk evaluation content, and storing a system name and a system backspacing relation; and step 3: the backspacing relation is analyzed to obtain a backspacing relation chain among the systems, and the purpose is to evaluate which systems need to backspace together and which systems do not need to backspace when one system backspace in a distributed system environment.
Description
Technical Field
The invention belongs to the technical field of risk assessment of computer technology, and particularly relates to a system backspacing risk assessment method.
Background
With the increase of systems in a distributed environment, the relationship among the systems is more complex, more than hundreds of systems are on-line simultaneously in the same production window, and less than dozens of systems are on-line simultaneously, when one of the systems is on-line, the system needs to be backed down to the previous version because of reasons such as that the service verification fails or the system reports errors, and the like, which associated systems need to be backed down together, and which do not need to be backed down; if the associated system needing to be rolled back does not roll back to the last version, the access between the systems is likely to cause error report and a production event occurs.
The system rollback risk assessment methods in the prior art can be roughly divided into 2 types:
1) the off-line meeting review method comprises the steps of summoning the related system responsible persons of the same production window through organization off-line meeting review, then carrying out review of backspacing risk assessment on all the systems in production and aligning the backspacing influence of the systems, wherein the method has the following defects: when the system rollback really happens, the rollback influence is completely processed by manually informing;
2) the online statistics is combined with the offline review method, namely, relevant system responsible persons of the same production window fill system rollback risk assessment on line in a submitted production work order, for example, which system rollback is caused by filling the system rollback, and the like. After completing the statistical information online, the conference review is organized again offline to ensure the correctness of the backspacing effect. The method has the following defects: after the system rollback risk assessment is filled on line, a system rollback relation chain is difficult to automatically analyze according to the filled text content, and rollback influence processing still mainly depends on manual operation.
Disclosure of Invention
In order to solve the defects in the prior art, the invention provides a system rollback risk assessment method, which aims to assess which systems need to be rolled back together and which systems do not need to be rolled back when one system rolls back in a distributed system environment, and automatically warn corresponding system responsible persons when the system rolls back based on a rollback relation chain, so that production events caused by system rolling back are avoided.
The technical scheme adopted by the invention is as follows:
a system rollback risk assessment method specifically comprises the following steps:
step 1: the names and codes of all systems are subjected to specification and merged into a database according to a preset format, the name and code table structures of all systems are established and stored in the database, and an API (application program interface) is provided for inquiring the names and the codes of the systems, so that the uniqueness effect of the names and the codes of the systems is achieved, and the problem that the names of the systems cannot be used for program analysis in the prior art is solved;
step 2: establishing a system rollback relation table, filling system rollback risk evaluation contents, storing the filled system rollback risk evaluation contents in a storage medium in a file data stream format, and forming a key-value pair data structure by the corresponding system name and system rollback relation and storing the key-value pair data structure in the storage medium for the analysis of the whole system rollback relation chain in the step 3;
and step 3: all stored backspacing relations are analyzed to obtain backspacing relation chains among different systems, and risks during backspacing are controlled based on the backspacing relation chains, so that the problems of unreliable backspacing relations and artificial analysis in the prior art are solved.
According to the invention, through standardizing the system name and standardizing backspacing risk evaluation, the relationship chain tracking algorithm is used for analyzing the system backspacing relationship, and the system backspacing relationship chain is automatically generated and visualized, so that the problems of the necessary manual disposal process and the manual risk in the prior art are solved, and the complex backspacing risk among systems in the distributed system environment is clearer and more accurate.
Further, the step 1 specifically includes the following steps:
step 1.1: standardizing the names and codes of all systems, wherein each system has a unique code, and after the system has the unique code, the system codes are used for identifying the system in the subsequent steps;
step 1.2: the system name and the code are stored in a database for unified management, all subsequent system data acquisition needs to be based on the data source, and the problem of inaccuracy of the system name when filling in the backspacing risk evaluation content of the system is solved;
step 1.3: and step 1.2, managing the system data, classifying the system data into a system catalog of a data standard system, providing an api interface for acquiring the system data, wherein the api interface adopts an http protocol, and responding to the data format of the message body by using json. In the subsequent steps, when the system name and the code are required to be obtained, the system name and the code are obtained through the api interface, so that the uniqueness and the correctness of the system name are ensured.
Further, the step 2 specifically includes the following steps:
step 2.1: acquiring all production work orders of a production window, and acquiring all change system information of the same production window so as to judge which systems need to carry out backspacing risk evaluation;
step 2.2: on the basis of the step 1.1, setting controls for controlling filling authority in pages of all change lists showing the same production window, and filling the system rollback risk assessment content;
further, after the applicant in step 2.2 enters the backspacing risk evaluation page, two dimensions are required to be filled in for the backspacing relationship, the first dimension determines which systems need to backspace due to the backspacing of the system, the second dimension determines which systems need to backspace due to the backspacing of the system, and the two dimensions correspond to two system backspacing relationships but may correspond to a plurality of system backspacing relationships. By adopting the preferred technical scheme, the backspacing relation between systems is clearly described by defining the backspacing relation of two dimensions, and a complex backspacing relation chain is analyzed by combining a relation chain tracking algorithm;
step 2.3: developing a page for filling the rollback risk and judging the rollback relations of the systems, and accurately storing the system rollback relations and the system names of all the changed systems when the completion of filling and storage is carried out;
further, the system filled in step 2.3 is obtained through the api interface in step 1.3, so as to ensure the uniqueness of the system name and the code, when the system is filled in, the system name is selected through a drop-down box, and when the system name is stored in a database, the system name and the system code are stored;
further, the step 3 specifically includes the following steps:
step 3.1: analyzing the system rollback relation by adopting a relation chain tracking algorithm so as to obtain a system rollback relation chain and visually displaying the relation chain;
step 3.2: respectively establishing corresponding backspacing relations according to the two dimensions of the backspacing relations;
step 3.3: performing cross validation on the rollback relationship established in the step 3.2 according to the two dimensions of the rollback relationship, and determining whether the rollback relationship is valid;
step 3.4: step 3.2 to step 3.3 are circulated, and the rollback relations of all the systems are analyzed to obtain final rollback relation chain results of all the systems;
fallback relationship step 3.5: and repeating all the steps to finally obtain a system rollback relation chain with a correct production window, and when a certain system backs, ensuring that the relevant systems back together by means of short message early warning and the like so as to avoid production events caused by the back.
Furthermore, the system which needs to rollback but judges that the rollback relationship is invalid in the step 3.3 is prompted, and the rollback relationship is evaluated and filled again.
In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that:
1. according to the invention, through standardizing the system name and standardizing backspacing risk evaluation, the relationship chain tracking algorithm is used for analyzing the system backspacing relationship, and the system backspacing relationship chain is automatically generated and visualized, so that the problems of the necessary manual disposal process and the manual risk in the prior art are solved, and the complex backspacing risk among systems in the distributed system environment is clearer and more accurate.
2. By defining the backspacing relation of two dimensions, the backspacing relation between systems is clearly described, and a relation chain tracking algorithm is combined, so that a complex backspacing relation chain is analyzed.
3. The complex backspacing risk among systems in a distributed system environment is reduced, a backspacing relation chain of the system is automatically generated and visualized, and the risk of the system during backspacing becomes controllable.
4. Compared with the traditional system backspacing conference review, the invention solves the problem of excessive manual disposal by standardizing the system name, evaluating the backspacing risk and automatically analyzing the backspacing relation.
Drawings
The invention will now be described, by way of example, with reference to the accompanying drawings, in which:
FIG. 1 is a schematic flow chart of a system backspacing risk assessment method according to the present invention;
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of embodiments of the present application, generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
In the description of the embodiments of the present application, it should be noted that the terms "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings or orientations or positional relationships that the products of the present invention are usually placed in when used, and are only used for convenience of description and simplicity of description, but do not indicate or imply that the devices or elements that are referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present application. Furthermore, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
The present invention will be described in detail with reference to fig. 1.
A system rollback risk assessment method specifically comprises the following steps:
step 1: the names and codes of all systems are subjected to specification according to a preset format and are merged into a database, a table structure for storing the names and codes of all systems is established in the database, and an API (application programming interface) is provided for inquiring the names and codes of the systems, so that the uniqueness effect of the names and codes of the systems is achieved;
further, the step 1 specifically includes the following steps:
step 1.1: standardizing the names and codes of all systems, wherein each system has a unique code, and after the system has the unique code, the system codes are used for identifying the system in the subsequent steps;
step 1.2: establishing a table structure for storing names and codes of all systems in a database, storing the system names and the codes in the database for unified management, and solving the problem of inaccuracy of the system names when filling in the backspacing risk evaluation content of the system based on the data source for all subsequent system name acquisition;
step 1.3: and (3) classifying the system data management in the step (1.2) into a system catalog of a data standard system, providing an api interface for acquiring system data, wherein the api interface adopts an http protocol, responding to the data format of the message body and using json, and the json data comprises a system name and a system code. In the subsequent steps, when the system name and the code are required to be obtained, the system name and the code are obtained through the api interface, so that the uniqueness and the correctness of the system name are ensured.
Step 2: establishing a system backspacing relation table, wherein the table structure mainly comprises a backspacing system name, a backspacing system code, an associated system name and an associated system code, analyzing the system backspacing relation according to the filled system backspacing risk evaluation content, storing one backspacing relation as a row of data of the table, and finally storing the backspacing relation data of all the systems for the analysis of the whole system backspacing relation chain in the step 3; further, the step 2 specifically includes the following steps:
step 2.1: acquiring all production work orders of a production window, and acquiring all change system information of the same production window so as to judge which systems need to carry out backspacing risk evaluation;
step 2.2: on the basis of the step 1.1, developing a page for displaying all change lists of the same production window, adding a 'filling rollback risk assessment' button behind each change, controlling filling authority, filling the system rollback risk assessment content, and only an applicant of a work order has authority to fill the system rollback risk assessment content;
further, after the applicant in step 2.2 enters a rollback risk evaluation page, two dimensions are required to be filled in for a rollback relationship, the first dimension judges which systems need to be rolled back together due to the rolling back of the system, the second dimension judges which systems need to be rolled back together due to the rolling back of the system, and the two dimensions correspond to two system rolling back relationships but may correspond to a plurality of system rolling back relationships; by defining the backspacing relation of two dimensions, the backspacing relation between systems is clearly described, and a relation chain tracking algorithm is combined, so that a complex backspacing relation chain is analyzed;
step 2.3: developing a page for filling the rollback risk, wherein the rollback relation filled in the page comprises the two dimensions, accurately storing the system rollback relation and the system name of the change system when the completion of filling is carried out, and the table structure of the storage mainly comprises the rollback system name, the rollback system code, the associated system name and the associated system code;
further, the system filled in step 2.3 is obtained through the api interface in step 1.3, so as to ensure the uniqueness of the system name and the code, when the system is filled in, the system name is selected through a drop-down box, and when the system name is stored in a database, the system name and the system code are stored;
step 2.4: and (3) the change systems of the same production window need to complete the step 2.2 to the step 2.3, so that the system backspacing relations of all the change systems are stored in a storage for the step 3 to analyze the whole system backspacing relation chain.
And step 3: and analyzing all stored rollback relations, obtaining a complete rollback relation chain of all systems by adopting a link tracking algorithm according to two dimensions of the rollback relations, and controlling risks when rollback occurs based on the rollback relation chain.
Further, the step 3 specifically includes the following steps:
step 3.1: after the step 2 is completed, backspacing risk evaluation contents filled in all the change systems and backspacing relations among the systems can be obtained, the backspacing relations of the systems are analyzed by adopting a relation chain tracking algorithm, and the backspacing relations established by two dimensions of the backspacing relations need to be validated;
step 3.2: establishing a backspacing relation according to a first dimension of two dimensions of the backspacing relation, and judging whether the backspacing relation generated by the dimension is effective or not;
step 3.3: analyzing all the fallback relations stored in the step 2 according to the second dimension of the two dimensions of the fallback relations, and determining whether the fallback relation established in the step 3.2 by the first dimension is valid;
step 3.4: establishing a backspacing relation according to the second dimension of the two dimensions of the backspacing relation, and judging whether the backspacing relation generated by the dimension is effective or not;
step 3.5: according to the first dimension of the two dimensions of the backspacing relation, analyzing all backspacing relations stored in the step 2, and confirming whether the backspacing relation established by the second dimension in the step 3.4 is effective
Step 3.6: step 3.2 to step 3.5 are circulated, the rollback relations of all the systems are analyzed, the effectiveness of all the rollback relations is verified, and finally the rollback relation chain results of all the systems are obtained;
step 3.7: and repeating all the steps to finally obtain a system rollback relation chain with a correct production window, and when a certain system backs, ensuring that the relevant systems back together by means of short message early warning and the like so as to avoid production events caused by the back.
The specific algorithm is as follows:
1) supposing that A, B, C three systems fill in rollback risk assessment content, wherein the content filled in the system A is system rollback A, and the systems B and C need to rollback, two rollback relations are considered to exist, namely the influence of the system A on the system B and the influence of the system A on the system C, and whether the systems B and C are filled with the two rollback relations is tracked in turn;
2) checking the rollback relation filled by the system B according to the second dimension of the step 2, and if the rollback of the system A and the rollback of the system are needed together, considering that the rollback relation of the system A and the system B, which is aligned with the rollback relation of the system A and the system B, is influenced, and the rollback relation is correct and effective; checking the rollback relation filled in the C system according to the second dimension in the step 2.3, if the rollback relation of the A system is not aligned and the system needs to rollback together, considering that the rollback relations of the A and the C systems are not aligned, and judging that the rollback relation of the A influencing the C is wrong;
3) the steps are circulated, and the rollback relations of all the systems are analyzed to obtain the final rollback relation chain results of all the systems;
the rollback relationship linking result obtained in the above embodiment is not necessarily the final correct result, because the rollback relationships of the systems a and C are not aligned, re-evaluation and re-filling are required, and a system that needs to rollback but determines that the rollback relationship is invalid is prompted, and re-evaluation and filling are performed on the rollback relationship, specifically: in the display page of the fallback relation chain, the unaligned fallback relation of the influence A and the influence C in the step 3.3 is highlighted, so that an incorrect fallback relation is found quickly, meanwhile, related responsible persons of the systems A and C are notified to check and confirm in a short message or mail mode until the relation chains of the systems of the two parties are consistent, and the purpose of the step is to align the fallback relations of all the changed systems, and the unaligned fallback relation can be evaluated and filled again.
According to the invention, through standardizing the system name and standardizing backspacing risk evaluation, the relationship chain tracking algorithm is used for analyzing the system backspacing relationship, and the system backspacing relationship chain is automatically generated and visualized, so that the problems of the necessary manual disposal process and the manual risk in the prior art are solved, and the complex backspacing risk among systems in the distributed system environment is clearer and more accurate.
The above-mentioned embodiments only express the specific embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for those skilled in the art, without departing from the technical idea of the present application, several changes and modifications can be made, which are all within the protection scope of the present application.
Claims (7)
1. A system rollback risk assessment method is characterized by comprising the following steps:
step 1: standardizing the names and codes of all systems according to a preset format, merging the names and codes into a database, and establishing and storing the name and code table structures of all systems in the database;
step 2: establishing a system backspacing relation table, filling system backspacing risk evaluation contents, storing the filled system backspacing risk evaluation contents in a storage medium in a file data stream format, and forming a key-value pair data structure by the corresponding system name and the system backspacing relation and storing the key-value pair data structure in the storage medium;
and step 3: and analyzing the backspacing relation to obtain a backspacing relation chain among different systems, and controlling the risk when backspacing occurs based on the backspacing relation chain.
2. The method for evaluating the risk of system rollback according to claim 1, wherein the step 1 specifically comprises the following steps:
step 1.1: standardizing names and codes of all systems, wherein each system has a unique code, and establishing the table space and the table structure;
step 1.2: storing the system name and the code into a database for unified management;
step 1.3: and step 1.2, managing and classifying the system data into a corresponding system directory to form a tree data structure in a directory form, and providing an api interface for acquiring the system data.
3. The method for evaluating the risk of system rollback according to claim 2, wherein the step 2 specifically comprises the following steps:
step 2.1: acquiring all production work orders of a production window, and acquiring all change system information of the same production window, so as to judge which systems need to carry out backspacing risk evaluation;
step 2.2: on the basis of the step 1.1, setting controls for controlling filling authority in pages of all change lists showing the same production window, and filling the system rollback risk assessment content;
step 2.3: and judging the rollback relations of the systems, and accurately storing the system rollback relations and the system names of all changed systems when the rollback risk pages are filled in and stored.
4. The method as claimed in claim 3, wherein in step 2.2, after entering the rollback risk evaluation page, two dimensions are filled in for the rollback relationship, wherein the first dimension determines which systems need to be rolled back together due to the system rollback, and the second dimension determines which systems need to be rolled back together due to the system rollback.
5. A system rollback risk assessment method according to claim 3, wherein the system filled in step 2.3 is obtained through the api interface of step 1.3, so as to ensure the uniqueness of the system name and the system code, when filling in the system, the system name is selected through a drop-down box, and when saving the system name in the database, the system name and the system code are saved.
6. The method for evaluating the risk of system rollback according to claim 3, wherein the step 3 specifically comprises the following steps:
step 3.1: analyzing the system rollback relation by adopting a relation chain tracking algorithm so as to obtain a system rollback relation chain and visually displaying the relation chain;
step 3.2: respectively establishing corresponding backspacing relations according to the two dimensions of the backspacing relations;
step 3.3: performing cross validation on the rollback relationship established in the step 3.2 according to the two dimensions of the rollback relationship, and determining whether the rollback relationship is valid;
step 3.4: step 3.2 to step 3.3 are circulated, and the rollback relations of all the systems are analyzed to obtain final rollback relation chain results of all the systems;
step 3.5: and repeating all the steps to finally obtain a system rollback relation chain with a correct production window, and when a certain system backs, giving an early warning to ensure that the relevant systems back together, so as to avoid the production event caused by the back.
7. The method as claimed in claim 6, wherein the system requiring rollback but determining that the rollback relationship is invalid in step 3.3 is prompted, and the rollback relationship is re-evaluated and filled.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111223962.XA CN114035835A (en) | 2021-10-15 | 2021-10-15 | System backspacing risk assessment method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111223962.XA CN114035835A (en) | 2021-10-15 | 2021-10-15 | System backspacing risk assessment method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114035835A true CN114035835A (en) | 2022-02-11 |
Family
ID=80142217
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111223962.XA Pending CN114035835A (en) | 2021-10-15 | 2021-10-15 | System backspacing risk assessment method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114035835A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9575840B1 (en) * | 2014-08-15 | 2017-02-21 | Google Inc. | Recovery rollback risk reduction |
| CN110223127A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Bill data backing method and system |
| CN112288573A (en) * | 2020-12-25 | 2021-01-29 | 支付宝(杭州)信息技术有限公司 | Method, device and equipment for constructing risk assessment model |
| CN112288439A (en) * | 2020-11-23 | 2021-01-29 | 中信银行股份有限公司 | Risk assessment method and device, electronic equipment and readable storage medium |
-
2021
- 2021-10-15 CN CN202111223962.XA patent/CN114035835A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9575840B1 (en) * | 2014-08-15 | 2017-02-21 | Google Inc. | Recovery rollback risk reduction |
| CN110223127A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Bill data backing method and system |
| CN112288439A (en) * | 2020-11-23 | 2021-01-29 | 中信银行股份有限公司 | Risk assessment method and device, electronic equipment and readable storage medium |
| CN112288573A (en) * | 2020-12-25 | 2021-01-29 | 支付宝(杭州)信息技术有限公司 | Method, device and equipment for constructing risk assessment model |
Non-Patent Citations (1)
| Title |
|---|
| WANFANG003: ""信息系统的风险评估过程与评估方法"", pages 1 - 4, Retrieved from the Internet <URL:《https://blog.csdn.net/wanfang003/article/details/83994668》> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20080091742A1 (en) | System and method for detecting and updating geographical information dataset versions | |
| CN109656205B (en) | Defective product control method and device, electronic device and readable storage medium | |
| CN113312260B (en) | Interface test method, device, equipment and storage medium | |
| CN111522741A (en) | Interface test code generation method and device, electronic equipment and readable storage medium | |
| CN111782464B (en) | Webpage dynamic anomaly monitoring method and system | |
| CN111045935A (en) | Automatic version auditing method, device, equipment and storage medium | |
| CN111752833B (en) | Software quality system approval method, device, server and storage medium | |
| CN112561370A (en) | Software version management method and device, computer equipment and storage medium | |
| CN112348530A (en) | Automatic server production inspection and repair method | |
| CN112632330A (en) | Method and device for routing inspection of ATM equipment, computer equipment and storage medium | |
| CN113780986A (en) | Measurement method, system, equipment and medium for software development process | |
| WO2002057988A2 (en) | Method, apparatus and system for quality performance evaluation of a supplier base | |
| CN114035835A (en) | System backspacing risk assessment method | |
| CN111427959A (en) | Data storage method and device | |
| CN115136129A (en) | Digital inspection method and device applied to clinical test and related equipment | |
| Allalouf et al. | Quality control for scoring tests administered in continuous mode: An NCME instructional module | |
| CN112598226A (en) | Equipment checking method, device, equipment and storage medium | |
| CN112035617A (en) | System testing method and device based on data comparison, computer equipment and medium | |
| CN114401494B (en) | Short message issuing abnormality detection method, device, computer equipment and storage medium | |
| CN112860803A (en) | Account checking method, device and equipment and readable storage medium | |
| CN115187411A (en) | Insurance applicability automatic analysis method and system and computer equipment | |
| CN114065698A (en) | Address standardization processing system and method | |
| CN117874007A (en) | Spatial data storage management method, device, equipment and medium | |
| CN117421346A (en) | VMT-based automobile assembly on-line measurement data analysis and monitoring method and device | |
| CN114882966A (en) | Electronic medical record generation method, device, equipment, medium and product |
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 |