CN-121981535-A - Project risk detection method and system based on multi-system cooperation
Abstract
The embodiment of the application provides a project risk detection method and system based on multi-system collaboration, wherein conventional window parameters of a multi-system collaboration project are configured, the conventional window parameters comprise an online review window and a conventional change window, the online review window is associated with delivery deadline, and the conventional change window is associated with project release time. And generating a delivery verification result according to the delivery time of the project business requirements included in the received delivery request of the project business requirements. And if the delivery verification result is that the verification is passed, synchronizing the delivery time of the project business requirement to the research and development requirements of each project system corresponding to the project business requirement. In the project release review stage, a release verification result is generated according to the delivery time of project business requirements, the expected online time of each research and development requirement and the project release time. And if the issued verification result is that the verification is not passed, executing risk early warning operation. The method can improve the reliability of the project release process and reduce the risk of the project release process.
Inventors
- GAN QING
- LIU YU
- CUI MEI
- ZHOU HONGLI
- CHENG TONG
Assignees
- 江苏常熟农村商业银行股份有限公司
Dates
- Publication Date
- 20260505
- Application Date
- 20260113
Claims (10)
- 1. The project risk detection method based on multi-system cooperation is characterized by comprising the following steps of: configuring conventional window parameters of a multi-system collaborative project, wherein the conventional window parameters comprise an online review window and a conventional change window, the online review window is associated with a delivery deadline, and the conventional change window is associated with a project release time; Generating a delivery verification result according to the delivery time of the project service requirement included in the received delivery request of the project service requirement, wherein the delivery verification result is determined based on whether the delivery time of the project service requirement falls in the conventional change window and/or whether the delivery time of the project service requirement exceeds the delivery deadline; If the delivery verification result is that verification is passed, synchronizing the delivery time of the project service requirement to the research and development requirements of each project system corresponding to the project service requirement, so that the delivery time of each research and development requirement is the same as the delivery time of the project service requirement; in a project release review stage, generating a release verification result according to the delivery time of the project business requirements, the estimated online time of each research and development requirement and the project release time; And if the release verification result is that the verification is not passed, executing risk early-warning operation, wherein the risk early-warning operation comprises the step of outputting risk early-warning prompt information.
- 2. The multi-system collaboration-based project risk detection method of claim 1, wherein the generating a delivery verification result according to a delivery time of the project business requirements included in the received delivery request of the project business requirements comprises: determining whether the delivery time of the project business needs exceeds the delivery deadline when the delivery time of the project business needs is within the regular change window; if the delivery time of the project business requirement does not exceed the delivery deadline, determining that the delivery verification result is verification passing; if the delivery time of the project service requirement exceeds the delivery deadline, determining that the delivery verification result is that verification is failed, and outputting second risk early warning prompt information, wherein the second risk early warning prompt information is used for prompting delivery failure; and if the delivery verification result is that the verification is not passed, if the delivery application is received, updating the delivery time of the project service requirement according to the evaluation result when the evaluation result corresponding to the delivery application is that the evaluation is passed, and updating the delivery verification result to be that the verification is passed.
- 3. The method for detecting project risk based on multi-system collaboration according to claim 1, wherein the generating a release check result according to the delivery time of the project business requirement, the estimated online time of each development requirement, and the project release time comprises: Extracting a specific time point of the delivery time of the project business requirement, a specific time point of the predicted online time of each research and development requirement and a specific time point of the project release time to obtain a time feature set; acquiring pre-dependency information and post-dependency information between the research and development requirements, and fusing the pre-dependency information and the post-dependency information with the delivery time feature and the estimated online time feature in the time feature set to obtain a fused feature set containing the dependency and the time feature; performing risk probability calculation on the fusion feature set to obtain a risk probability value corresponding to each research and development requirement; Comparing the risk probability value of each research and development requirement with a preset risk threshold value to obtain a risk judgment result of each research and development requirement, wherein the risk judgment result comprises an abnormal state and a normal state; Counting risk judging results of all the research and development requirements, and determining the number of abnormal research and development requirements with abnormal risk judging results; generating the release verification result according to the number of the abnormal research and development requirements and the risk probability value of each abnormal research and development requirement, wherein the release verification result is determined to be not passed if the number of the abnormal research and development requirements is greater than or equal to a preset number threshold value, and the release verification result is determined to be passed if the number of the abnormal research and development requirements is less than the preset number threshold value.
- 4. The method for detecting risk of project based on multi-system collaboration according to claim 3, wherein the step of calculating risk probability of the fusion feature set to obtain risk probability values corresponding to the development requirements comprises the steps of: Extracting a feature subset corresponding to each research and development requirement from the fusion feature set, wherein the feature subset comprises the expected online time feature of each research and development requirement, the dependency relationship feature between each research and development requirement, the delivery time feature of the project service requirement corresponding to each research and development requirement and the conventional change window feature of the project system corresponding to each research and development requirement; Performing numerical standardization processing on the expected online time feature, the delivery time feature and the conventional change window feature in the feature subset, and performing coding processing on the dependency relationship feature to generate an alignment feature vector with consistent dimension; Performing association analysis processing on the dependency relationship features in the alignment feature vector, calculating the dependency strength value between the development requirements, and generating a dependency relationship weight matrix, wherein the element representations in the dependency relationship weight matrix correspond to the dependency strength value between the two development requirements; Performing weighted fusion processing on the expected online time feature, the delivery time feature and the conventional change window feature in the alignment feature vector by using the dependency relation weight matrix to obtain a weighted fusion feature vector; Obtaining initial risk probability values corresponding to the research and development requirements according to the linear transformation processing of the weighted fusion feature vectors; And carrying out normalization processing on the initial risk probability value, and mapping the initial risk probability value into a preset probability interval to obtain the normalized risk probability value.
- 5. The method for detecting risk of project based on multi-system collaboration according to claim 3, wherein the generating the release verification result according to the number of abnormal development requirements and the risk probability value of each abnormal development requirement comprises: acquiring the number of the abnormal development requirements and the risk probability value of each abnormal development requirement; Sorting the risk probability values of the abnormal development demands to obtain an abnormal development demand sequence which is arranged from high to low according to the risk probability values; extracting abnormal research and development requirements corresponding to a preset number of risk probability values from the abnormal research and development requirement sequence to obtain a high-risk abnormal research and development requirement set; counting the abnormal research and development demand quantity of each project system in the high-risk abnormal research and development demand set to obtain high-risk abnormal distribution information of each project system; Combining the quantity of the abnormal development demands and the high-risk abnormal distribution information to determine the overall risk level of the multi-system collaborative project; And generating the release verification result according to the overall risk level, wherein if the overall risk level reaches a preset risk level threshold, the release verification result is determined to be not passed, and if the overall risk level does not reach the preset risk level threshold, the release verification result is determined to be passed.
- 6. The multi-system collaboration-based item risk detection method of claim 1, wherein prior to the item publication review stage, the method further comprises: Triggering a risk detection operation to determine whether each of the development requirements of each of the project systems meets a preset association rule, wherein the preset association rule comprises at least one of all of the development requirements being associated to a system release, the delivery time of each of the development requirements being the same as the delivery time of the project business requirements, no development requirements having a delivery time the same as the project release time and not associated to the system release; If the abnormal research and development requirements which do not meet the preset association rule exist, outputting third risk early warning prompt information, wherein the third risk early warning prompt information comprises the abnormal research and development requirements; And if the abnormal research and development requirements which do not meet the preset association rule do not exist, locking the delivery time of the project service requirements.
- 7. The multi-system collaboration-based project risk detection method of claim 6, wherein the triggering a risk detection operation to determine whether each of the development requirements of each of the project systems satisfies a preset association rule comprises: Acquiring associated information of each research and development requirement of each project system, wherein the associated information comprises whether the research and development requirement is associated to system release, the delivery time of the research and development requirement and whether the delivery time of the research and development requirement is the same as the project release time; Checking whether the research and development requirements are related to system release or not, and generating a first checking result; marking research and development requirements which are not related to system release according to the first checking result to obtain an unassociated research and development requirement set; checking whether the delivery time of each research and development requirement is the same as the delivery time of the project service requirement, and generating a second checking result; marking the research and development requirements with different delivery times according to the second checking result to obtain a research and development requirement set with inconsistent delivery times; Checking whether the development requirement which has the same delivery time as the project release time and is not related to the system release exists or not, and generating a third checking result; Marking the research and development requirements which have the same delivery time as the project release time and are not related to the system release according to the third checking result to obtain a research and development requirement set with the release time not related; obtaining an abnormal research and development demand set according to the unassociated research and development demand set, the inconsistent delivery time research and development demand set and the unassociated research and development demand set at the release time; if the abnormal research and development requirement set is empty, determining that each research and development requirement of each project system meets the preset association rule; and if the abnormal research and development requirement set is not empty, determining that each research and development requirement of each project system does not meet the preset association rule.
- 8. The multi-system collaboration-based item risk detection method of claim 1, wherein configuring conventional window parameters of a multi-system collaboration item comprises: Acquiring historical delivery data of all project systems associated with the multi-system collaborative project, wherein the historical delivery data comprises historical actual delivery time, historical schedule delivery time and dependency relationship information among the project systems; Performing deviation feature extraction processing on the historical delivery data to obtain historical delivery deviation distribution features of each project system; Determining a conventional change window adjustment factor for each of the project systems based on the historical delivery deviation distribution characteristics; Dynamically adjusting the initial conventional change window by using the adjustment factors to obtain candidate conventional change windows of each project system; Performing dependency conflict verification on the candidate regular change windows by combining the dependency relationship information among the historical systems, and eliminating window overlapping conflicts among the project systems; and generating and storing the conventional window parameters according to the adjusted conflict-free candidate conventional change window and an online review window associated with the adjusted conflict-free candidate conventional change window.
- 9. The multi-system collaboration-based item risk detection method of claim 8, wherein the determining a conventional change window adjustment factor for each of the item systems based on the historical delivery deviation distribution characteristics comprises: analyzing the historical delivery deviation distribution characteristics to obtain the historical delivery deviation type and deviation amplitude information of each project system, wherein the historical delivery deviation type comprises a delivery time advance deviation and a delivery time delay deviation, and the deviation amplitude information comprises deviation time length information; Carrying out statistical analysis processing on the historical delivery deviation types, and calculating the proportion of the quantity of the delivery time advance deviation to the total deviation quantity and the proportion of the quantity of the delivery time delay deviation to the total deviation quantity in each project system to obtain the distribution proportion of the historical delivery deviation types of each project system; obtaining the influence degree of the historical delivery deviation of each project system according to the distribution proportion of the historical delivery deviation types and the deviation amplitude information; determining a conventional change window adjustment direction of each project system according to the historic delivery deviation influence degree; Obtaining a conventional change window adjustment amplitude of each project system based on the adjustment direction and the historical delivery deviation influence degree; Generating the conventional change window adjustment factors of the project systems according to the conventional change window adjustment directions and the conventional change window adjustment amplitudes, wherein the conventional change window adjustment factors comprise adjustment direction identifiers and adjustment amplitude values, and the conventional change window adjustment factors are used for dynamically adjusting the initial conventional change window.
- 10. A multi-system collaboration-based item risk detection system comprising a processor and a computer-readable storage medium having stored therein machine-executable instructions that when executed by a computer implement the multi-system collaboration-based item risk detection method of any one of claims 1-9.
Description
Project risk detection method and system based on multi-system cooperation Technical Field The application relates to the technical field of computer information, in particular to a project risk detection method and system based on multi-system cooperation. Background In the operation and development process of large enterprises or organizations, project management processes take a significant role. The efficient project management flow is not only a key support for ensuring that various businesses of enterprises are successfully developed, but also an important guarantee for promoting the innovative development of the enterprises and improving the market competitiveness. The project management flow coordinates the cooperation among a plurality of roles of a business party, a project manager, a demand responsible person, a system responsible person, a production management team and the like, and ensures the orderly promotion of the whole process from the business demand to the system development and transformation and then to the final project release and online. However, the conventional project management process at present has the problems of resource preparation hasten caused by uncertain delivery versions of the systems, resource leakage of partial systems caused by unaligned demand and system responsible person distribution time, lack of risk early warning, difficulty in early perception of delay risks, rigidification of abnormal condition adjustment means and the like in practical application, so that the distribution efficiency is low, the resources are wasted, and the online risk is high. Therefore, how to improve the reliability of the project release process and reduce the risk of the project release process is a problem to be solved. Disclosure of Invention Therefore, the application aims to provide a project risk detection method and system based on multi-system cooperation, so as to improve the reliability of a project release process and reduce the risk of the project release process. In a first aspect, the present application provides a method for detecting risk of an item based on multi-system collaboration, including: configuring conventional window parameters of a multi-system collaborative project, wherein the conventional window parameters comprise an online review window and a conventional change window, the online review window is associated with a delivery deadline, and the conventional change window is associated with a project release time; Generating a delivery verification result according to the delivery time of the project service requirement included in the received delivery request of the project service requirement, wherein the delivery verification result is determined based on whether the delivery time of the project service requirement falls in the conventional change window and/or whether the delivery time of the project service requirement exceeds the delivery deadline; If the delivery verification result is that verification is passed, synchronizing the delivery time of the project service requirement to the research and development requirements of each project system corresponding to the project service requirement, so that the delivery time of each research and development requirement is the same as the delivery time of the project service requirement; in a project release review stage, generating a release verification result according to the delivery time of the project business requirements, the estimated online time of each research and development requirement and the project release time; And if the release verification result is that the verification is not passed, executing risk early-warning operation, wherein the risk early-warning operation comprises the step of outputting risk early-warning prompt information. Optionally, the generating a delivery verification result according to the delivery time of the project service requirement included in the received delivery request of the project service requirement includes: determining whether the delivery time of the project business needs exceeds the delivery deadline when the delivery time of the project business needs is within the regular change window; if the delivery time of the project business requirement does not exceed the delivery deadline, determining that the delivery verification result is verification passing; if the delivery time of the project service requirement exceeds the delivery deadline, determining that the delivery verification result is that verification is failed, and outputting second risk early warning prompt information, wherein the second risk early warning prompt information is used for prompting delivery failure; and if the delivery verification result is that the verification is not passed, if the delivery application is received, updating the delivery time of the project service requirement according to the evaluation result when the evaluation result corresponding to the deliv