CN114186894A - Project risk detection method and device, electronic equipment and storage medium - Google Patents

Project risk detection method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114186894A
CN114186894A CN202111556461.3A CN202111556461A CN114186894A CN 114186894 A CN114186894 A CN 114186894A CN 202111556461 A CN202111556461 A CN 202111556461A CN 114186894 A CN114186894 A CN 114186894A
Authority
CN
China
Prior art keywords
risk
information
project
target
development
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111556461.3A
Other languages
Chinese (zh)
Inventor
黄翰
徐娟
李晓莉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CCB Finetech Co Ltd
Original Assignee
CCB Finetech Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by CCB Finetech Co Ltd filed Critical CCB Finetech Co Ltd
Priority to CN202111556461.3A priority Critical patent/CN114186894A/en
Publication of CN114186894A publication Critical patent/CN114186894A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0635Risk analysis of enterprise or organisation activities
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/04Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Data Mining & Analysis (AREA)
  • Educational Administration (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application provides a project risk detection method, a project risk detection device, electronic equipment and a storage medium, which relate to the technical field of software engineering, wherein first project information of a target project is obtained, and the first project information is used for representing the development progress of a program code of the target project; acquiring risk information according to the first item information and a preset first identification logic, wherein the risk information comprises a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used for representing risk factors which possibly cause that program codes of the target item cannot be completed on schedule, and the weight coefficient is used for representing influence weights of the risk factors; determining risk evaluation information corresponding to the risk information based on a pre-trained prediction model, wherein the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule; according to the method, risk factors can be positioned in real time, and timeliness of project risk processing is improved.

Description

Project risk detection method and device, electronic equipment and storage medium
Technical Field
The present application relates to the field of software engineering technologies, and in particular, to a method and an apparatus for detecting a risk of a project, an electronic device, and a storage medium.
Background
Currently, with the complexity and the upsizing of a software project, the development task of one software project usually needs to be completed by cooperation of numerous developers and development groups. Therefore, development modes based on the cross-region virtual development group are increasing, and such development modes based on the virtual development group complete the planning, adjustment and execution of development tasks through a unified project management system, so as to complete the project development tasks together.
However, in the actual project development process, as the scale of the software development project gradually increases, the corresponding project management and control difficulty also gradually increases, and the management and control mode based on manual identification-submission-processing in the prior art has the problems of low efficiency, poor real-time performance and the like, which causes the problems of untimely project risk discovery and processing in the development project, further causes the problems of prolonged project delivery cycle, increased development cost, reduced project quality and the like.
Disclosure of Invention
The application provides a project risk detection method, a project risk detection device, electronic equipment and a storage medium, which are used for solving the problem that project risk discovery and processing in a development project are not timely.
In a first aspect, the present application provides a method for item risk detection, including:
acquiring first project information of a target project, wherein the first project information is used for representing the development progress of a program code of the target project; acquiring risk information according to the first project information and a preset first identification logic, wherein the risk information is used for representing risk factors which possibly cause that the program codes of the target project cannot be completed on schedule; and determining target management and control equipment corresponding to the risk information, and sending the risk information to the target management and control equipment.
In one possible implementation, the target project includes at least one development task, the development task is used for generating program codes of the target project; the risk information comprises at least one risk task, and the risk task is a development task which cannot be completed on time.
In a possible implementation manner, obtaining risk information according to the first item information and a preset first identification logic includes: acquiring resource information of each development task of the target project, wherein the resource information is used for representing currently available development resources of the development tasks; and determining a risk task according to the first project information and the resource information.
In a possible implementation manner, the determining, by the first project information, a risk task according to the first project information and the resource information includes: determining incomplete development tasks according to the development progress corresponding to each development task; and determining the risk task according to the resource information of each unfinished development task and the execution time sequence of each unfinished development task.
In a possible implementation manner, obtaining risk information according to the first item information and a preset first identification logic includes: acquiring a key time node of each development task; determining risk tasks according to the critical time nodes of the development tasks, wherein the critical time nodes comprise: a start time of the development task, and/or an end time of the development task.
In a possible implementation manner, determining the target management and control device corresponding to the risk information includes: determining risk type information corresponding to the risk information according to the risk information, wherein the risk type information is used for representing the category of risk factors corresponding to the risk information; and determining corresponding target management and control equipment according to the risk type information.
In one possible implementation, the method further includes: acquiring historical risk item data, wherein the historical risk item data comprise a plurality of groups of second item information, and the second item information represents a data group consisting of risk identification and weight coefficient and a mapping relation with the overdue completion duration of the historical item; and training a preset neural network model to be convergent based on the historical risk item data to obtain the pre-trained prediction model.
In a possible implementation manner, determining, based on the risk assessment information, a corresponding target management and control device includes: determining corresponding control level information according to the risk assessment information, wherein the control level information is used for representing the authority level for processing the risk information; determining a device network address corresponding to the authority level according to a preset device mapping relation; sending the risk information to the target management and control device, including: and sending the risk information to the target management and control equipment according to the equipment network address.
In one possible implementation, the method further includes: receiving first request information returned by the target management and control equipment, wherein the first request information represents a request for handing over the risk factors by the target management and control equipment; responding to the first request information, and sending the risk information to a superior device corresponding to the target management and control device, wherein the superior device is a management and control device with higher project management authority relative to the target management and control device.
In a second aspect, the present application provides a project risk detection apparatus, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring first project information of a target project, and the first project information is used for representing the development progress of a program code of the target project;
the generating module is used for obtaining risk information according to the first item information and a preset first identification logic, wherein the risk information comprises a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used for representing risk factors which possibly cause that program codes of the target item cannot be completed on schedule, and the weight coefficient is used for representing influence weights of the risk factors;
and the prediction module is used for determining risk evaluation information corresponding to the risk information based on a pre-trained prediction model, and the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule.
And the determining module is used for determining corresponding target management and control equipment based on the risk assessment information and sending the risk information to the target management and control equipment.
In one possible implementation, the target project includes at least one development task, the development task is used for generating program codes of the target project; the risk information comprises at least one risk task, and the risk task is a development task which cannot be completed on time.
In a possible implementation manner, the generating module is specifically configured to: acquiring resource information of each development task of the target project, wherein the resource information is used for representing currently available development resources of the development tasks; and determining a risk task according to the first project information and the resource information.
In a possible implementation manner, the first project information includes an execution timing sequence of each development task of the target project and a development progress corresponding to each development task, and the generation module is specifically configured to, when determining a risk task according to the first project information and the resource information: determining incomplete development tasks according to the development progress corresponding to each development task; and determining the risk task according to the resource information of each unfinished development task and the execution time sequence of each unfinished development task.
In a possible implementation manner, the generating module is specifically configured to: acquiring a key time node of each development task; determining risk tasks according to the critical time nodes of the development tasks, wherein the critical time nodes comprise: a start time of the development task, and/or an end time of the development task.
In a possible implementation manner, the prediction module is specifically configured to: determining risk type information corresponding to the risk information according to the risk information, wherein the risk type information is used for representing the category of risk factors corresponding to the risk information; and determining corresponding target management and control equipment according to the risk type information.
In a possible implementation manner, the determining module is specifically configured to: determining corresponding control level information according to the risk assessment information, wherein the control level information is used for representing the authority level for processing the risk information; determining a device network address corresponding to the authority level according to a preset device mapping relation; when sending the risk information to the target management and control device, the determining module is specifically configured to: and sending the risk information to the target management and control equipment according to the equipment network address.
In one possible implementation, the prediction module is further configured to: receiving first request information returned by the target management and control equipment, wherein the first request information represents a request for handing over the risk factors by the target management and control equipment; responding to the first request information, and sending the risk information to a superior device corresponding to the target management and control device, wherein the superior device is a management and control device with higher project management authority relative to the target management and control device.
In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the item risk detection method according to any one of the first aspect of the embodiments of the present application.
In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the project risk detection method according to any one of the first aspect of the embodiments of the present application.
According to a fifth aspect of embodiments herein, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the project risk detection method of any of the first aspects above.
According to the project risk detection method, the project risk detection device, the electronic equipment and the storage medium, first project information of a target project is obtained, and the first project information is used for representing the development progress of a program code of the target project; acquiring risk information according to the first item information and a preset first identification logic, wherein the risk information comprises a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used for representing risk factors which possibly cause that program codes of the target item cannot be completed on schedule, and the weight coefficient is used for representing influence weights of the risk factors; determining risk evaluation information corresponding to the risk information based on a pre-trained prediction model, wherein the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule; and determining corresponding target management and control equipment based on the risk assessment information, and sending the risk information to the target management and control equipment. By the method, the target management and control equipment which is responsible for managing and controlling the development progress of the program codes of the target project can obtain risk factors which possibly influence the progress of the target project in real time based on the risk assessment information predicted by the prediction model, so that the risk factors are timely processed, the problem that the project risk in the development project cannot be timely found is solved, the timeliness of processing the project risk is improved, the project delivery cycle is shortened, the development cost is reduced, and the project quality can be improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is an application scenario diagram of a project risk detection method according to an embodiment of the present application;
FIG. 2 is a flowchart of a project risk detection method provided in an embodiment of the present application;
fig. 3 is a flowchart of the step of determining a target management and control device corresponding to the risk information in step S103;
fig. 4 is a schematic diagram illustrating determination of concurrent risk information of a target management and control device according to an embodiment of the present application;
FIG. 5 is a flow chart of a project risk detection method provided in another embodiment of the present application;
FIG. 6 is a flowchart of one implementation of step S203 in the embodiment shown in FIG. 5;
FIG. 7 is a flowchart of another implementation manner of step S203 in the embodiment shown in FIG. 5;
fig. 8 is a schematic diagram of a mapping relationship between risk impact information and a network address according to an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of a project risk detection apparatus according to an embodiment of the present application;
FIG. 10 is a schematic view of an electronic device provided by an embodiment of the present application;
fig. 11 is a block diagram of a terminal device according to an exemplary embodiment of the present application.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The following explains an application scenario of the embodiment of the present application:
fig. 1 is an application scenario diagram of a project risk detection method provided in an embodiment of the present application, where the project risk detection method provided in the embodiment of the present application may be applied to a scenario of software project development based on a virtual development group, and exemplarily, as shown in fig. 1, an execution main body of the method provided in the embodiment of the present application may be a server, a project warehouse is deployed in the server, the server is in communication connection with terminal devices disposed in various places through a local area network or a wide area network, and each terminal device may implement uploading of data such as program codes and project documents through a project management system operating in the server, and store the data in the project warehouse. The terminal equipment with the authority can access the server through the project management system and check project data in the project warehouse, so that the overall management and control of the developed projects are realized. Certainly, in another possible implementation manner, program codes and project files of the development project are stored in a separate code server, the server communicates with the separate code server, and acquires related data of the development project through the code server, and a terminal device with authority may acquire the related data stored in the code server through a project management system operated by the server, so as to implement management and control of the development project, where the two are basically the same in other aspects except that the data storage locations are different, and a specific implementation of such an architecture is not described herein again (not shown in the drawings).
Referring to the application scenario diagram shown in fig. 1, currently, based on a development mode of a virtual development group, a project management system running in a server may implement planning, adjustment, and execution of a development task, so as to jointly complete the development task of the project. However, with the gradual increase of the scale of software development projects, the project management and control difficulty is gradually increased in the scene of the development mode of the virtual development group, in the prior art, due to the project management system in the server, terminal devices in various places are required to actively report problems occurring in the project development process, and a certain time is required to be consumed in the process; meanwhile, the responsible persons responsible for the management and control of the development project are also divided into different management authorities, under the traditional project management and organization framework, after risks appear in the project, related risk information needs to be reported layer by layer, and for larger project risks, after information is transmitted and aggregated for many times, the higher risk information can be displayed in the terminal equipment of the responsible persons corresponding to the higher level. Therefore, the management and control mode based on manual identification-submission-processing has the problems of low risk information transmission efficiency, poor real-time performance and the like, so that project risk discovery and processing in a development project are not timely, the project delivery cycle is prolonged, the development cost is increased, the project quality is reduced and the like.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a project risk detection method according to an embodiment of the present application, and as shown in fig. 2, the project risk detection method according to the embodiment includes the following steps:
step S101, acquiring first project information of the target project, wherein the first project information is used for representing the development progress of the program code of the target project.
For example, an execution subject of the project risk detection method provided by this embodiment may be a server, and referring to the application scenario diagram shown in fig. 1, a project warehouse for storing program codes and project files of a development project is deployed in the server. The project risk detection method provided by the embodiment is used for detecting the target project so as to determine whether the target project has a project risk.
Further, the target project has project information, which is descriptive information related to the target project, such as project name, project personnel, mission plan, etc. The first project information may be a configuration table preset in the server, and the server obtains the first project information by reading the configuration table.
Further, the first project information may be generated by the server according to the program codes and the project files uploaded by each terminal device, for example, a preset project schedule of the target project is preset in the server, the project schedule includes a mapping relationship between the identifier of the program code file and the development schedule of the target project, and the server determines the development schedule of the target project according to the project schedule and the identifier of the program codes uploaded by the terminal device in the current project warehouse, so as to generate the first project information. Of course, in another possible implementation manner, the first project information may also be obtained by the server by detecting a project file uploaded by a terminal device in the project warehouse, where the project file includes information representing a development progress of a program code of the target project, and further, the first project information may be obtained by the project file.
The item risk detection method provided in this embodiment may be implemented based on an application service, that is, an item risk detection service for implementing the method of this embodiment is run in a server, and after being triggered and started, the item risk detection service is always run in the server, and a first item of a target item is obtained in a preset manner, and is analyzed, where the preset manner is, for example, to sequentially perform steps of obtaining information of the first item by periodically generating a task queue.
Step S102, obtaining risk information according to the first item information and a preset first identification logic, wherein the risk information comprises risk identifiers and weight coefficients corresponding to the risk identifiers, the risk identifiers are used for representing risk factors which may cause that program codes of the target item cannot be completed on schedule, and the weight coefficients are used for representing influence weights of the risk factors.
Illustratively, after the server acquires the first project information, according to the development progress of the program codes of the target project represented by the first project information, the detection of the project risk can be realized. Specifically, one possible implementation manner of the first recognition logic is to determine the risk information according to a distance relationship between a current progress identifier of the target item and a planned progress identifier, for example, according to a current system time, the server first determines a current planned progress identifier, for example, a planned line number of program codes of the target item at the current system time, and then determines, by querying a code warehouse corresponding to the current target item, a current progress identifier, for example, an actual line number of the program codes at the current system time, and further determines whether the item risk exists. Specifically, in this case, if the actual number of lines of the program code in the current system time is less than or equal to the difference between the planned number of lines in the current system time by a number threshold, that is, the distance between the current progress mark and the planned progress mark is greater than or equal to the distance threshold, the risk factor corresponding to the risk information is "the project progress is behind". That is, when the current progress of the target project lags behind the planned progress of the project plan, the program code of the target project may not be completed on schedule, so as to generate information for representing this situation, that is, risk identification, and the specific distance relationship, that is, the number of lagged days in the above example, may be determined as the weight coefficient according to the preset mapping relationship.
For example, the first identification logic may be preset, and the risk information may be obtained by combining the first item information according to a rule represented by the first item information. Of course, it can be understood that, besides the implementation provided in this embodiment, the first identification logic has other implementation, for example, determining risk information according to the current progress identifier of the target project, the available project resources and the average daily resource amount, in which case, the risk factor corresponding to the risk information is "insufficient project resources". This is described in detail in the following examples, which are not described in detail in this example.
And S103, determining risk evaluation information corresponding to the risk information based on the pre-trained prediction model, wherein the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule.
Illustratively, the pre-trained predictive model is a model for outputting risk assessment information representing the occurrence probability that the target item cannot be completed on schedule, with risk information as input information. That is, the model may be a prediction model that predicts the overdue occurrence probability of the target item by using the risk identifier and the weight coefficient corresponding to the risk identifier as inputs, and the model may be implemented based on a neural network classification model. Therefore, before determining the risk assessment information corresponding to the risk information based on the prediction model, the method further includes a step of training the risk assessment information, and specifically, before step S103, the method further includes: acquiring historical risk item data, wherein the historical risk item data comprise a plurality of groups of second item information, and the second item information represents a data group consisting of risk identification and weight coefficient and a mapping relation with the overdue completion duration of the historical item; and training the preset neural network model to be convergent based on the historical risk item data to obtain a pre-trained prediction model.
The historical risk item data may be data generated after calculation and normalization processing are performed based on the first item information of the previous historical item, and the implementation process of the historical risk item data is similar to the manner of obtaining the risk information in the step of this embodiment, and is not described here again.
Further, based on the pre-trained prediction model, risk assessment information corresponding to different risk information may be output, and the risk assessment information may be a specific probability value, for example, 40%, 0.6, and the like. The larger the occurrence probability, the larger the overdue risk of the project, and vice versa.
And step S104, determining corresponding target control equipment based on the risk assessment information, and sending the risk information to the target control equipment.
Exemplarily, the risk assessment information can represent the overdue risk of the project, and after the risk assessment information is determined, the server needs to push the risk information to the developer user in time, so that the developer user can know the risk information in time, and corresponding measures can be taken. However, for different overdue risks, the risk information needs to be transmitted to the terminal devices with the matching permissions, specifically, after the risk evaluation information is determined by the server, the corresponding target permission level identifiers are determined according to the occurrence probability that the target items represented by the risk evaluation information cannot be completed on time, the terminal devices registered in the server all correspond to a group of terminal information including the permission level identifiers, and the server determines the corresponding target management and control device through the terminal information and the target permission level identifiers. And further sending the risk information to the target management and control equipment through a local area network or a wide area network. In another possible implementation manner, the server first obtains the current system time, and under different system times, different mapping relationships exist between the risk assessment information and the target management and control device. Based on the current system time, determining target management and control equipment corresponding to the risk assessment information, wherein a user corresponding to the target management and control equipment can be a responsible person of a target project in the current time period, and sending all risk information detected in the target project to terminal equipment (namely the target management and control equipment) corresponding to the responsible person in the current time period, so that accurate transmission of the risk information is realized.
In another possible implementation manner, as shown in fig. 3, the step of determining the target management and control device corresponding to the risk assessment information includes:
step S1041, when the occurrence probability corresponding to the risk assessment information is greater than a probability threshold, determining risk type information corresponding to the risk information according to the risk information, wherein the risk type information is used for representing the category of risk factors corresponding to the risk information;
step S1042, determining a corresponding target management and control device according to the risk type information.
For example, when the occurrence probability corresponding to the risk assessment information is smaller than a probability threshold, the risk assessment information may not be processed, and when the occurrence probability corresponding to the risk assessment information is larger than the probability threshold, the target management and control device may be further determined according to a specific risk type represented by the risk information. For example, if the risk factor is "behind project progress", the corresponding category is "project development category", and if the risk factor is "business requirement change", the corresponding category is "business requirement category". Furthermore, different risk type information corresponds to different management and control devices, and based on a preset mapping relationship, the management and control device corresponding to the risk type information in this step may be determined.
In the process of project development, project personnel of multiple levels participate from top to bottom, for example, project managers such as a project manager are responsible for management in project requirement, and technical developers such as programmers are responsible for work in program code implementation. Fig. 4 is a schematic diagram of determining concurrent air risk information of a target management and control device according to an embodiment of the present application, and as shown in fig. 4, after determining risk type information, a server represents risk factors of different types according to the risk type information and pushes the risk information to a corresponding target management and control device, as shown in the figure, the server sends risk information a representing risk factors of "project development class" to a management and control device a, and sends risk information B representing risk factors of "business requirement class" to a management and control device B, where a user on one side of the management and control device a is a project manager, and a user on one side of the management and control device B is a programmer.
When the occurrence probability corresponding to the risk assessment information is greater than the probability threshold value, the risk type information corresponding to the risk information is determined, and the target management and control equipment corresponding to the risk type information is determined, so that refined pushing of the risk information can be achieved, responsible persons of risk factors of different risk types can directly process the risk factors, the flattening degree of project development is improved, and then the risk detection and risk processing efficiency of the target project is improved.
In the embodiment, by acquiring first project information of a target project, the first project information is used for representing the development progress of a program code of the target project; acquiring risk information according to the first item information and a preset first identification logic, wherein the risk information comprises a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used for representing risk factors which possibly cause that program codes of the target item cannot be completed on schedule, and the weight coefficient is used for representing influence weights of the risk factors; determining risk evaluation information corresponding to the risk information based on a pre-trained prediction model, wherein the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule; and determining corresponding target management and control equipment based on the risk assessment information, and sending the risk information to the target management and control equipment. By the method, the target management and control equipment which is responsible for managing and controlling the development progress of the program codes of the target project can obtain risk factors which possibly influence the progress of the target project in real time based on the risk assessment information predicted by the prediction model, so that the risk factors are timely processed, the problem that the project risk in the development project cannot be timely found is solved, the timeliness of processing the project risk is improved, the project delivery cycle is shortened, the development cost is reduced, and the project quality can be improved.
Fig. 5 is a flowchart of a project risk detection method according to another embodiment of the present application, and as shown in fig. 5, the project risk detection method according to the present embodiment further refines steps S102 to S104 on the basis of the project risk detection method according to the embodiment shown in fig. 2, and then the project risk detection method according to the present embodiment includes the following steps:
step S201, acquiring first project information of a target project, wherein the first project information is used for representing the development progress of program codes of the target project, the target project comprises at least one development task, and the development task is used for generating the program codes of the target project.
Step S202, acquiring resource information of each development task of the target project, wherein the resource information is used for representing the currently available development resources of the development tasks.
Step S203, determining at least one risk task according to the first project information and the resource information, wherein the risk task is a development task which cannot be completed on time.
Illustratively, the resource information characterizes development resources possessed by each development task of the target item. Specifically, the development resources are, for example, human resources, device resources, and the like. The resource information may be information preset in the server by the user through the terminal device connected to the terminal device in communication, or may be information determined by the server based on project data stored in the project repository, such as device information, developer information, and the like. The resource information may be a set of specific values, and the resource information may be used to measure the progress speed of the development progress of the program code of each development task of the target project. The more development resources that the resource information characterizes, the shorter the time required to complete the development task. The resource information may also be in other implementation forms, such as an array, a matrix, and the like, and the advancing speed of the development progress of the program code of the development task is measured by multiple data dimensions, which is not described in detail in this embodiment.
Further, after the resource information is determined, the judgment is performed according to the currently available development resources of the development tasks represented by the resource information, and when the currently available development resources of the development tasks are low, the risk that the development tasks cannot be completed on time may occur in the development tasks, so that the development progress of each development task represented by the first project information can be combined with the corresponding resource information to determine the development tasks, namely the risk tasks, which cannot be completed on time in each development task.
In a possible implementation manner, the first project information includes an execution timing sequence of each development task of the target project and a development progress corresponding to each development task, as shown in fig. 6, an implementation manner of step S203 includes:
step S2031, determining incomplete development tasks according to the development progress corresponding to each development task.
Step S2032, determining a risk task according to the resource information of each incomplete development task and the execution timing of each incomplete development task.
Illustratively, at least one incomplete development task is determined according to the development progress corresponding to each development task, and then the time length required for completing the remaining development tasks is determined according to the resource information corresponding to each incomplete development task. It should be noted that, in the development process of the target project, there may be a dependency relationship between the development tasks, for example, in the program code corresponding to the development task B, an API interface for using the program code corresponding to the development task a is required. In this case, it is necessary to sequentially perform coding development of different development tasks according to a preset time sequence, and therefore, after the current development task is determined as the risk task, even if the subsequent development task is completed within the planning time based on the corresponding development resource, the subsequent development task is still determined as the risk task if the subsequent development task cannot be completed before the time node specified by the project plan.
In the embodiment, the risk tasks are comprehensively determined by combining the development progress corresponding to the development tasks and the corresponding resource information with the execution time sequence among the development tasks, so that the risk information is accurately evaluated, the task is adjusted in response, and each node of the target project can be completed according to the project plan.
In another possible implementation manner, as shown in fig. 7, the implementation manner of step S203 includes:
step S2033, a key time node of each development task is acquired.
Step S2034, determining risk tasks according to the key time nodes of each development task, wherein the key time nodes comprise: a start time of the development task, and/or an end time of the development task.
Illustratively, according to the starting time of each development task and/or the ending time of the development task, comparison is carried out based on a preset project plan, and the development tasks exceeding the project plan corresponding to the project plan time nodes are determined as risk tasks.
Step S204, determining a risk identifier corresponding to the risk task and a corresponding weight coefficient.
Exemplarily, after determining the risk information, the corresponding risk identifier may be determined according to the risk factor corresponding to the risk task, and this process may be implemented by a preset mapping relationship, which is not described herein again. For example, according to the risk factors of the risk task a, the risk task a is a development task on a critical path, and the subsequent development tasks are all implemented based on the output of the risk task a, so that the risk factor of each risk task included in the risk information has a large influence on the target project; on the contrary, the risk task B on the non-critical path does not affect the subsequent development task, so the degree of influence on the target project is small. Therefore, according to the cumulative sum of the influences of the risk tasks on the target item in the risk information, the influence degree of the risk factors corresponding to the risk information on the target item, namely the weight coefficient, can be determined.
Illustratively, the risk information includes task identifiers of the risk tasks and weight coefficients corresponding to the task identifiers, and the weight coefficients represent the degree of influence on the target project. The weight coefficient can be obtained by looking up a table according to the task identifier and preset development task weight information, and details are not repeated here.
Of course, it can be understood that, when the risk information includes only one development task, or the risk information is used to represent the risk factors corresponding to the whole target project, the weight coefficient represents the degree of influence of the risk factors corresponding to the risk information on the target project, which is similar to the case described in the foregoing embodiments and is not described herein again.
And S205, based on the pre-trained prediction model, generating risk assessment information according to the risk tasks and the corresponding weight coefficients, and sending the risk assessment information to the target management and control equipment, wherein the risk assessment information is used for representing the probability that the target project cannot be completed on schedule.
Illustratively, since different risk factors have different degrees of influence on the target item, according to the risk task in the risk information and the weight coefficient corresponding to each risk factor, for example, the risk information includes a risk task a and a risk task B, where the risk element corresponding to the risk task a is a, the risk element corresponding to the risk task B is B, and through preset weight coefficient information, the weight coefficient of the risk element a is 2, the weight coefficient of the risk element is 1.2, the reference value of each risk element is 1, and through the corresponding weight coefficient, the influence of different risk elements on the target item is also different. The larger the weight coefficient is, the greater the influence of the representation on the target item is, and therefore, the greater the probability that the target item cannot be completed on schedule. Therefore, according to the risk information and the weight coefficients corresponding to the risk factors, risk assessment information for representing the probability that the target project cannot be completed according to time can be generated. Specifically, based on the pre-trained prediction model, the risk evaluation information can be predicted by using the risk task (corresponding risk identifier) and the weight coefficient corresponding to each risk factor as input, which has been described in detail in the above embodiments and is not described here again.
And step S206, determining control level information corresponding to the risk assessment information, wherein the control level information is used for representing and processing the authority level of the risk information.
Step S207, determining the device network address corresponding to the permission level according to the preset device mapping relationship.
And step S208, according to the network address of the equipment, sending the risk information to the target management and control equipment.
For example, after determining the risk assessment information, for different risk assessment information, corresponding to different principals, for example, the greater the probability that the target item represented by the risk assessment information is overdue, the greater the administrative authority of the principal carrying the target item is, and therefore the risk assessment information should be sent to the management and control device matched with the level of the risk assessment information. In a possible implementation manner, the risk assessment information includes a plurality of influence probability identifiers, each influence probability identifier corresponds to one authority level identifier, each authority level identifier corresponds to one or more network addresses, the server obtains the risk assessment information, determines the authority level identifiers and the network addresses in sequence according to the influence probability identifiers in the risk assessment information, and then sends the risk information to corresponding terminal devices, namely target management devices, so that accurate pushing of the risk information is achieved.
Fig. 8 is a schematic diagram of a mapping relationship between risk assessment information and a network address provided in an embodiment of the present application, and as shown in fig. 8, exemplarily, the risk assessment information includes an influence probability identifier I, an influence probability identifier II, an influence probability identifier III, and an influence probability identifier IV, and the management and control level information includes a permission level a, a permission level B, a permission level C, and a device network address includes/admin 1,/admin 2,/admin 3. The system comprises a level identifier I, a level identifier II, a network address/admin 1 and/admin 2, a level identifier I, a level identifier II, a level identifier III, a level identifier IV, a network address/admin 1 and/admin 1, wherein the level identifier I and the level identifier II correspond to an authority level identifier A (representing that the level identifier I and the level identifier II correspond to the same authority level), the level identifier III corresponds to an authority level identifier B, the level identifier IV corresponds to an authority level identifier C, the authority level identifier A further corresponds to a network address/admin 1 and/admin 2 (representing that when the risk information corresponds to the authority level A, the risk information is simultaneously sent to the two devices of addresses/admin 1 and/admin 1), and the authority level identifier B corresponds to a network address/admin 2; the permission level identification CC corresponds to the network address/admin 3.
In the step of this embodiment, through mapping control between the risk assessment information and the network address, risk information that causes different degrees of influence on the target project can be accurately sent to the matched target management and control device, so that the corresponding project responsible person can perform real-time processing, the project responsible persons at different levels do not need to perform secondary information forwarding, and project propulsion efficiency is improved.
Further, in a possible implementation manner, the method further includes: the risk assessment information is sent to the target management and control equipment, so that a user of the target management and control equipment can know the current overall situation of the target project in real time, namely the probability that the target project cannot be completed on time, a manager of the project can directly monitor the target project in real time on the premise that the task progress in the project does not need to be analyzed one by one, and the real-time performance and the detection effect of the risk detection of the project are improved.
Step S209, receiving first request information returned by the target management and control device, where the first request information represents a request for handing over the risk factor by the target management and control device.
Step S210, in response to the first request information, sending the risk information to a higher-level device corresponding to the target management and control device, where the higher-level device is a management and control device having a higher project management authority than the target management and control device.
For example, after the risk information is sent to the target management and control device, if an operator corresponding to the target management and control device is not a responsible person corresponding to the risk information, the operator may send first request information to the server through the target management and control device to request the server to send the risk information to another management and control device. The server receives first request information returned by the target management and control equipment, responds to the first request, judges according to a user instruction or based on the steps of the embodiment again, determines a corresponding new target management and control equipment, and sends the risk information, so that secondary pushing of the risk information of the target project under the condition of inaccurate pushing is realized, the pushing of the risk information is completed as fast as possible, the automation degree of task circulation is improved, and the project risk detection efficiency is improved.
Fig. 9 is a schematic structural diagram of an item risk detection apparatus according to an embodiment of the present application, and as shown in fig. 9, an item risk detection apparatus 3 according to the embodiment includes:
the acquisition module 31 is configured to acquire first project information of a target project, where the first project information is used to represent a development progress of a program code of the target project;
the generating module 32 is configured to obtain risk information according to the first item information and a preset first identification logic, where the risk information includes a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used to represent a risk factor that may cause that a program code of a target item cannot be completed on schedule, and the weight coefficient is used to represent an influence weight of the risk factor;
and the prediction module 33 is configured to determine risk assessment information corresponding to the risk information based on the pre-trained prediction model, where the risk assessment information is used to represent an occurrence probability that the target item cannot be completed on schedule.
And the determining module 34 is configured to determine a corresponding target management and control device based on the risk assessment information, and send the risk information to the target management and control device.
In one possible implementation, the target project includes at least one development task, the development task is used for generating program codes of the target project; the risk information comprises at least one risk task, and the risk task is a development task which cannot be completed on time.
In a possible implementation manner, the generating module 32 is specifically configured to: acquiring resource information of each development task of a target project, wherein the resource information is used for representing currently available development resources of the development tasks; and determining the risk task according to the first project information and the resource information.
In a possible implementation manner, the first project information includes an execution timing sequence of each development task of the target project and a development progress corresponding to each development task, and the generating module 32 is specifically configured to, when determining the risk task according to the first project information and the resource information: determining incomplete development tasks according to the development progress corresponding to each development task; and determining the risk task according to the resource information of each incomplete development task and the execution time sequence of each incomplete development task.
In a possible implementation manner, the generating module 32 is specifically configured to: acquiring a key time node of each development task; determining risk tasks according to the key time nodes of the development tasks, wherein the key time nodes comprise: a start time of the development task, and/or an end time of the development task.
In a possible implementation, the prediction module 33 is specifically configured to: determining risk type information corresponding to the risk information according to the risk information, wherein the risk type information is used for representing the category of risk factors corresponding to the risk information; and determining corresponding target management and control equipment according to the risk type information.
Risk assessment information in one possible implementation, the determining module 34 is specifically configured to: determining corresponding control level information according to the risk assessment information, wherein the control level information is used for representing and processing the authority level of the risk information; determining a device network address corresponding to the authority level according to a preset device mapping relation; when sending the risk information to the target management and control device, the determining module 34 is specifically configured to: and sending the risk information to the target management and control equipment according to the equipment network address.
In a possible implementation, the prediction module 33 is further configured to: receiving first request information returned by the target management and control equipment, wherein the first request information represents a request of the target management and control equipment for handing over the risk factors; responding to the first request information, and sending the risk information to a superior device corresponding to the target management and control device, wherein the superior device is a management and control device with higher project management authority relative to the target management and control device.
The obtaining module 31, the generating module 32, the predicting module 33 and the determining module 34 are connected in sequence. The project risk detection apparatus 3 provided in this embodiment may execute the technical solution of the method embodiment shown in any one of fig. 2 to 8, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 10 is a schematic view of an electronic device according to an embodiment of the present application, and as shown in fig. 10, an electronic device 4 according to the embodiment includes: a processor 41, and a memory 42 communicatively coupled to the processor 41.
Wherein the memory 42 stores computer-executable instructions;
processor 41 executes computer-executable instructions stored in memory 42 to implement the project risk detection method provided in any of the embodiments corresponding to fig. 2-8 of the present application.
The memory 41 and the processor 42 are connected by a bus 43.
The relevant descriptions and effects corresponding to the steps in the embodiments corresponding to fig. 2 to fig. 8 can be understood, and are not described in detail herein.
One embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the project risk detection method provided in any one of the embodiments corresponding to fig. 2 to fig. 8 of the present application.
The computer readable storage medium may be, among others, ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
An embodiment of the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the project risk detection method provided in any embodiment of the present application corresponding to fig. 2 to fig. 8.
Fig. 11 is a block diagram of a terminal device 800, which may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc., according to an exemplary embodiment of the present application.
Terminal device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the terminal device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the terminal device 800. Examples of such data include instructions for any application or method operating on terminal device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
Power components 806 provide power to the various components of terminal device 800. Power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for terminal device 800.
The multimedia component 808 includes a screen providing an output interface between the terminal device 800 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. When the terminal device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive an external audio signal when the terminal device 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
Sensor component 814 includes one or more sensors for providing various aspects of state assessment for terminal device 800. For example, sensor assembly 814 can detect an open/closed state of terminal device 800, the relative positioning of components, such as a display and keypad of terminal device 800, sensor assembly 814 can also detect a change in position of terminal device 800 or a component of terminal device 800, the presence or absence of user contact with terminal device 800, orientation or acceleration/deceleration of terminal device 800, and a change in temperature of terminal device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
Communication component 816 is configured to facilitate communications between terminal device 800 and other devices in a wired or wireless manner. The terminal device 800 may access a wireless network based on a communication standard, such as WiFi, 3G, 4G, 5G, or other standard communication networks, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, communications component 816 further includes a Near Field Communications (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the terminal device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the methods provided by any of the embodiments of fig. 2-8 of the present application.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the terminal device 800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
An embodiment of the present application further provides a non-transitory computer-readable storage medium, where instructions in the storage medium, when executed by a processor of a terminal device, enable the terminal device 800 to perform the method provided in any embodiment corresponding to fig. 2 to 8 of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (13)

1. A method for item risk detection, the method comprising:
acquiring first project information of a target project, wherein the first project information is used for representing the development progress of a program code of the target project;
acquiring risk information according to the first item information and a preset first identification logic, wherein the risk information comprises a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used for representing risk factors which possibly cause that program codes of the target item cannot be completed on schedule, and the weight coefficient is used for representing influence weights of the risk factors;
determining risk evaluation information corresponding to the risk information based on a pre-trained prediction model, wherein the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule;
and determining corresponding target management and control equipment based on the risk assessment information, and sending the risk information to the target management and control equipment.
2. The method of claim 1, wherein the target project comprises at least one development task for generating program code of the target project; the risk information comprises at least one risk task, and the risk task is a development task which cannot be completed on time.
3. The method of claim 2, wherein obtaining risk information according to the first item information and a preset first identification logic comprises:
acquiring resource information of each development task of the target project, wherein the resource information is used for representing currently available development resources of the development tasks;
and determining a risk task according to the first project information and the resource information.
4. The method of claim 3, wherein the first project information includes an execution timing sequence of each development task of the target project and a development progress corresponding to each development task, and determining a risk task according to the first project information and the resource information includes:
determining incomplete development tasks according to the development progress corresponding to each development task;
and determining the risk task according to the resource information of each unfinished development task and the execution time sequence of each unfinished development task.
5. The method of claim 2, wherein obtaining risk information according to the first item information and a preset first identification logic comprises:
acquiring a key time node of each development task;
determining risk tasks according to the critical time nodes of the development tasks, wherein the critical time nodes comprise: a start time of the development task, and/or an end time of the development task.
6. The method according to claim 1, wherein determining the target management and control device corresponding to the risk information includes:
determining risk type information corresponding to the risk information according to the risk information, wherein the risk type information is used for representing the category of risk factors corresponding to the risk information;
and determining corresponding target management and control equipment according to the risk type information.
7. The method of claim 1, further comprising:
acquiring historical risk item data, wherein the historical risk item data comprise a plurality of groups of second item information, and the second item information represents a data group consisting of risk identification and weight coefficient and a mapping relation with the overdue completion duration of the historical item;
and training a preset neural network model to be convergent based on the historical risk item data to obtain the pre-trained prediction model.
8. The method according to claim 1, wherein determining a corresponding target management and control device based on the risk assessment information comprises:
determining corresponding control level information according to the risk assessment information, wherein the control level information is used for representing the authority level for processing the risk information;
determining a device network address corresponding to the authority level according to a preset device mapping relation;
sending the risk information to the target management and control device, including:
and sending the risk information to the target management and control equipment according to the equipment network address.
9. The method according to any one of claims 1-8, further comprising:
receiving first request information returned by the target management and control equipment, wherein the first request information represents a request for handing over the risk factors by the target management and control equipment;
responding to the first request information, and sending the risk information to a superior device corresponding to the target management and control device, wherein the superior device is a management and control device with higher project management authority relative to the target management and control device.
10. An item risk detection device, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring first project information of a target project, and the first project information is used for representing the development progress of a program code of the target project;
the generating module is used for obtaining risk information according to the first item information and a preset first identification logic, wherein the risk information comprises a risk identifier and a weight coefficient corresponding to the risk identifier, the risk identifier is used for representing risk factors which possibly cause that program codes of the target item cannot be completed on schedule, and the weight coefficient is used for representing influence weights of the risk factors;
the prediction module is used for determining risk evaluation information corresponding to the risk information based on a pre-trained prediction model, and the risk evaluation information is used for representing the occurrence probability that the target project cannot be completed on schedule;
and the determining module is used for determining corresponding target management and control equipment based on the risk assessment information and sending the risk information to the target management and control equipment.
11. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the item risk detection method of any one of claims 1 to 9.
12. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, are configured to implement the item risk detection method of any one of claims 1 to 9.
13. A computer program product comprising a computer program which, when executed by a processor, implements the item risk detection method of any one of claims 1 to 9.
CN202111556461.3A 2021-12-17 2021-12-17 Project risk detection method and device, electronic equipment and storage medium Pending CN114186894A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111556461.3A CN114186894A (en) 2021-12-17 2021-12-17 Project risk detection method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111556461.3A CN114186894A (en) 2021-12-17 2021-12-17 Project risk detection method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114186894A true CN114186894A (en) 2022-03-15

Family

ID=80544460

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111556461.3A Pending CN114186894A (en) 2021-12-17 2021-12-17 Project risk detection method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114186894A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117557086A (en) * 2023-07-05 2024-02-13 北京忠业兴达科技有限公司 Secret-related carrier supervision method, device, equipment and readable storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107679686A (en) * 2017-08-28 2018-02-09 阿里巴巴集团控股有限公司 A kind of business performs method and device
CN108428114A (en) * 2018-03-20 2018-08-21 网易(杭州)网络有限公司 Information processing method and device, storage medium, the electronic device of project
CN110929965A (en) * 2018-09-19 2020-03-27 北京国双科技有限公司 Project risk assessment method and device
CN112465011A (en) * 2020-11-25 2021-03-09 平安医疗健康管理股份有限公司 Project risk prediction method and system based on project research and development process

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107679686A (en) * 2017-08-28 2018-02-09 阿里巴巴集团控股有限公司 A kind of business performs method and device
CN108428114A (en) * 2018-03-20 2018-08-21 网易(杭州)网络有限公司 Information processing method and device, storage medium, the electronic device of project
CN110929965A (en) * 2018-09-19 2020-03-27 北京国双科技有限公司 Project risk assessment method and device
CN112465011A (en) * 2020-11-25 2021-03-09 平安医疗健康管理股份有限公司 Project risk prediction method and system based on project research and development process

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117557086A (en) * 2023-07-05 2024-02-13 北京忠业兴达科技有限公司 Secret-related carrier supervision method, device, equipment and readable storage medium
CN117557086B (en) * 2023-07-05 2024-03-26 北京忠业兴达科技有限公司 Secret-related carrier supervision method, device, equipment and readable storage medium

Similar Documents

Publication Publication Date Title
CN110209952B (en) Information recommendation method, device, equipment and storage medium
US11561837B2 (en) Resource processing method and apparatus for mobile terminal, computer device and storage medium
CN111338910B (en) Log data processing method, log data display method, log data processing device, log data display device, log data processing equipment and log data storage medium
US10248855B2 (en) Method and apparatus for identifying gesture
US20180342029A1 (en) Method, apparatus terminal device, and computer readable storage medium for invoking a virtual public transport card
CN110969072B (en) Model optimization method, device and image analysis system
CN111143608A (en) Information pushing method and device, electronic equipment and storage medium
CN114760339A (en) Fault prediction method, apparatus, device, medium, and product
CN106021072A (en) Information display method and device
CN112256563A (en) Android application stability testing method and device, electronic equipment and storage medium
CN111338971A (en) Application testing method and device, electronic equipment and storage medium
CN114186894A (en) Project risk detection method and device, electronic equipment and storage medium
CN108012258B (en) Data traffic management method and device for virtual SIM card, terminal and server
CN114896165A (en) Testing method and device of conversation robot system, electronic equipment and storage medium
CN114780334A (en) Power consumption monitoring method, power consumption monitoring device and storage medium
CN114066370A (en) Inventory service calling method, device, equipment, storage medium and program product
CN111526084A (en) Information processing method, device, equipment and storage medium
CN105224336A (en) Information list generates method and apparatus, smart machine
CN112102081B (en) Method, device, readable storage medium and blockchain network for generating blockchain
CN115665224A (en) Data transmission method, device and equipment based on cloud data warehouse and storage medium
CN110750355B (en) Control system, control method and device
EP4180987A1 (en) Multimodal data sending method and apparatus, and multimodal data processing method and apparatus
CN114416038A (en) Code branch processing method and device, electronic equipment and storage medium
CN114168244A (en) Information processing method and device, electronic equipment and storage medium
CN115658476A (en) Automatic testing method and device, electronic equipment and storage medium

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