Risk identification method and device, computer readable storage medium and electronic equipment

Abstract

The invention discloses a risk identification method and device, a computer readable storage medium and electronic equipment. Relates to the field of artificial intelligence, and the method comprises the steps: obtaining a to-be-developed project, and obtaining a plurality of function items included in the project, and a plurality of function items included in each function item; for each function entry, constructing at least one development task corresponding to the function entry; in the project development process, according to a preset time interval, on the basis of the developed workloads of the multiple target objects for codes in the project, the development progress in the development task associated with each target object is updated; and determining a development risk value of at least one dimension based on the development progress in the plurality of development tasks, and determining a development risk level of each dimension based on the development risk value of each dimension. Through the method and the device, the problem of low accuracy of risk identification of the project development progress in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence, and more specifically, to a risk identification method, device, computer-readable storage medium, and electronic device. Background Art

[0002] The technology projects of financial institutions are important projects to promote and ensure the smooth operation of the business of financial institutions. Like other software engineering projects, the technology projects of financial institutions need to strictly control the progress of research and development and the quality of program production. At present, the risk identification of project development progress in related technologies relies on manual work, which has a strong subjective consciousness. Due to limited labor costs, it is usually determined based on the macro progress whether the project is lagging, resulting in low accuracy of risk identification, which makes it difficult for developers to adjust project work in a timely manner, so that the project may not be put into use as planned, affecting the business services of financial institutions.

[0003] Currently, no effective solution has been proposed to address the problem of low accuracy in risk identification of project development progress in related technologies. Summary of the invention

[0004] The main purpose of this application is to provide a risk identification method, device, computer-readable storage medium and electronic device to solve the problem of low accuracy in risk identification of project development progress in related technologies.

[0005] According to one aspect of an embodiment of the present invention, a risk identification method is provided, comprising: obtaining a project to be developed, and obtaining a plurality of function items included in the project, and a plurality of function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of the business functions; for each function entry, constructing at least one development task corresponding to the function entry, wherein each development task is used to record development information and development progress of at least part of the code corresponding to the function entry; during the development of the project, updating the development progress in the development tasks associated with each target object based on the developed workload of the code in the project for multiple target objects at preset time intervals; determining a development risk value of at least one dimension based on the development progress in the multiple development tasks, and determining the development risk level of each dimension based on the development risk value of each dimension, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function entry dimension, development task dimension, and the development risk value represents the lag value of the development progress.

[0006] Furthermore, the risk identification method also includes: for each target object, obtaining the design progress of the target object in the design phase of the target development task to obtain a first progress value, wherein the target development task is a development task associated with the target object; determining the coding progress of the target object in the coding phase of the target development task to obtain a second progress value; determining the testing progress of the target object in the testing phase of the target development task to obtain a third progress value; and determining the development progress in the development task associated with the target object based on at least one of the first progress value, the second progress value, and the third progress value.

[0007] Furthermore, the risk identification method also includes: determining the programs in the target development task as target programs, and counting the total number of target programs; obtaining the number of target programs that have been processed by the target object in the encoding stage of the target development task; and calculating based on the number of target programs that have been processed, the total number of programs, and the program complexity coefficient of each target program to obtain a second progress value.

[0008] Furthermore, the risk identification method also includes: determining the test cases in the target development task as target test cases, and counting the total number of target test cases; obtaining the number of target test cases that have been tested and passed by the target object in the test phase of the target development task; and calculating based on the number of target test cases that have been tested and passed, the total number of cases, and the test complexity coefficient to obtain a third progress value.

[0009] Furthermore, the risk identification method also includes: when at least one dimension includes a development task dimension, for each development task, determining the development risk value of the development task based on the development progress of the development task and a reference progress corresponding to the development task; when at least one dimension includes a function item dimension, for each function item, determining the development risk value of the function item based on the highest development risk value of the development task under the function item; when at least one dimension includes a function item dimension, for each function item, determining the development risk value of the function item based on the highest development risk value of the function items under the function item; when at least one dimension includes a project dimension, determining the development risk value of the project based on the highest development risk value of the function item.

[0010] Furthermore, the risk identification method also includes: calculating the difference between the development progress and the reference progress to obtain a target difference; and determining the development risk value of the development task according to the target difference and the importance coefficient of the development task.

[0011] Furthermore, the risk identification method also includes: taking projects, function items, function entries, and development tasks as nodes, and constructing edges between nodes based on the association relationships between projects, function items, function entries, and development tasks to obtain a tree structure diagram, wherein different levels in the tree structure diagram represent different dimensions; based on the development risk levels of projects, each function item, each function entry, and each development task, color rendering the nodes and edges in the tree structure diagram to obtain an updated tree structure diagram, wherein different development risk levels correspond to different colors; and displaying the updated tree structure diagram through the front-end interactive interface.

[0012] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a risk identification device is provided. The device includes: an acquisition module, which is used to obtain a project to be developed, and obtain multiple function items included in the project, and multiple function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of business functions; a first processing module, which is used to construct at least one development task corresponding to each function entry for each function entry, wherein each development task is used to record the development information and development progress of at least part of the code corresponding to the function entry; a second processing module, which is used to update the development progress in the development tasks associated with each target object based on the developed workload of the code in the project for multiple target objects at a preset time interval during the development process of the project; a determination module, which is used to determine the development risk value of at least one dimension based on the development progress in the multiple development tasks, and determine the development risk level of each dimension based on the development risk value of each dimension, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function entry dimension, development task dimension, and the development risk value represents the lag value of the development progress.

[0013] Furthermore, the second processing module also includes: an acquisition submodule, which is used to acquire, for each target object, the design progress of the target object in the design phase of the target development task, and obtain a first progress value, wherein the target development task is a development task associated with the target object; a first determination submodule, which is used to determine the coding progress of the target object in the coding phase of the target development task, and obtain a second progress value; a second determination submodule, which is used to determine the test progress of the target object in the test phase of the target development task, and obtain a third progress value; and a third determination submodule, which is used to determine the development progress in the development task associated with the target object based on at least one of the first progress value, the second progress value and the third progress value.

[0014] Furthermore, the first determination submodule also includes: a first statistical unit, used to determine the programs in the target development task as target programs, and to count the total number of target programs; a first acquisition unit, used to obtain the number of target programs that have been processed by the target object in the encoding stage of the target development task; a processing unit, used to calculate based on the number of target programs that have been processed, the total number of programs, and the program complexity coefficient of each target program to obtain a second progress value.

[0015] Furthermore, the second determination submodule also includes: a second statistical unit, used to determine the test cases in the target development task as target test cases, and to count the total number of target test cases; a second acquisition unit, used to obtain the number of target test cases that have been tested and passed by the target object in the test phase of the target development task; a first calculation unit, used to calculate based on the number of target test cases that have been tested and passed, the total number of cases and the test complexity coefficient to obtain a third progress value.

[0016] Furthermore, the determination module also includes: a fourth determination submodule, which is used to determine the development risk value of the development task for each development task based on the development progress of the development task and the reference progress corresponding to the development task when at least one dimension includes the development task dimension; a fifth determination submodule, which is used to determine the development risk value of the function item for each function item based on the highest development risk value of the development task under the function item when at least one dimension includes the function item dimension; a sixth determination submodule, which is used to determine the development risk value of the function item for each function item based on the highest development risk value of the function items under the function item when at least one dimension includes the function item dimension; and a seventh determination submodule, which is used to determine the development risk value of the project based on the highest development risk value of the function item when at least one dimension includes the project dimension.

[0017] Furthermore, the fourth determination submodule also includes: a second calculation unit, used to calculate the difference between the development progress and the reference progress to obtain a target difference; a determination unit, used to determine the development risk value of the development task based on the target difference and the importance coefficient of the development task.

[0018] Furthermore, the risk identification device also includes: a third processing module, which is used to take projects, function items, function entries, and development tasks as nodes, and to construct edges between nodes based on the association relationship between projects, function items, function entries, and development tasks to obtain a tree structure diagram, wherein different levels in the tree structure diagram represent different dimensions; a fourth processing module, which is used to color the nodes and edges in the tree structure diagram based on the development risk levels of projects, each function item, each function entry, and each development task to obtain an updated tree structure diagram, wherein different development risk levels correspond to different colors; an update module, which is used to display the updated tree structure diagram through a front-end interactive interface.

[0019] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer-readable storage medium is provided, and the computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the above-mentioned risk identification method.

[0020] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an electronic device is provided, the electronic device comprising a memory storing an executable program; and a processor for running the program, wherein the above-mentioned risk identification method is executed when the program is running.

[0021] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer program product is provided, including computer instructions, which implement the steps of the above-mentioned risk identification method when executed by a processor.

[0022] In an embodiment of the present application, by obtaining multiple functional items included in the project to be developed, multiple functional items included in each functional item, and constructing a corresponding development task for each functional item, effective refinement of the project content is achieved, which facilitates more accurate positioning of specific business functions, application scenarios, and specific codes. By updating the development progress in the development tasks associated with each target object based on the developed workload of the code in the project for multiple target objects during the project development process, timely and accurate determination of the code development progress is achieved. By determining the development risk value of at least one dimension based on the development progress in multiple development tasks, and determining the development risk level of each dimension based on the development risk value of each dimension, on the one hand, a quantitative assessment of the development progress risk of each dimension is achieved, and on the other hand, a comprehensive assessment of the project development progress risk from macro to micro is achieved, thereby effectively improving the accuracy of risk identification.

[0023] It can be seen that the solution of the present application achieves the purpose of conducting quantitative assessment of the project development progress risks in different dimensions, realizes the technical effect of improving the accuracy of risk identification, and solves the problem of low accuracy of risk identification of project development progress in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0025] Figure 1 is a hardware structure block diagram of a computer terminal provided according to an embodiment of the present application;

[0026] Figure 2 is a flow chart of a risk identification method provided according to an embodiment of the present application;

[0027] Figure 3 It is a schematic diagram of a project structure provided according to an embodiment of the present application;

[0028] Figure 4 is a schematic diagram of an updated tree structure diagram provided according to an embodiment of the present application;

[0029] Figure 5 is a schematic diagram of a risk identification method provided according to an embodiment of the present application;

[0030] Figure 6 is a schematic diagram of a risk identification device provided according to an embodiment of the present application;

[0031] Figure 7 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] It should be noted that the collected information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0035] Example 1

[0036] According to an embodiment of the present application, a method embodiment of risk identification is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0037] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal (or mobile device) for implementing a risk identification method. Figure 1As shown, the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0038] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0039] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the risk identification method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned risk identification method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0040] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0041] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0042] Under the above operating environment, this application provides Figure 2 The risk identification method shown. Figure 2 It is a flow chart of a risk identification method provided according to an embodiment of the present application.

[0043] Step S201, obtaining a project to be developed, and obtaining multiple function items included in the project, and multiple function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of the business functions.

[0044] Optionally, electronic devices, application systems, servers and other devices may be used as the execution entity of the present application. In this embodiment, the risk identification system is used as the execution entity to execute the above-mentioned risk identification method.

[0045] Optionally, in this embodiment, the project to be developed can be understood as a software engineering project of a financial institution. For example, the project can be a project corresponding to an application to be launched by the financial institution.

[0046] Optionally, the multiple function items included in the project and the multiple function items included in each function item can be obtained by manual splitting. Different function items correspond to different business functions. Different function items are logically independent and can be put into production separately according to the needs of the business department to create value for the business department. For example, the overseas online acquiring 3DS2.0 upgrade project can be split into overseas debit card online acquiring 3DS2.0 upgrade, overseas credit card online acquiring 3DS2.0 upgrade, overseas non-physical electronic card online acquiring 3DS2.0 upgrade and other function items. Different function items correspond to different application scenarios of business functions and can be tested separately. For example, the debit card ATM function item can be split into ATM deposit, ATM withdrawal, ATM balance inquiry, ATM card password modification and other function items.

[0047] Step S202: for each function entry, construct at least one development task corresponding to the function entry, wherein each development task is used to record development information and development progress of at least a portion of the code corresponding to the function entry.

[0048] Optionally, a development task is the smallest development unit under a function entry. Each development task contains the development information and development progress of a specific code in the function entry. The development information includes, but is not limited to: person in charge, involved programs, test cases, start time, planned completion time, importance coefficient, whether performance testing is involved, whether security testing is involved, etc. The initial value of the development progress in a development task is 0, or is empty.

[0049] Optionally, the development information can be set by the project manager, development manager and developer. For example, the project manager, development manager and developer formulate the start time and planned completion time of each task card according to the overall project plan, the workload of the task card, the dependencies between the previous and next items of the task and the resource situation of the project. The programs in the development tasks are sorted by the number of programs called by them, and different development tasks are assigned different importance coefficients of 1, 0.9, ..., 0.1 according to the first 10%, 20%, ..., 100% of their called amount. And here, a full program list library can be established first, and the importance coefficient can be directly obtained from the program list library and can be manually adjusted by the development manager. For financial institutions, concurrency and security are two important indicators. Therefore, whether performance testing and whether security testing are involved can be added to the development information to accurately describe the risk level of the development task. Among them, whether performance testing is involved can be directly obtained from the program list library and can be manually adjusted by the test manager. Similarly, whether security testing is involved is directly obtained from the program library and can be manually adjusted by the test manager.

[0050] In some embodiments, the content of an optional development task is shown in Table 1:

[0051] Table 1

[0052]

[0053] In some embodiments, the relationship between projects, functional items, functional items, and development tasks is as follows: Figure 3 As shown, Figure 3 is a schematic diagram of a project structure provided according to an embodiment of the present application. Figure 3 In the process, the project is divided into functional items, functional items, and tasks step by step.

[0054] Step S203 , during the development process of the project, at preset time intervals, based on the development workload of multiple target objects for the code in the project, the development progress in the development task associated with each target object is updated.

[0055] Optionally, after all the development tasks corresponding to the project have been built, the project enters the development phase. During the development of the project, the risk identification system can obtain the development workload of multiple developers (i.e., target objects) for the code in the project at daily, weekly, and other time intervals. The developed workload includes the progress values ​​of the developers at various stages of the development process. The progress values ​​are expressed in the form of percentages, which can be input by the developers themselves or calculated by the risk identification system based on the work content completed by the developers. Optionally, after determining the development workload of the developer, the risk identification system can update the development progress in the development task associated with the developer. For example, the progress values ​​of the developer at each stage are weighted and summed to obtain the total development progress, and then the total development progress is updated to the development progress in the development task. Optionally, the risk identification system can determine the association between the development task and the developer based on the responsible person information in the development task.

[0056] Step S204, based on the development progress in multiple development tasks, determine the development risk value of at least one dimension, and determine the development risk level of each dimension based on the development risk value of each dimension, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function entry dimension, development task dimension, and the development risk value represents the lag degree value of the development progress.

[0057] Optionally, the risk identification system may determine the development risk value of each dimension in the order of “development task-function item-function item-project”.

[0058] For example, first determine the development risk value of each development task based on the development progress of multiple development tasks, then determine the development risk value of the functional item based on the development risk value of each development task, then determine the development risk value of the functional item based on the development risk value of each functional item, and finally determine the development risk value of the project based on the development risk value of each functional item. When determining the development risk value of the previous level based on the development risk value of the next level, the average or minimum value can be used, for example, the development risk value of each functional item under the project is averaged to obtain the development risk value of the project.

[0059] Optionally, the development risk value of the development task can be determined based on the difference between the development progress in the development task and the reference progress of the development task. For example, the lower the development progress is than the reference progress, the higher the development risk value is, and the higher the development progress is than the reference progress, the lower the development risk value is.

[0060] Optionally, after determining the development risk value of at least one dimension, for each dimension, the risk identification system may determine the development risk level of the dimension based on the development risk value of the dimension. For example, if the development risk value is less than 0, the development risk level is determined to be the lowest risk level; if the development risk value is less than 0-10%, the development risk level is determined to be a low risk level; if the development risk value is 10%-20%, the development risk level is determined to be a medium risk level; if the development risk value is greater than 20%, the development risk level is determined to be a high risk level.

[0061] It should be noted that the development risk level of each dimension is also updated according to the preset time interval, that is, whenever the development progress of the development task is updated, the development risk level is also recalculated.

[0062] In an embodiment of the present application, by obtaining multiple functional items included in the project to be developed, multiple functional items included in each functional item, and constructing a corresponding development task for each functional item, effective refinement of the project content is achieved, which facilitates more accurate positioning of specific business functions, application scenarios, and specific codes. By updating the development progress in the development tasks associated with each target object based on the developed workload of the code in the project for multiple target objects during the project development process, timely and accurate determination of the code development progress is achieved. By determining the development risk value of at least one dimension based on the development progress in multiple development tasks, and determining the development risk level of each dimension based on the development risk value of each dimension, on the one hand, a quantitative assessment of the development progress risk of each dimension is achieved, and on the other hand, a comprehensive assessment of the project development progress risk from macro to micro is achieved, thereby effectively improving the accuracy of risk identification.

[0063] It can be seen that the solution of the present application achieves the purpose of conducting quantitative assessment of the project development progress risks in different dimensions, realizes the technical effect of improving the accuracy of risk identification, and solves the problem of low accuracy of risk identification of project development progress in related technologies.

[0064] In an optional embodiment, in the process of updating the development progress in the development tasks associated with each target object based on the developed workload of multiple target objects for the code in the project, the risk identification system can, for each target object, obtain the design progress of the target object in the design phase of the target development task to obtain a first progress value, wherein the target development task is the development task associated with the target object; determine the coding progress of the target object in the coding phase of the target development task to obtain a second progress value; determine the testing progress of the target object in the testing phase of the target development task to obtain a third progress value; and determine the development progress in the development task associated with the target object based on at least one of the first progress value, the second progress value, and the third progress value.

[0065] Optionally, the development phase of the code associated with the development task includes at least one of the following: a design phase, a coding phase, and a testing phase, and the design phase, the coding phase, and the testing phase are performed sequentially.

[0066] Optionally, the design phase is the initial stage of project development, and developers (i.e., target objects) need to plan the code structure and logical flow according to business requirements and functional items. The evaluation of design progress is usually based on the completion of design documents, such as use case diagrams, class diagrams, flow charts, etc. The design progress of the design phase can be input by the target object to the risk identification system, and the risk identification system can determine the progress value input by the target object for the design phase as the first progress value. The first progress value reflects the progress completion of the design phase.

[0067] Optionally, during the coding phase, developers will begin writing actual code based on the results of the design phase. The risk identification system can continuously monitor and automatically calculate the coding progress based on indicators such as the amount of code, submission frequency, and code complexity to obtain a second progress value. The coding progress can be determined based on the ratio of the complexity of the programs involved in the program inventory library and the amount of code submitted by the developer. For example, a task development involves n programs, and the developer has currently submitted m programs, each with a corresponding degree of complexity. The coding progress can be quantified by the formula (the sum of the complexity of m programs / the sum of the complexity of n programs). The second progress value reflects the progress completion of the coding phase.

[0068] Optionally, as the development task enters the testing phase, developers can perform functional, performance, and security testing on the code. The risk identification system can automatically calculate the test progress based on the execution of the test cases (such as the test pass rate and the complexity of the test cases) to obtain a third progress value. The test progress can be determined based on the complexity of the test cases and the ratio of executed test cases. For example, if a task has n test cases, m test cases have been passed, and each case has a corresponding complexity coefficient, then the test progress can be determined by the formula (the sum of the complexity of the m test cases / the sum of the complexity of the n test cases). The third progress value reflects the progress completion of the testing phase.

[0069] Optionally, after determining the first progress value, the second progress value, and the third progress value, the risk identification system may determine the development progress in the development task associated with the target object according to at least one of the first progress value, the second progress value, and the third progress value.

[0070] In some embodiments, the development progress in the development task associated with the target object is determined according to the first progress value, the second progress value, and the third progress value. For example, the calculation formula of the development progress can be expressed as:

[0071] Development progress = first progress value * PS + second progress value * PD + third progress value * PT

[0072] Among them, PS, PD, and PT represent the progress proportions of the three stages of design, coding, and testing. The three values ​​are preset by developers, PS+PD+PT=1.

[0073] It should be noted that through the above process, the progress evaluation of the development task is broken down into three specific stages: design, coding and testing. The above process not only quantifies the work progress of developers at different stages, but also integrates and calculates the overall progress of the development task, thereby providing objective and detailed data support for subsequent risk assessment, which can further improve the accuracy of risk identification.

[0074] In an optional embodiment, in the process of determining the coding progress of the target object in the coding stage of the target development task and obtaining the second progress value, the risk identification system can determine the program in the target development task as the target program, and count the total number of target programs; obtain the number of target programs that have been processed by the target object in the coding stage of the target development task; and calculate based on the number of programs of the processed target programs, the total number of programs, and the program complexity coefficient of each target program to obtain the second progress value.

[0075] During the project development process, each development task involves the writing and modification of multiple programs. Therefore, the risk identification system can identify all programs under the target development task based on the design documents written by developers during the design phase, define them as target programs, and then count the total number of these target programs.

[0076] During the project development process, developers can submit their processed target programs to the risk identification system at preset time intervals, so that the risk identification system can count the number of target programs that developers have processed in the coding phase of the target development task. For example, developers can submit the processed target program to the program list library and specify the development task to which the target program belongs when submitting it.

[0077] Optionally, the risk identification system can calculate the second progress value based on the number of programs of the aforementioned processed target programs, the total number of programs, and the program complexity coefficient of each target program, wherein the program complexity coefficient of each target program can be determined based on the design document written by the developer during the design phase. For example, a development task involves n programs P1, P2, ..., Pn, and the complexity of the programs is C1, C2, ..., Cn, respectively. The current programs P1, P2, ..., Pm have been submitted to the program list library, then the second progress value is (C1+C2+...+Cm) / (C1+C2+...+Cn).

[0078] It should be noted that, through the above method, the coding progress of the target object in the coding stage of the target development task is determined in combination with the program complexity coefficient of the target program, thereby improving the accuracy of the determined coding progress, and further improving the accuracy of risk identification.

[0079] In an optional embodiment, in the process of determining the test progress of the target object in the test phase of the target development task and obtaining the third progress value, the risk identification system can determine the test cases in the target development task as target test cases, and count the total number of target test cases; obtain the number of target test cases that have passed the test of the target object in the test phase of the target development task; and calculate based on the number of target test cases that have passed the test, the total number of cases, and the test complexity coefficient to obtain the third progress value.

[0080] In the project development process, the testing phase is a key link to ensure code quality and functional implementation. The risk identification system can identify all test cases under the target development task based on the design documents written by developers in the design phase, define them as target test cases, and then count the total number of these target test cases.

[0081] During the project development process, developers can submit their target test cases that have passed the test to the risk identification system at preset time intervals, so that the risk identification system can count the number of target test cases that have passed the test of the target object during the testing phase of the target development task.

[0082] Optionally, the risk identification system can calculate based on the number of cases of the aforementioned target test cases that have been tested, the total number of cases, and the test complexity coefficient to obtain a third progress value. Among them, the test complexity coefficient of each target test case can be determined based on the design document written by the developer during the design phase. For example, a development task involves n test cases T1, T2, ... Tn, and the test complexity coefficients of the test cases are E1, E2, ..., En respectively. The current test cases T1, T2, ..., Tm have been executed and tested and passed, then the test progress is (E1+E2+...+Em) / (E1+E2+...+En).

[0083] It should be noted that, through the above method, the test progress of the target object in the test phase of the target development task is determined in combination with the program complexity coefficient of the test case, thereby improving the accuracy of the determined test progress and further improving the accuracy of risk identification.

[0084] In an optional embodiment, in the process of determining the development risk value of at least one dimension based on the development progress in multiple development tasks, the risk identification system may, when at least one dimension includes the development task dimension, determine, for each development task, the development risk value of the development task based on the development progress of the development task and a reference progress corresponding to the development task; when at least one dimension includes the function item dimension, for each function item, determine the development risk value of the function item based on the highest development risk value of the development task under the function item; when at least one dimension includes the function item dimension, for each function item, determine the development risk value of the function item based on the highest development risk value of the function items under the function item; when at least one dimension includes the project dimension, determine the development risk value of the project based on the highest development risk value of the function item.

[0085] Optionally, in the case where at least one dimension includes a development task dimension, the risk identification system can calculate the development risk value of each development task in the project by comparing its current development progress with the reference progress corresponding to the task. The reference progress corresponding to the development task can be pre-set by the developer according to the task type, or it can be determined by the risk identification system based on the average progress data of similar tasks in the progress model experience library. The reference progress represents a standard or expected progress line, and the progress model experience library stores the progress data of completed development tasks.

[0086] In some embodiments, for a certain development task, its start time is D1 and its end time is D2, then its life cycle D=D2-D1, and the corresponding reference progress is different for different days in the life cycle. The risk identification system can determine the corresponding reference progress according to the day to which the current development progress of the development task belongs. For example, assuming that the life cycle is 3 days, the reference progress on the first day can be 33%, the reference progress on the second day can be 66%, and the reference progress on the third day can be 100%.

[0087] Optionally, when at least one dimension includes a function item dimension, the risk identification system can determine the development risk values ​​of all development tasks under the function item, and select the highest value as the development risk value of the function item. This method ensures that even if most of the development tasks within the function item progress smoothly, the high-risk status of any task can be highlighted, so that timely measures can be taken to avoid possible delays.

[0088] Optionally, when at least one dimension includes a functional item dimension, the risk identification system can determine the development risk values ​​of all functional items under the functional item, and then select the highest value as the development risk value of the functional item. This step further extends risk identification to a higher management level, helping project managers to grasp the progress risk of functional items as a whole, as well as the possible impact on the entire project.

[0089] Optionally, when at least one dimension includes a project dimension, the risk identification system can determine the development risk values ​​of all functional items under the project, and then select the highest value as the development risk value of the entire project. This value not only reflects the most serious schedule risk in the project, but also provides a key indicator to help the decision-makers of the financial institution quickly understand the overall health of the project and make corresponding resource allocation or project adjustment decisions based on this.

[0090] It should be noted that through the above process, it is possible to determine the risk value step by step starting from the most basic development task, ensuring that progress risks can be identified and responded to in a timely manner from micro to macro, thereby improving the accuracy of risk identification.

[0091] In an optional embodiment, in the process of determining the development risk value of a development task based on the development progress of the development task and the reference progress corresponding to the development task, the risk identification system can calculate the difference between the development progress and the reference progress to obtain a target difference; and determine the development risk value of the development task based on the target difference and the importance coefficient of the development task.

[0092] In some embodiments, the risk identification system can determine a reference progress corresponding to a development task based on average progress data of similar tasks in a progress model experience library, where the reference progress represents a standard or expected progress line. The progress model experience library stores progress data of completed development tasks.

[0093] For example, for a development task, its start time is D1 and end time is D2, then its life cycle D = D2-D1. Record the task progress of each day for the development task. For example, Task A is completed in 5 days. The design is completed on the first day, with a total progress of 20%. The coding is completed on the second day, with a total progress of 35%. The coding is completed on the third day, with a total progress of 60%. The testing is completed on the fourth day, with a total progress of 85%. The testing is completed on the fifth day, with a total progress of 100%. Then the content of Table 2 below is recorded in the experience database.

[0094] Table 2

[0095]

[0096]

[0097] According to the principle of entering the experience library, the last day must be the day when the test is completed and the progress is 100%, so the last item does not need to be recorded. Based on the experience library, the progress model of a life cycle development task can be obtained, the stage and average progress of each day in the life cycle, and the proportion of design, coding, and testing work can also be calculated.

[0098] Therefore, when determining the reference progress corresponding to a development task, the planned life cycle D of the development task can be calculated based on the start time D1 and the planned completion time D2 of the development task, and then the development tasks with the same life cycle D can be screened out from the progress model experience library, and the average progress of each day in the life cycle D can be calculated based on the daily development progress of the screened development tasks, so that the average progress of each day in the life cycle D can be used as the reference progress for each day in the life cycle D.

[0099] Furthermore, the risk identification system can determine the day (i.e., the day number) corresponding to the current development progress of the development task in the planned life cycle, thereby determining the average progress corresponding to the day in the life cycle as the current reference progress.

[0100] After determining the reference schedule, the risk identification system can calculate the development risk value based on the following formula:

[0101] Development risk value of development task = (reference progress - development progress) * importance coefficient;

[0102] Among them, "(reference progress - development progress)" is equivalent to the target difference; the programs in the development tasks are sorted by the number of programs called by them, and different development tasks can be given different importance coefficients of 1, 0.9, ..., 0.1 according to the first 10%, 20%, ..., 100% of their called amount. And here, a full program list library can be established first, and the importance coefficient can be directly obtained from the program list library and can be manually adjusted by the development manager.

[0103] Optionally, based on the financial institutions' consideration of the importance of security testing and performance testing, the risk identification system can also determine the development risk value of the development task based on the target difference, the importance coefficient of the development task, the performance testing results of the development task, and the security testing results of the development task.

[0104] For example, if the development task involves performance testing or security testing, the risk identification system can calculate the development risk value based on the following formula:

[0105] Development risk value of development task = (reference progress - development progress) * importance coefficient * 2;

[0106] It should be noted that by determining the development risk value of the development task in combination with the importance coefficient of the development task, the accuracy of determining the development risk value can be further improved, thereby improving the accuracy of risk identification.

[0107] In an optional embodiment, when at least one dimension includes: project dimension, function item dimension, function entry dimension, and development task dimension, after determining the development risk level of each dimension based on the development risk value of each dimension, the risk identification system can use projects, function items, function entries, and development tasks as nodes, and construct edges between nodes based on the association relationship between projects, function items, function entries, and development tasks to obtain a tree structure diagram, wherein different levels in the tree structure diagram represent different dimensions; based on the development risk level of the project, each function item, each function entry, and each development task, the nodes and edges in the tree structure diagram are color rendered to obtain an updated tree structure diagram, wherein different development risk levels correspond to different colors; and the updated tree structure diagram is displayed through the front-end interactive interface.

[0108] Optionally, the risk identification system can use projects, functional items, functional entries, and development tasks as nodes, and construct edges between nodes based on the association relationship between projects, functional items, functional entries, and development tasks to obtain a tree structure diagram. The tree structure diagram can be as follows: Figure 3 This structure diagram reflects the hierarchical relationship of project management, where the project node is at the top of the tree diagram, the function item node is the middle layer, the function item node is below the function item node, and the development task node is the terminal node at the bottom layer.

[0109] Optionally, after determining the development risk values ​​of each dimension and dividing the development risk levels accordingly, the target processing system can color-render the nodes and edges in the tree structure diagram to obtain an updated tree structure diagram. The choice of color is closely related to the development risk level, for example, green represents the lowest risk, yellow represents low risk, red represents medium risk, and black represents high risk.

[0110] After obtaining the updated tree structure diagram, the risk identification system can display the updated tree structure diagram to the project manager and team members through the front-end interactive interface so that they can understand the project progress risks in a timely manner. Figure 4 is a schematic diagram of an updated tree structure diagram provided according to an embodiment of the present application, such as Figure 4 As shown, the updated tree structure diagram can also display the development risk value corresponding to each node.

[0111] It should be noted that through the above process, a visual display of the development risk levels of various dimensions in the project is achieved, so that the project team can immediately identify areas that require focus and adjustment, respond to risks in a timely manner, optimize resource allocation, avoid project delays, and thus ensure the smooth development of financial institutions' business.

[0112] In some embodiments, Figure 5 is a schematic diagram of a risk identification method provided according to an embodiment of the present application. Figure 5 An optional application process of this embodiment is described. Figure 5 As shown, the risk identification system can obtain the project to be developed, and obtain multiple functional items included in the project, as well as multiple functional items included in each functional item, and then construct at least one development task corresponding to the project to determine the project structure of the project to be developed. After that, the project development is carried out, and the development progress of the task is determined at preset time intervals to calculate the development risk value of each dimension, and then determine the development risk level. Among them, the risk calculation can be performed in combination with the data in the progress model experience library. Optionally, after the development risk level is determined, the risk identification system can display it visually. Optionally, after the project development is completed, the progress data of the development task can be stored in the experience library to update the progress model experience library.

[0113] It can be seen that the solution of the present application achieves the purpose of conducting quantitative assessment of the project development progress risks in different dimensions, realizes the technical effect of improving the accuracy of risk identification, and solves the problem of low accuracy of risk identification of project development progress in related technologies.

[0114] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0115] Example 2

[0116] The embodiment of the present application also provides a risk identification device. It should be noted that the risk identification device of the embodiment of the present application can be used to execute the risk identification method provided by the embodiment of the present application. The risk identification device provided by the embodiment of the present application is introduced below.

[0117] According to an embodiment of the present application, a device for implementing the above risk identification method is also provided, such as Figure 6 As shown, the device comprises:

[0118] The acquisition module 601 is used to obtain a project to be developed, and obtain multiple function items included in the project, and multiple function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of the business functions;

[0119] A first processing module 602 is used to construct, for each function item, at least one development task corresponding to the function item, wherein each development task is used to record development information and development progress of at least a portion of the code corresponding to the function item;

[0120] The second processing module 603 is used to update the development progress in the development task associated with each target object based on the development workload of the code in the project for multiple target objects at preset time intervals during the development process of the project;

[0121] Determination module 604 is used to determine the development risk value of at least one dimension based on the development progress in multiple development tasks, and determine the development risk level of each dimension based on the development risk value of each dimension, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function item dimension, development task dimension, and the development risk value represents the lag degree value of the development progress.

[0122] It should be noted that the above-mentioned acquisition module 601, first processing module 602, second processing module 603 and determination module 604 correspond to steps S201 to S204 in the above-mentioned embodiment, and the examples and application scenarios implemented by the four modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned embodiment 1.

[0123] In an embodiment of the present application, by obtaining multiple functional items included in the project to be developed, multiple functional items included in each functional item, and constructing a corresponding development task for each functional item, effective refinement of the project content is achieved, which facilitates more accurate positioning of specific business functions, application scenarios, and specific codes. By updating the development progress in the development tasks associated with each target object based on the developed workload of the code in the project for multiple target objects during the project development process, timely and accurate determination of the code development progress is achieved. By determining the development risk value of at least one dimension based on the development progress in multiple development tasks, and determining the development risk level of each dimension based on the development risk value of each dimension, on the one hand, a quantitative assessment of the development progress risk of each dimension is achieved, and on the other hand, a comprehensive assessment of the project development progress risk from macro to micro is achieved, thereby effectively improving the accuracy of risk identification.

[0124] It can be seen that the solution of the present application achieves the purpose of conducting quantitative assessment of the project development progress risks in different dimensions, realizes the technical effect of improving the accuracy of risk identification, and solves the problem of low accuracy of risk identification of project development progress in related technologies.

[0125] Optionally, in the risk identification device provided in the embodiment of the present application, the second processing module also includes: an acquisition submodule, used to acquire, for each target object, the design progress of the target object in the design phase of the target development task, and obtain a first progress value, wherein the target development task is a development task associated with the target object; a first determination submodule, used to determine the coding progress of the target object in the coding phase of the target development task, and obtain a second progress value; a second determination submodule, used to determine the test progress of the target object in the test phase of the target development task, and obtain a third progress value; and a third determination submodule, used to determine the development progress in the development task associated with the target object based on at least one of the first progress value, the second progress value, and the third progress value.

[0126] Optionally, in the risk identification device provided in the embodiment of the present application, the first determination submodule also includes: a first statistical unit, used to determine the programs in the target development task as target programs, and to count the total number of target programs; a first acquisition unit, used to obtain the number of target programs that have been processed by the target object in the encoding stage of the target development task; a processing unit, used to calculate based on the number of target programs that have been processed, the total number of programs, and the program complexity coefficient of each target program to obtain a second progress value.

[0127] Optionally, in the risk identification device provided in the embodiment of the present application, the second determination submodule also includes: a second statistical unit, used to determine the test cases in the target development task as target test cases, and to count the total number of target test cases; a second acquisition unit, used to obtain the number of target test cases that have been tested and passed by the target object during the testing phase of the target development task; a first calculation unit, used to calculate based on the number of target test cases that have been tested and passed, the total number of cases, and the test complexity coefficient to obtain a third progress value.

[0128] Optionally, in the risk identification device provided in the embodiment of the present application, the determination module also includes: a fourth determination submodule, which is used to determine, for each development task, the development risk value of the development task based on the development progress of the development task and the reference progress corresponding to the development task when at least one dimension includes a development task dimension; a fifth determination submodule, which is used to determine, for each function item, the development risk value of the function item based on the highest development risk value of the development task under the function item when at least one dimension includes a function item dimension; a sixth determination submodule, which is used to determine, for each function item, the development risk value of the function item based on the highest development risk value of the function items under the function item when at least one dimension includes a function item dimension; and a seventh determination submodule, which is used to determine, for at least one dimension includes a project dimension, the development risk value of the project based on the highest development risk value of the function item.

[0129] Optionally, in the risk identification device provided in the embodiment of the present application, the fourth determination submodule also includes: a second calculation unit, used to calculate the difference between the development progress and the reference progress to obtain a target difference; a determination unit, used to determine the development risk value of the development task based on the target difference and the importance coefficient of the development task.

[0130] Optionally, in the risk identification device provided in the embodiment of the present application, the risk identification device also includes: a third processing module, which is used to take projects, function items, function entries, and development tasks as nodes, and to construct edges between nodes based on the association relationship between projects, function items, function entries, and development tasks to obtain a tree structure diagram, wherein different levels in the tree structure diagram represent different dimensions; a fourth processing module, which is used to color the nodes and edges in the tree structure diagram based on the development risk levels of projects, each function item, each function entry, and each development task to obtain an updated tree structure diagram, wherein different development risk levels correspond to different colors; an update module, which is used to display the updated tree structure diagram through a front-end interactive interface.

[0131] It should be noted that the acquisition module 601, the first processing module 602, the second processing module 603 and the determination module 604 correspond to steps S201 to S204 in Example 1, and the four modules and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in the above-mentioned Example 1. It should be noted that the above-mentioned modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above-mentioned modules may also be part of the device and may be run in the computer terminal 10 provided in Example 1.

[0132] Example 3

[0133] An embodiment of the present application may provide an electronic device, Figure 7 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 7 As shown, the electronic device may include: one or more ( Figure 7 (only one is shown) processor 1002, memory 1004, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0134] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0135] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: obtain a project to be developed, and obtain multiple function items included in the project, and multiple function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of the business functions; for each function entry, construct at least one development task corresponding to the function entry, wherein each development task is used to record the development information and development progress of at least part of the code corresponding to the function entry; during the development of the project, according to a preset time interval, based on the developed workload of the code in the project for multiple target objects, update the development progress in the development tasks associated with each target object; based on the development progress in the multiple development tasks, determine the development risk value of at least one dimension, and determine the development risk level of each dimension based on the development risk value of each dimension, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function entry dimension, development task dimension, and the development risk value represents the lag value of the development progress.

[0136] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: for each target object, obtain the design progress of the target object in the design phase of the target development task to obtain a first progress value, wherein the target development task is a development task associated with the target object; determine the encoding progress of the target object in the encoding phase of the target development task to obtain a second progress value; determine the test progress of the target object in the test phase of the target development task to obtain a third progress value; and determine the development progress in the development task associated with the target object based on at least one of the first progress value, the second progress value, and the third progress value.

[0137] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: determine the program in the target development task as the target program, and count the total number of target programs; obtain the number of target programs that have been processed by the target object in the encoding stage of the target development task; calculate based on the number of target programs that have been processed, the total number of programs, and the program complexity coefficient of each target program to obtain a second progress value.

[0138] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: determine the test cases in the target development task as target test cases, and count the total number of target test cases; obtain the number of target test cases that have been tested and passed by the target object in the test phase of the target development task; calculate based on the number of target test cases that have been tested and passed, the total number of cases, and the test complexity coefficient to obtain a third progress value.

[0139] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: when at least one dimension includes a development task dimension, for each development task, determine the development risk value of the development task based on the development progress of the development task and the reference progress corresponding to the development task; when at least one dimension includes a function item dimension, for each function item, determine the development risk value of the function item based on the highest development risk value of the development task under the function item; when at least one dimension includes a function item dimension, for each function item, determine the development risk value of the function item based on the highest development risk value of the function items under the function item; when at least one dimension includes a project dimension, determine the development risk value of the project based on the highest development risk value of the function item.

[0140] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: calculate the difference between the development progress and the reference progress to obtain the target difference; determine the development risk value of the development task based on the target difference and the importance coefficient of the development task.

[0141] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: in the case where at least one dimension includes: project dimension, function item dimension, function entry dimension, and development task dimension, after determining the development risk level of each dimension based on the development risk value of each dimension, take the project, function item, function entry, and development task as nodes, and construct the edges between the nodes based on the association relationship between the project, function item, function entry, and development task to obtain a tree structure diagram, wherein different levels in the tree structure diagram represent different dimensions; based on the development risk level of the project, each function item, each function entry, and each development task, color the nodes and edges in the tree structure diagram to obtain an updated tree structure diagram, wherein different development risk levels correspond to different colors; and display the updated tree structure diagram through the front-end interactive interface.

[0142] In an embodiment of the present application, by obtaining multiple functional items included in the project to be developed, multiple functional items included in each functional item, and constructing a corresponding development task for each functional item, effective refinement of the project content is achieved, which facilitates more accurate positioning of specific business functions, application scenarios, and specific codes. By updating the development progress in the development tasks associated with each target object based on the developed workload of the code in the project for multiple target objects during the project development process, timely and accurate determination of the code development progress is achieved. By determining the development risk value of at least one dimension based on the development progress in multiple development tasks, and determining the development risk level of each dimension based on the development risk value of each dimension, on the one hand, a quantitative assessment of the development progress risk of each dimension is achieved, and on the other hand, a comprehensive assessment of the project development progress risk from macro to micro is achieved, thereby effectively improving the accuracy of risk identification.

[0143] It can be seen that the solution of the present application achieves the purpose of conducting quantitative assessment of the project development progress risks in different dimensions, realizes the technical effect of improving the accuracy of risk identification, and solves the problem of low accuracy of risk identification of project development progress in related technologies.

[0144] It can be understood by those skilled in the art that Figure 7 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 7 The structure of the electronic device is not limited. Figure 7 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 7Different configurations are shown.

[0145] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0146] Example 4

[0147] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the risk identification method provided in the first embodiment.

[0148] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0149] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing the steps of the risk identification method.

[0150] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0151] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0152] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0153] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0154] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0155] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0156] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A risk identification method, characterized in that: include: Acquire a project to be developed, and acquire multiple function items included in the project, and multiple function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of the business functions; For each function entry, construct at least one development task corresponding to the function entry, wherein each development task is used to record development information and development progress of at least a portion of the code corresponding to the function entry; During the development of the project, at preset time intervals, based on the development workload of multiple target objects for the code in the project, the development progress in the development task associated with each target object is updated; Based on the development progress in multiple development tasks, a development risk value of at least one dimension is determined, and based on the development risk value of each dimension, a development risk level of each dimension is determined, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function entry dimension, development task dimension, and the development risk value represents the lag degree value of the development progress.

2. The method according to claim 1, characterized in that The development phase of the code associated with the development task includes at least one of the following: a design phase, a coding phase, and a testing phase, wherein, based on the development workload of the multiple target objects for the code in the project, updating the development progress in the development task associated with each target object includes: For each target object, obtaining a design progress of the target object in a design phase of a target development task to obtain a first progress value, wherein the target development task is a development task associated with the target object; Determine the coding progress of the target object in the coding phase of the target development task to obtain a second progress value; Determine the test progress of the target object in the test phase of the target development task to obtain a third progress value; The development progress in the development task associated with the target object is determined according to at least one of the first progress value, the second progress value, and the third progress value.

3. The method according to claim 2, characterized in that Determining the coding progress of the target object in the coding phase of the target development task to obtain a second progress value includes: Determine the programs in the target development task as target programs, and count the total number of programs of the target programs; Obtaining the number of target programs that have been processed by the target object in the encoding phase of the target development task; The second progress value is obtained by performing calculation based on the number of programs of the processed target programs, the total number of programs, and the program complexity coefficient of each target program.

4. The method according to claim 2, characterized in that: Determining the test progress of the target object in the test phase of the target development task to obtain a third progress value includes: Determine the test cases in the target development task as target test cases, and count the total number of the target test cases; Obtaining the number of target test cases that have passed the test of the target object in the test phase of the target development task; The third progress value is obtained by performing calculation based on the number of target test cases that have passed the test, the total number of cases, and a test complexity coefficient.

5. The method according to claim 1, characterized in that: Based on the development progress in multiple development tasks, determine the development risk value of at least one dimension, including: In a case where the at least one dimension includes a development task dimension, for each development task, determining a development risk value of the development task according to the development progress of the development task and a reference progress corresponding to the development task; In the case where the at least one dimension includes the function item dimension, for each function item, determining the development risk value of the function item according to the highest development risk value of the development task under the function item; In the case where the at least one dimension includes the function item dimension, for each function item, determining the development risk value of the function item according to the highest development risk value of the function items under the function item; In a case where the at least one dimension includes the project dimension, the development risk value of the project is determined according to the highest development risk value of the functional items.

6. The method according to claim 5, characterized in that Determining a development risk value of the development task according to the development progress of the development task and a reference progress corresponding to the development task includes: Calculating the difference between the development progress and the reference progress to obtain a target difference; A development risk value of the development task is determined according to the target difference and the importance coefficient of the development task.

7. The method according to claim 1, characterized in that In the case where the at least one dimension includes: the project dimension, the function item dimension, the function entry dimension, and the development task dimension, after determining the development risk level of each dimension based on the development risk value of each dimension, the method further includes: Taking the project, the function item, the function entry, and the development task as nodes, constructing edges between the nodes based on the association relationship between the project, the function item, the function entry, and the development task, to obtain a tree structure diagram, wherein different levels in the tree structure diagram represent different dimensions; Based on the development risk levels of the project, each functional item, each functional entry, and each development task, color rendering is performed on the nodes and edges in the tree structure diagram to obtain an updated tree structure diagram, wherein different development risk levels correspond to different colors; The updated tree structure diagram is displayed through the front-end interactive interface.

8. A risk identification device, characterized in that: include: An acquisition module, used to obtain a project to be developed, and obtain multiple function items included in the project, and multiple function entries included in each function item, wherein different function items correspond to different business functions, and different function entries correspond to different application scenarios of the business functions; A first processing module is used to construct, for each function entry, at least one development task corresponding to the function entry, wherein each development task is used to record development information and development progress of at least a portion of the code corresponding to the function entry; A second processing module is used to update the development progress in the development task associated with each target object based on the development workload of the multiple target objects for the code in the project at preset time intervals during the development process of the project; A determination module is used to determine a development risk value of at least one dimension based on the development progress in multiple development tasks, and determine the development risk level of each dimension based on the development risk value of each dimension, wherein the at least one dimension includes at least one of the following: project dimension, function item dimension, function entry dimension, development task dimension, and the development risk value represents the lag degree value of the development progress.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the risk identification method described in any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program, when running, executes the risk identification method described in any one of claims 1 to 7.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the risk identification method described in any one of claims 1 to 7 are implemented.

Images