CN118113554A - Abnormality monitoring method and device for software development, storage medium and electronic equipment - Google Patents
Abnormality monitoring method and device for software development, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN118113554A CN118113554A CN202410182067.5A CN202410182067A CN118113554A CN 118113554 A CN118113554 A CN 118113554A CN 202410182067 A CN202410182067 A CN 202410182067A CN 118113554 A CN118113554 A CN 118113554A
- Authority
- CN
- China
- Prior art keywords
- stage
- current stage
- monitoring
- preset rule
- preset
- 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
- 238000012544 monitoring process Methods 0.000 title claims abstract description 140
- 238000000034 method Methods 0.000 title claims abstract description 128
- 230000005856 abnormality Effects 0.000 title claims abstract description 25
- 238000003860 storage Methods 0.000 title claims abstract description 18
- 230000008569 process Effects 0.000 claims abstract description 80
- 230000002159 abnormal effect Effects 0.000 claims abstract description 52
- 238000012827 research and development Methods 0.000 claims abstract description 25
- 238000011161 development Methods 0.000 claims description 40
- 230000004044 response Effects 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012806 monitoring device Methods 0.000 claims description 5
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000011156 evaluation Methods 0.000 description 25
- 238000012360 testing method Methods 0.000 description 14
- 238000001514 detection method Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000012549 training Methods 0.000 description 6
- 238000012552 review Methods 0.000 description 5
- 230000007547 defect Effects 0.000 description 4
- 238000003908 quality control method Methods 0.000 description 4
- 210000001503 joint Anatomy 0.000 description 3
- 238000012356 Product development Methods 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 238000010948 quality risk assessment Methods 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000012502 risk assessment Methods 0.000 description 2
- 230000000391 smoking effect Effects 0.000 description 2
- 208000006011 Stroke Diseases 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013528 artificial neural network Methods 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000003066 decision tree Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000011056 performance test Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000004886 process control Methods 0.000 description 1
- 238000011002 quantification Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 238000012706 support-vector machine Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- 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/3664—Environments for testing or debugging software
-
- 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/3676—Test management for coverage analysis
-
- 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/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an anomaly monitoring method and device for software development, a storage medium and electronic equipment. The method relates to the technical field of quality management of software development process, and comprises the following steps: in the process of software research and development, acquiring stage information of a current stage, wherein the stage information is used for representing the identification of the current stage and whether the research and development of the current stage is finished; responding to the completion of the research and development of the current stage, acquiring preset rules corresponding to the stage information from a preset rule library, wherein different preset rules corresponding to different stages are stored in the preset rule library; and monitoring the current stage based on a preset rule and data generated in the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether the current stage is abnormal or not. The invention solves the technical problem that the abnormal management rules are not uniform when the abnormality of the software research and development process is monitored in the related technology.
Description
Technical Field
The invention relates to the technical field of quality management in a software development process, in particular to an abnormality monitoring method and device for software development, a storage medium and electronic equipment.
Background
The quality control management of the current software project process generally relies on project managers to coordinate the personnel of each party in the project to manually evaluate the project risk and progress, and send delay risk and quality risk through e-mails and workgroup messages, and finally invite each party to make a decision about risk response through conferences. However, the method mainly relies on decision-makers to manage by means of memory, and does not form systematic decision rules and decision flows, so that decisions are inconsistent when large-scale projects are cooperated in multiple directions, and abnormal management rules are not unified when abnormal monitoring is performed in the software research and development process.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the invention provides an abnormality monitoring method and device for software development, a storage medium and electronic equipment, which are used for at least solving the technical problem that abnormality management rules are not uniform when abnormality monitoring is performed on a software development process in the related technology.
According to an aspect of the embodiment of the present invention, there is provided an anomaly monitoring method for software development, including: in the process of software research and development, acquiring stage information of a current stage, wherein the stage information is used for representing the identification of the current stage and whether the research and development of the current stage is finished; responding to the completion of the research and development of the current stage, acquiring preset rules corresponding to the stage information from a preset rule library, wherein different preset rules corresponding to different stages are stored in the preset rule library; and monitoring the current stage based on a preset rule and data generated in the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether the current stage is abnormal or not.
Optionally, the method further comprises: controlling the software development process to enter the next stage in response to the monitoring result that no abnormality occurs in the current stage, and repeatedly acquiring stage information of the next stage, monitoring the next stage based on a preset rule corresponding to the next stage and data generated in the next stage in response to the next stage development being completed, so as to obtain a monitoring result until the software development process is finished; and responding to the monitoring result that the current stage is abnormal, outputting abnormal alarm information, and interrupting the software research and development process.
Optionally, after interrupting the software development process, the method further comprises: and carrying out manual auditing on the monitoring result to obtain a manual auditing result, wherein the manual auditing result is used for verifying whether the accuracy of the monitoring result is greater than or equal to a preset threshold value.
Optionally, the method further comprises: responding to the manual auditing result that the accuracy of the monitoring result is larger than or equal to a preset threshold value, terminating the software research and development process, and outputting abnormal alarm information; and responding to the manual auditing result that the accuracy of the monitoring result is smaller than a preset threshold value, recovering the software research and development process, and controlling the software research and development process to enter the next stage.
Optionally, the method further comprises: in response to the existence of a plurality of sub-phases in the current phase, monitoring data generated by the plurality of sub-phases in sequence based on the research and development completion time of the plurality of sub-phases and a preset rule base to obtain a plurality of sub-monitoring results; responding to the monitoring results of the plurality of sub-stages to determine that the current stage is not abnormal; and determining that the current stage is abnormal in response to the plurality of sub-monitoring results being abnormal in at least one sub-stage of the plurality of sub-stages.
Optionally, monitoring the current stage based on the preset rule and the data generated by the current stage to obtain a monitoring result, including: responding to the data generated in the current stage to completely meet the preset rule, and determining that the monitoring result is abnormal in the current stage; and responding to the data generated in the current stage failing to fully meet the preset rule, and determining that the monitoring result is abnormal in the current stage.
Optionally, before the preset rule corresponding to the stage information is obtained from the preset rule base, the method further includes: based on the identification in the stage information, determining application scenes of different stages, wherein the application scenes comprise one of the following: the security level of the second application scene is higher than that of the first application scene; based on application scenes, determining preset rules corresponding to different stages; and constructing a preset rule base based on preset rules corresponding to different stages.
Optionally, based on the application scenario, determining the preset rule corresponding to the different phases includes: responding to the application scene as a first application scene, and obtaining a first preset rule of different stages in the first application scene Jing Duiying based on the first weight; responding to the application scene as a second application scene, and obtaining second preset rules corresponding to different stages in the second application scene based on second weights, wherein the second weights are larger than the first weights, and the number of the second preset rules is larger than that of the first preset rules; summarizing the first preset rule and the second preset rule to obtain preset rules corresponding to different stages.
Optionally, obtaining the first preset rule of the different stages in the first application field Jing Duiying based on the first weight includes: setting corresponding first initial preset rules for different stages; and distributing corresponding weights to the first initial preset rule to obtain the first preset rule.
According to another aspect of the embodiment of the present invention, there is also provided an anomaly monitoring device for software development, including: the first acquisition module is used for acquiring phase information of the current phase in the process of developing software, wherein the phase information is used for representing the identification of the current phase and whether the development of the current phase is finished or not; the second acquisition module is used for acquiring preset rules corresponding to the stage information from a preset rule base in response to the completion of the research and development of the current stage, wherein different preset rules corresponding to different stages are stored in the preset rule base; the monitoring module is used for monitoring the current stage based on a preset rule and data generated in the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether the current stage is abnormal or not.
According to another aspect of the embodiment of the present invention, there is also provided a computer readable storage medium, where the computer readable storage medium includes a stored program, and when the program runs, the device on which the computer readable storage medium is controlled to execute the method of any one of the above steps.
According to another aspect of embodiments of the present invention there is also provided an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the method of any of the above.
In the embodiment of the invention, the stage information of the current stage is acquired in the process of software development, wherein the stage information is used for representing the identification of the current stage and whether the development of the current stage is finished or not; responding to the completion of the research and development of the current stage, acquiring preset rules corresponding to the stage information from a preset rule library, wherein different preset rules corresponding to different stages are stored in the preset rule library; and monitoring the current stage based on a preset rule and data generated in the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether an abnormal mode occurs in the current stage. It is easy to notice that through setting up the rule base of predetermineeing, can be directly through predetermineeing the rule in the rule base and carry out unified anomaly monitoring to different stages, need not different decision-makers and carry out different anomaly monitoring to the anomaly of each stage, reached the purpose that can unify monitoring to the anomaly in the software research and development process to realized improving the technical effect to the uniformity of anomaly monitoring in the software research and development process, and then solved the technical problem that during the anomaly monitoring to the software research and development process in the correlation technique, anomaly management rule is not unified.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
FIG. 1 is a flow chart of a software developed anomaly monitoring method in accordance with an embodiment of the present invention;
FIG. 2 is a schematic diagram of an alternative preset rule base according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an alternative develop whole process admission stuck point automation in accordance with an embodiment of the invention;
FIG. 4 is a workflow diagram of an alternative automated stuck point assessment apparatus according to an embodiment of the invention;
Fig. 5 is a schematic diagram of a software developed anomaly monitoring device according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
In accordance with an embodiment of the present invention, a software developed anomaly monitoring method embodiment is provided, it being noted that the steps shown in the flowchart of the figures may be performed in a computer system, such as a set of computer executable instructions, and, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than what is shown or described herein.
FIG. 1 is a flowchart of a software developed anomaly monitoring method according to an embodiment of the present invention, as shown in FIG. 1, the method comprising the steps of:
Step S102, acquiring stage information of a current stage in a software development process, wherein the stage information is used for representing the identification of the current stage and whether the development of the current stage is completed.
The software development process described above may include, but is not limited to: a demand phase, a development phase, a test phase, a gray scale phase, and an on-line phase. The requirement stage is used for determining the functional and performance requirements of the software and knowing the requirements and expectations of users. The development stage is used for designing the architecture, interfaces and functional modules of the software according to the result of the demand stage. The test stage is used for performing functional test, performance test, compatibility test and the like on the software, so that the quality of the software is ensured. The gray level stage may be to test the software by a small part of users after the software is primarily developed, so as to determine whether the software has a problem. The online stage is a stage in which after software development is completed, the external user is formally opened, and all users can use the online stage. The phase information described above may include, but is not limited to: identification of the current phase and phase state information. The stage status information can indicate whether the development of the current stage is completed, and the identifier may be an item identifier (Identification) of the current stage, but is not limited thereto, and may be an item name of the current stage.
In an alternative embodiment, there are multiple stages in the process of developing the software, and each stage generates corresponding data, so that in order to ensure that the software can be developed accurately, in the case that the software is developed in different stages, the stage information of the current stage can be obtained by the stuck point evaluation device to determine whether the data generated in the current stage needs to be monitored. The stage information can indicate the identification of the corresponding different stages and whether the research and development is completed or not.
It should be noted that, when advancing in each stage in the development process, the component interface of the stuck point evaluation device may be invoked, the parameter is invoked to transfer the item ID of the current stage, the stuck point evaluation device may trigger a stuck point evaluation event (i.e. a preset rule) based on the state data, and the stuck point evaluation result is presented on the stage advancing page, and meanwhile, risk early warning multi-channel access is performed for the risk needing to be alarmed.
Step S104, in response to the completion of the research and development of the current stage, acquiring the preset rules corresponding to the stage information from a preset rule base, wherein different preset rules corresponding to different stages are stored in the preset rule base.
The preset rule base can be built in advance by a researcher, wherein preset rules corresponding to different stages are stored in the preset rule base, and data generated in different stages can be monitored based on the corresponding preset rules so as to ensure the accuracy of a software research and development process. FIG. 2 is a schematic diagram of an alternative preset rule base according to an embodiment of the present invention, as shown in FIG. 2, the software development process includes: a demand phase, a development phase, a test phase, a gray scale phase, and an on-line phase. The preset rules of the demand stage may include, but are not limited to: product demand documents (Product Requirements Document, PRD) pass review, review of legacy questions is completed, user Interface (UI) passes review, PRD and UI profile archive detection. The preset rules of the development phase may include, but are not limited to: project branch pulling, development machine application, warehouse entry quality inspection passing, development environment deployment, advanced test rebase, smoke test passing, automatic regression passing, code coverage reaching standards and advanced test Code Review (CR) passing, wherein rebase is a concept of a version control system, and rebase refers to reapplying a submitting record of a current branch to a target branch when merging branches in version control so as to make the submitting history clearer and more visual. The preset rules for the test phase may include, but are not limited to: and (3) deploying a Test environment, wherein the use case passing rate reaches the standard, closing project defects, testing (Test) coverage rate reaches the standard, and issuing and evaluating and detecting safety. The preset rules for gray scale phase may include, but are not limited to: and (5) deploying a gray environment, starting gray drainage, and finishing gray coverage up to the standard and gray acceptance. The preset rules for the online phase may include, but are not limited to: and (5) on-line code packaging, blue-green deployment release, blue-green release confirmation and release confirmation completion.
In an alternative embodiment, after the stage information of the current stage is obtained by the stuck point evaluation device, the stage information may be analyzed, and in the case that the stage information can embody that the research and development of the current stage is completed, a preset rule corresponding to the stage information may be obtained from a preset rule base based on the identifier of the stage information, so that the data generated in the current stage may be monitored based on the preset rule corresponding to the stage information. For example, after the stage information is acquired, the current stage may be determined to be a required stage based on the identifier in the stage information, meanwhile, the stage status information in the stage information may be analyzed, and in the case that the stage status information is determined to be that the development of the required stage is completed, a preset rule corresponding to the stage information may be acquired in a preset rule base, for example, a preset rule corresponding to the required stage may be acquired, so that the data generated in the current stage may be monitored based on the preset rule.
And step S106, monitoring the current stage based on a preset rule and data generated in the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether the current stage is abnormal or not.
In an alternative embodiment, in the case that the preset rule corresponding to the current stage is obtained, the current stage may be monitored by the stuck point evaluation device based on the preset rule and the data generated by the current stage, so as to obtain a monitoring result. For example, after the preset rule corresponding to the demand phase is obtained, the data generated in the demand phase may be determined based on the preset rule corresponding to the demand phase, where the monitoring result may be determined that no abnormality occurs in the current phase in the case where the data generated in the demand phase all satisfy the preset rule, and where the abnormality occurs in the current phase in the case where at least one data generated in the demand phase does not satisfy the preset rule.
In the embodiment of the invention, the stage information of the current stage is acquired in the process of software development, wherein the stage information is used for representing the identification of the current stage and whether the development of the current stage is finished or not; responding to the completion of the research and development of the current stage, acquiring preset rules corresponding to the stage information from a preset rule library, wherein different preset rules corresponding to different stages are stored in the preset rule library; and monitoring the current stage based on a preset rule and data generated in the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether an abnormal mode occurs in the current stage. It is easy to notice that through setting up the rule base of predetermineeing, can be directly through predetermineeing the rule in the rule base and carry out unified anomaly monitoring to different stages, need not different decision-makers and carry out different anomaly monitoring to the anomaly of each stage, reached the purpose that can unify monitoring to the anomaly in the software research and development process to realized improving the technical effect to the uniformity of anomaly monitoring in the software research and development process, and then solved the technical problem that during the anomaly monitoring to the software research and development process in the correlation technique, anomaly management rule is not unified.
Optionally, the method further comprises: controlling the software development process to enter the next stage in response to the monitoring result that no abnormality occurs in the current stage, and repeatedly acquiring stage information of the next stage, monitoring the next stage based on a preset rule corresponding to the next stage and data generated in the next stage in response to the next stage development being completed, so as to obtain a monitoring result until the software development process is finished; and responding to the monitoring result that the current stage is abnormal, outputting abnormal alarm information, and interrupting the software research and development process.
The abnormality alert information described above may include, but is not limited to: mail early warning information and image early warning information.
In an alternative embodiment, under the condition that the monitoring result is determined that no abnormality occurs in the current stage, the next stage can be controlled by the stuck point evaluation device to control the software development to enter the next stage, stage information of the next stage is repeatedly acquired, the next stage is monitored based on preset rules corresponding to the next stage and data generated in the next stage in response to completion of the next stage development, and a step of obtaining the monitoring result is performed until the software development process is finished. For example, in the case that it is determined that no abnormality occurs in the demand stage, the stuck point evaluation device may control the software development process to enter the development stage, and repeatedly acquire stage information of the development stage, and in the case that it is determined that development of the development stage is completed, the stuck point evaluation device may monitor data generated in the development stage based on a preset rule corresponding to the development stage, so as to obtain a monitoring result, until the software development process is completed.
In another alternative embodiment, in the case that the monitoring result is determined to be that the current stage is abnormal, the abnormal alarm information can be output through the stuck point evaluation device, and the software development process is interrupted. For example, the abnormal alarm mail can be sent to the user terminal of the developer through the stuck point evaluation device, and the image early warning information can be sent to the user terminal of the developer through the stuck point evaluation device so as to prompt the occurrence of the abnormality in the current stage of the software development process.
Optionally, after interrupting the software development process, the method further comprises: and carrying out manual auditing on the monitoring result to obtain a manual auditing result, wherein the manual auditing result is used for verifying whether the accuracy of the monitoring result is greater than or equal to a preset threshold value.
The preset threshold may be set in advance by a developer, and is used for determining whether the monitoring result is accurate. The specific numerical value user can set according to the actual research and development requirements, and in this embodiment, the specific numerical value user can be 95%, but is not limited to this, and can also be 90%,99%, and the like.
In an alternative embodiment, after the software development process is interrupted, the monitoring result can be sent to the developer through the stuck point evaluation device, meanwhile, the developer can manually monitor the data generated in the current stage based on the preset rule to obtain the manual monitoring result, then the manual monitoring result can be compared with the monitoring result, and under the condition that the monitoring result is identical to the manual monitoring result, the accuracy of the manual auditing result can be determined to be the monitoring result and is greater than or equal to the preset threshold value. And under the condition that the monitoring result is different from the manual monitoring result, determining that the accuracy of the manual auditing result is smaller than a preset threshold value.
Optionally, the method further comprises: responding to the manual auditing result that the accuracy of the monitoring result is larger than or equal to a preset threshold value, terminating the software research and development process, and outputting abnormal alarm information; and responding to the manual auditing result that the accuracy of the monitoring result is smaller than a preset threshold value, recovering the software research and development process, and controlling the software research and development process to enter the next stage.
In an alternative embodiment, under the condition that the accuracy of the manual auditing result is determined to be greater than or equal to the preset threshold value, the monitoring result can be determined to be accurate, so that the current stage can be determined to be abnormal, the software development process can be terminated, and abnormal alarm information can be output. Under the condition that the accuracy of the manual auditing result is determined to be smaller than the preset threshold value, the monitoring result can be determined to be inaccurate, namely erroneous judgment occurs, at the moment, the stuck point evaluation device can be controlled to recover the software research and development process, and the software research and development process is controlled to enter the next stage.
After the software development process is terminated, the developer can process the abnormality occurring in the current stage, and after the abnormality processing is determined to be completed, the stuck point evaluation device can be controlled to resume the software development process, and the software development process is controlled to enter the next stage.
Optionally, the method further comprises: in response to the existence of a plurality of sub-phases in the current phase, monitoring data generated by the plurality of sub-phases in sequence based on the research and development completion time of the plurality of sub-phases and a preset rule base to obtain a plurality of sub-monitoring results; responding to the monitoring results of the plurality of sub-stages to determine that the current stage is not abnormal; and determining that the current stage is abnormal in response to the plurality of sub-monitoring results being abnormal in at least one sub-stage of the plurality of sub-stages.
In an alternative embodiment, under the condition that a plurality of sub-phases exist in the current phase, the stuck point evaluation device can acquire sub-phase information of the plurality of sub-phases at the same time, then analyze the plurality of sub-phase information to obtain research and development completion time of the plurality of sub-phases, and then detect data generated by the plurality of sub-phases based on the research and development completion time of the plurality of sub-phases and a preset rule base to obtain a plurality of sub-monitoring results. For example, the stuck point evaluation apparatus may first monitor sub-stages that complete development based on development completion time, and monitor a plurality of sub-stages in sequence according to a sequence of completing development, so as to obtain a plurality of monitoring results.
In another alternative embodiment, in a case that the plurality of sub-monitoring results of the plurality of sub-phases are that all of the plurality of sub-phases are not abnormal, it may be determined that the current phase is not abnormal. In the case that an abnormality occurs in at least one sub-stage among the plurality of sub-monitoring results of the plurality of sub-stages, it may be determined that an abnormality occurs in the current stage.
Optionally, monitoring the current stage based on the preset rule and the data generated by the current stage to obtain a monitoring result, including: responding to the data generated in the current stage to completely meet the preset rule, and determining that the monitoring result is abnormal in the current stage; and responding to the data generated in the current stage failing to fully meet the preset rule, and determining that the monitoring result is abnormal in the current stage.
In an alternative embodiment, in the case that the data generated in the current stage all meet the preset rule, it may be determined that the monitoring result is that no abnormality occurs in the current stage. Under the condition that the data generated in the current stage cannot fully meet the preset rule, the monitoring result can be determined to be abnormal in the current stage.
Optionally, before the preset rule corresponding to the stage information is obtained from the preset rule base, the method further includes: based on the identification in the stage information, determining application scenes of different stages, wherein the application scenes comprise one of the following: the security level of the second application scene is higher than that of the first application scene; based on application scenes, determining preset rules corresponding to different stages; and constructing a preset rule base based on preset rules corresponding to different stages.
The first application scenario described above may be a low risk application scenario, for example, but not limited to, a game development scenario. The second application scenario may be a high-risk application scenario, for example, but not limited to, a resource loss scenario in the financial field. The security level of the second application scene is higher than that of the first application scene.
In an alternative embodiment, the application scenario of the different phases may also be determined first based on the identification in the phase information. For example, in the case that the current stage is the demand stage, the stage information may be acquired first, and then the identifier in the stage information may be parsed to obtain the project name of the current stage, for example, the project name of the current stage may be obtained as "x×game development", and at this time, the application scenario of the current stage may be determined to be the first application scenario, but not limited thereto. And secondly, based on application scenes, determining preset rules corresponding to different stages. For example, preset rules of different stages in different application scenes can be set, finally, a preset rule base can be constructed based on the preset rules corresponding to the different stages, for example, the preset rules of different stages in different application scenes can be summarized, and the preset rule base can be obtained.
Optionally, based on the application scenario, determining the preset rule corresponding to the different phases includes: responding to the application scene as a first application scene, and obtaining a first preset rule of different stages in the first application scene Jing Duiying based on the first weight; responding to the application scene as a second application scene, and obtaining second preset rules corresponding to different stages in the second application scene based on second weights, wherein the second weights are larger than the first weights, and the number of the second preset rules is larger than that of the first preset rules; summarizing the first preset rule and the second preset rule to obtain preset rules corresponding to different stages.
The first weight may be a weight corresponding to a first application scenario, and the second weight may be a weight corresponding to a preset rule added in a second application scenario. The newly added preset rule only exists in the second application scene. Wherein the second weight is greater than the first weight, i.e., the first weight has a duty cycle of less than 50%, and the second weight has a duty cycle of greater than or equal to 50%.
In an alternative embodiment, in the case that the application scenario is the first application scenario, the first preset rule of the different phases in the first application scenario Jing Duiying may be obtained based on the first weight. For example, a first preset rule in a first application scenario at different stages may be assigned to a corresponding weight in the first weights, so as to obtain the first preset rule.
For example, in the case that the different stage is a development stage and the application scenario is a first application scenario, the first initial preset rule may include, but is not limited to: code security scan rules, code review advance, code defect scan, code automation scan, smoking case execution and environmental deployment detection rules. The specific content of the code security scanning rule can be that the medium-high risk vulnerability is 0; code examination of the specific content in advance can submit codes for research personnel, so that 2+ personnel outside the code examination personnel can finish CR; the specific content of the code defect scan may be low-level defect=0; the code automation scan may be specific to an incremental code line coverage >80%, a branch coverage >70%; the specific content executed by the smoking case can be 100% of passing rate; the specific content of the environmental deployment detection may be 100% of the deployment service availability. At this time, the corresponding weight may be assigned to the above first initial preset rule based on the first weight.
It should be noted that, specific weight research personnel can be allocated by themselves based on actual demands, for example, the new team can be set flexibly according to the degree of the new and old development teams and the quality requirements, the new team has a compact development period and a small number of online users, and the automation weight can be reduced to 5% when the online time is faster than the quality in the initial stage of product development, but the method is not limited to this.
Optionally, in the case that the application scenario is a second application scenario, a second preset rule corresponding to the second application scenario in different stages may be obtained based on the second weight. For example, after the corresponding weights in the second weights are allocated to the second initial preset rules in the second application scenario at different stages, the second preset rules are obtained, wherein the second initial preset rules are newly added initial preset rules except the first initial preset rules, and the corresponding weights in the second weights are allocated to the newly added initial preset rules, so that the second preset rules can be obtained.
For example, in the case where the different stage is a development stage and the application scenario is a second application scenario, the second initial preset rule may include, but is not limited to: and the fund security checks the feasibility detection rule, and at the moment, the corresponding weight in the second weight can be allocated to the second initial preset rule, so that the second preset rule can be obtained. And finally, summarizing the second preset rule and the second preset rule to obtain the corresponding preset rule of different stages under different application scenes.
Optionally, obtaining the first preset rule of the different stages in the first application field Jing Duiying based on the first weight includes: setting corresponding first initial preset rules for different stages; and distributing corresponding weights to the first initial preset rule to obtain the first preset rule.
In an alternative embodiment, first, corresponding first preset rules may be set for different stages, and second, corresponding weights in the first weights may be assigned to the first preset rules, so as to obtain the first preset rules.
The invention aims to automatically solve the problems of untimely, inaccuracy, inconsistency, less closed loop and capability missing in the quality risk management in the research and development process.
FIG. 3 is a schematic diagram of an alternative development whole process access point automation, as shown in FIG. 3, software development process comprising: the system comprises a demand stage, a development stage, a test stage, a gray scale stage and an on-line stage, wherein in different stages, the stuck point evaluation device can acquire stage information of the stages, monitor the different stages based on the stage information to obtain a monitoring result, and can perform risk early warning multi-channel access under the condition that the monitoring result is abnormal in the current stage. For example, but not limited to, an early warning mail may be sent to a developer.
Fig. 4 is a workflow diagram of an alternative automatic stuck point evaluation apparatus according to an embodiment of the present invention, as shown in fig. 4, stage rule configuration is performed first, that is, multiple quality detection rules (that is, preset rules) may be set for different development stages, a preset rule base is obtained, rule stuck point thresholds and weights are set, and risk rules are quantified, and the stuck point evaluation apparatus may technically acquire quality data, that is, risk data generated by objects to be monitored in different stages may be acquired in real time, then weighting calculation is objectively performed on the acquired risk data, so as to obtain an overall risk, and finally a risk conclusion is output. The effects of objective quantification of the evaluation result, high efficiency and real time are achieved; and the technical scheme is simple in butt joint, and one-time butt joint supports multi-stage stuck points.
Optionally, the embodiment of the invention further provides an implementation technical scheme of the artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) stuck point assessment device, wherein the construction of the AI stuck point assessment mechanism is mainly to precipitate based on risk experience, train a set of risk assessment model, perform prior intervention on the research and development process based on the model, ensure that the online risk has more learning and flexibility than the pure automatic intervention effect, and the following steps are established by the AI stuck point assessment model:
Step S1, determining rule types and detection requirements: according to the rule types and requirements to be detected, such as network security rules, release rules, quality control rules and the like, the detected targets and requirements are defined.
Step S2, data collection and pretreatment: relevant data is collected for the type of rule to be detected and pre-processing, including data cleaning, normalization, etc., is performed in preparation for AI model training and testing.
Step S3, an AI model is constructed: and selecting a proper AI algorithm and model, such as a neural network, a decision tree, a support vector machine and the like, and performing model training and optimization according to a training data set so as to realize rule detection with high accuracy and generalization capability.
Step S4, rule detection and interception: and applying the trained AI model to actual data to perform rule detection and interception. And marking or intercepting the data meeting the rule requirements according to the output result of the model, and releasing or otherwise processing the data not meeting the rule requirements.
Step S5, model updating and maintenance: according to actual application conditions and feedback, the AI model is updated and maintained regularly, so that the accuracy and efficiency of rule detection and interception are improved.
The training result-based risk interception of the AI risk assessment model after future establishment can be used for risk interception of different scenes, the interception effect and the intelligence are better than the automation, but the training cost is high, and the authenticity of training data and scenes needs to be ensured.
Optionally, the embodiment of the invention also provides an application scene layering design scheme which is used for the whole daily research and development process management process, so that the standard of the research and development process is standardized, the standard is associated with quality control, and the standard is built into a research and development platform to realize process quality control of one-stop process stuck points; the quality problem is timely broadcasted and closed-loop, and the process control efficiency and risk interception in advance are greatly improved. For projects of different risk types and different stages of projects, the evaluation device and the stuck point capability also have automatic trade-off of trial scenes, and are combined with the following steps: the product online user exposes the surface, whether the product relates to fund safety, whether the product relates to large flow, whether the product relates to a leading decision and a product development period. Low risk item: the internal platform is hatched, and can be continuously built without involving external users and leading decisions. Stroke risk item: involving a small number of external users, not funding security high risk projects: to external mass user access, product data is used to lead significant decisions, to user funds security. And judging a rule group and a weight design which need to be referred by the risk level based on the project risk level and rule setting of the stuck point evaluation device, and guiding the stuck point evaluation link rule to take effect.
The main steps of the invention include risk rule storage, risk information acquisition and scheduling and risk weight calculation, and important protection is needed due to the technical realization of key technical points and quality expert experience.
The invention has the advantages that: the quality risk of each stage can be evaluated at any time for multiple times, and the risk early warning can be sent out by combining the risk rule in advance, so that the timeliness is high. The assessment mode is objective and data, and inaccuracy of manual assessment is avoided. And the assessment conclusion multi-channel full-member touch is avoided, and inconsistent assessment decision touch is avoided. And (4) carrying out next-stage access stuck point aiming at the risk which does not pass through, so as to ensure that the risk problem solves the closed loop. The stuck point capability is flexible and configurable, multiple risk rule configurations in different stages are supported, and the platform can realize multi-stage stuck point only by allowing one-time butt joint. The invention has the following effects: the problems of untimely, inaccurate, inconsistent, less closed loop and capability missing of risk reporting in quality risk management in the research and development process are solved.
Example 2
According to another aspect of the embodiment of the present invention, there is further provided a software development anomaly monitoring device, which can execute the software development anomaly monitoring method provided in the foregoing embodiment 1, and the specific implementation manner and the preferred application scenario are the same as those of the foregoing embodiment 1, and are not described herein.
FIG. 5 is a schematic diagram of a software developed anomaly monitoring device according to an embodiment of the present invention, as shown in FIG. 5, the device comprising: a first obtaining module 52, configured to obtain stage information of a current stage during a software development process, where the stage information is used to characterize an identifier of the current stage and whether the development of the current stage is completed; the second obtaining module 54 is configured to obtain, in response to completion of the current stage development, a preset rule corresponding to the stage information from a preset rule base, where different preset rules corresponding to different stages are stored in the preset rule base; the monitoring module 56 is configured to monitor the current stage based on the preset rule and the data generated in the current stage, so as to obtain a monitoring result, where the monitoring result is used to characterize whether an abnormality occurs in the current stage.
Optionally, the apparatus further comprises: the control module is used for controlling the software research and development process to enter the next stage and repeatedly acquiring stage information of the next stage in response to the monitoring result that no abnormality occurs in the current stage, monitoring the next stage based on a preset rule corresponding to the next stage and data generated in the next stage in response to the research and development of the next stage being completed, and obtaining a step of the monitoring result until the software research and development process is finished; and the output module is used for responding to the monitoring result that the current stage is abnormal, outputting abnormal alarm information and interrupting the software research and development process.
Optionally, after interrupting the software development process, the apparatus further comprises: and the auditing module is used for manually auditing the monitoring result to obtain a manual auditing result, wherein the manual auditing result is used for verifying whether the accuracy of the monitoring result is greater than or equal to a preset threshold value.
Optionally, the auditing module further includes: the termination unit is used for responding to the fact that the accuracy of the manual auditing result is larger than or equal to a preset threshold value, terminating the software research and development process and outputting abnormal alarm information; and the recovery unit is used for responding to the fact that the accuracy of the manual auditing result is smaller than a preset threshold value, recovering the software research and development process and controlling the software research and development process to enter the next stage.
Optionally, the apparatus further comprises: the sub-monitoring module is used for responding to the existence of a plurality of sub-stages in the current stage, and sequentially monitoring data generated by the plurality of sub-stages based on the research and development completion time of the plurality of sub-stages and a preset rule base to obtain a plurality of sub-monitoring results; the first determining module is used for determining that no abnormality exists in the current stage in response to the fact that the plurality of sub-monitoring results are that no abnormality exists in all the plurality of sub-stages; and the second determining module is used for determining that the current stage is abnormal in response to the fact that the plurality of sub-monitoring results are abnormal in at least one sub-stage of the plurality of sub-stages.
Optionally, the monitoring module includes: the first determining unit is used for determining that the monitoring result is abnormal in the current stage in response to the fact that all data generated in the current stage meet preset rules; and the second determining unit is used for determining that the monitoring result is abnormal in the current stage in response to the fact that the data generated in the current stage cannot fully meet the preset rule.
Optionally, before the preset rule corresponding to the stage information is obtained from the preset rule base, the device further includes: the third determining module is configured to determine application scenarios of different phases based on the identifiers in the phase information, where the application scenarios include one of the following: the security level of the second application scene is higher than that of the first application scene; a fourth determining module, configured to determine preset rules corresponding to different phases based on an application scenario; the construction module is used for constructing a preset rule base based on preset rules corresponding to different stages.
Optionally, the third determining module includes: the first processing unit is used for responding to the application scene as a first application scene and obtaining a first preset rule of different stages in the first application scene Jing Duiying based on the first weight; the second processing unit is used for responding to the application scene as a second application scene and obtaining second preset rules corresponding to different stages in the second application scene based on second weights, wherein the second weights are larger than the first weights, and the number of the second preset rules is larger than that of the first preset rules; and the summarizing unit is used for summarizing the first preset rule and the second preset rule to obtain preset rules corresponding to different stages.
Optionally, the first processing unit includes: the setting subunit is used for setting corresponding first initial preset rules for different stages; and the allocation subunit is used for allocating corresponding weights to the first initial preset rule to obtain the first preset rule.
Example 3
According to another aspect of the embodiment of the present invention, there is also provided a computer readable storage medium, where the computer readable storage medium includes a stored program, and when the program runs, the device on which the computer readable storage medium is controlled to execute the method of any one of the above steps.
Example 4
According to another aspect of embodiments of the present invention there is also provided an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the method of any of the above.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
In the foregoing embodiments of the present invention, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed technology may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, for example, may be a logic function division, and may be implemented in another manner, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.
Claims (11)
1. An anomaly monitoring method for software development, comprising:
in the process of software development, acquiring stage information of a current stage, wherein the stage information is used for representing the identification of the current stage and whether the development of the current stage is finished;
Responding to the completion of the current stage development, acquiring preset rules corresponding to the stage information from a preset rule base, wherein different preset rules corresponding to different stages are stored in the preset rule base;
and monitoring the current stage based on the preset rule and the data generated by the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether the current stage is abnormal or not.
2. The method according to claim 1, wherein the method further comprises:
controlling the software development process to enter a next stage in response to the monitoring result that no abnormality occurs in the current stage, and repeatedly acquiring the stage information of the next stage, monitoring the next stage based on a preset rule corresponding to the next stage and data generated by the next stage in response to the development of the next stage being completed, so as to obtain the monitoring result, until the software development process is finished;
And responding to the monitoring result to cause the current stage to be abnormal, outputting abnormal alarm information, and interrupting the software research and development process.
3. The method of claim 2, wherein after interrupting the software development process, the method further comprises:
and manually auditing the monitoring result to obtain a manual auditing result, wherein the manual auditing result is used for verifying whether the accuracy of the monitoring result is greater than or equal to a preset threshold value.
4. A method according to claim 3, characterized in that the method further comprises:
responding to the manual auditing result that the accuracy of the monitoring result is larger than or equal to the preset threshold value, terminating the software research and development process, and outputting abnormal alarm information;
And responding to the manual auditing result that the accuracy of the monitoring result is smaller than the preset threshold value, recovering the software research and development process, and controlling the software research and development process to enter the next stage.
5. The method according to claim 1, wherein the method further comprises:
In response to the existence of a plurality of sub-stages in the current stage, monitoring data generated by the plurality of sub-stages in sequence based on the research and development completion time of the plurality of sub-stages and the preset rule base to obtain a plurality of sub-monitoring results;
determining that the current stage is not abnormal in response to the plurality of sub-monitoring results that all of the plurality of sub-stages are not abnormal;
And determining that the current stage is abnormal in response to the plurality of sub-monitoring results that at least one sub-stage in the plurality of sub-stages is abnormal.
6. The method of claim 1, wherein monitoring the current stage based on the preset rules and the data generated by the current stage to obtain a monitoring result comprises:
Responding to the data generated in the current stage to fully meet the preset rule, and determining that the monitoring result is abnormal in the current stage;
and responding to the data generated in the current stage failing to fully meet the preset rule, and determining that the monitoring result is abnormal in the current stage.
7. The method of claim 1, wherein before acquiring the preset rule corresponding to the stage information from the preset rule base, the method further comprises:
Determining application scenes of the different phases based on the identification in the phase information, wherein the application scenes comprise one of the following: the system comprises a first application scene and a second application scene, wherein the security level of the second application scene is higher than that of the first application scene;
Determining preset rules corresponding to different stages based on the application scene;
and constructing the preset rule base based on the preset rules corresponding to the different stages.
8. The method of claim 7, wherein determining the preset rules corresponding to the different phases based on the application scenario comprises:
Responding to the application scene as the first application scene, and obtaining a first preset rule of the different stages in the first application scene Jing Duiying based on a first weight;
Responding to the application scene as the second application scene, and obtaining second preset rules corresponding to the different stages in the second application scene based on second weights, wherein the second weights are larger than the first weights, and the number of the second preset rules is larger than that of the first preset rules;
Summarizing the first preset rule and the second preset rule to obtain preset rules corresponding to different stages.
9. An anomaly monitoring device for software development, comprising:
the first acquisition module is used for acquiring phase information of a current phase in a software development process, wherein the phase information is used for representing the identification of the current phase and whether the development of the current phase is finished or not;
The second acquisition module is used for acquiring preset rules corresponding to the stage information from a preset rule base in response to the completion of the research and development of the current stage, wherein different preset rules corresponding to different stages are stored in the preset rule base;
the monitoring module is used for monitoring the current stage based on the preset rule and the data generated by the current stage to obtain a monitoring result, wherein the monitoring result is used for representing whether the current stage is abnormal or not.
10. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run controls a device in which the computer readable storage medium is located to perform the method according to any one of claims 1 to 8.
11. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to run the computer program to perform the method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410182067.5A CN118113554A (en) | 2024-02-18 | 2024-02-18 | Abnormality monitoring method and device for software development, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410182067.5A CN118113554A (en) | 2024-02-18 | 2024-02-18 | Abnormality monitoring method and device for software development, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118113554A true CN118113554A (en) | 2024-05-31 |
Family
ID=91207980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410182067.5A Pending CN118113554A (en) | 2024-02-18 | 2024-02-18 | Abnormality monitoring method and device for software development, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118113554A (en) |
-
2024
- 2024-02-18 CN CN202410182067.5A patent/CN118113554A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11748095B2 (en) | Automation of task identification in a software lifecycle | |
| US10310968B2 (en) | Developing software project plans based on developer sensitivity ratings detected from monitoring developer error patterns | |
| CN106598791B (en) | Industrial equipment fault preventive identification method based on machine learning | |
| JP2019185422A (en) | Failure prediction method, failure prediction device, and failure prediction program | |
| Hewett | Mining software defect data to support software testing management | |
| CN113327037A (en) | Model-based risk identification method and device, computer equipment and storage medium | |
| CN114549001A (en) | Method and device for training risk transaction recognition model and recognizing risk transaction | |
| CN116010066A (en) | RPA robot and implementation method | |
| CN116756021A (en) | Fault positioning method and device based on event analysis, electronic equipment and medium | |
| CN103440460A (en) | Application system change validation method and system | |
| CN105825130A (en) | Information security early-warning method and device | |
| CN101719091A (en) | Method and monitoring system for the rule-based monitoring of a service-oriented architecture | |
| CN113988690A (en) | Risk behavior monitoring method, device and equipment | |
| CN111651652B (en) | Emotion tendency identification method, device, equipment and medium based on artificial intelligence | |
| Mao et al. | A visual model-based evaluation framework of cloud-based prognostics and health management | |
| US11790249B1 (en) | Automatically evaluating application architecture through architecture-as-code | |
| Jyotish et al. | Availability analysis of safety-critical systems of nuclear power plant using ordinary differential equations and reachability graph | |
| CN118113554A (en) | Abnormality monitoring method and device for software development, storage medium and electronic equipment | |
| Kirschenmann et al. | Decision dependent stochastic processes | |
| CN115619529A (en) | Abnormal asset card processing method and device | |
| Feau et al. | A method to build a production process model prior to a process mining approach | |
| CN114722025A (en) | Data prediction method, device and equipment based on prediction model and storage medium | |
| CN109583026B (en) | Relay protection service modeling method and system based on Petri network appearance sequence | |
| Staron et al. | Industrial self-healing measurement systems | |
| JP2006018735A (en) | Coding standard observance situation monitoring system |
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 |