A software development requirement launch risk identification method, device, equipment and medium

By identifying the matching of the requirements plan and code function points during the software development process, timely warning and adjusting the development plan, the risk of demand delayed launch is solved, ensuring the stability and reliability of software development, and reducing rework costs.

CN118569654BActive Publication Date: 2024-11-12湖南长银五八消费金融股份有限公司
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
CN202411053489.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-02
Publication Date
2024-11-12
Estimated Expiration
2044-08-02

AI Technical Summary

Technical Problem

During the software development process, the risk of delayed demand online is often discovered in the later stages, resulting in business impact. How to identify and warn in time at different development stages to avoid such situations.

Method used

By obtaining the requirements plan of the software development project, we judge whether the expected online time is reasonable, extract the requirements function points and the code function points for matching inspection. If it does not match, it will trigger the online risk warning to ensure that the requirements and code functions are consistent, and adjust the development plan in a timely manner.

Benefits of technology

Discover the time conflicts and function mismatch problems of demand planning in advance, avoid failure or rework caused by rushing online, improve software stability and reliability, optimize resource allocation and task arrangement, and reduce rework costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118569654B_ABST
    Figure CN118569654B_ABST
Patent Text Reader

Abstract

The present application discloses a method, apparatus, device and medium for identifying risks in launching software development requirements, and relates to the field of risk identification technology, including: obtaining a demand plan for a software development project, and determining whether a first expected launch time in the demand plan is earlier than a second expected launch time determined after evaluating the development workload; if so, triggering a software development demand launch risk warning, prompting a redefinition of the second expected launch time and the first expected launch time; if not, extracting and recording demand function points filled in based on a preset demand function template from the demand plan to obtain a demand function list, and reading and saving developed code function points from the development code of the software development project to obtain a code function list; if a circular matching result of the demand function list and the code function list is a matching result in which a list record of the demand function list does not match a list record of the code function list, triggering a software development demand launch risk warning.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of risk identification technology, and in particular to a method, device, equipment and medium for identifying risks of software development requirements going online. Background Art

[0002] At present, the entire life cycle of software development for products or business needs has been digitally managed, including the demand stage, development stage, and testing stage, and the entire process of project flow is managed in the project management system. Daily iterative development is basically based on one demand dimension, from the business demand personnel proposing the demand to development, testing, and online, forming a closed loop. The demand development process is a long link with many influencing factors. It is often easy to discover the risk of delayed launch of the demand in the later stage, but the business party often urgently needs to launch the demand to solve the actual business needs. How to avoid such situations and realize risk identification at different stages of the software development project, so as to timely discover the online risks and notify personnel to adjust, so as to avoid various problems that are discovered near the online stage and cause business impacts that cannot be launched as planned. Summary of the invention

[0003] In view of this, the purpose of the present invention is to provide a method, device, equipment and medium for identifying risks in software development requirements, which can identify risks at different stages of software development projects, automatically identify risks and issue timely warnings. The specific scheme is as follows:

[0004] In a first aspect, the present application discloses a method for identifying risks in software development requirements launch, comprising:

[0005] Obtaining a demand plan for a software development project, and determining whether a first expected launch time of the demand plan is earlier than a second expected launch time determined after evaluating the development workload;

[0006] If so, a risk warning for the launch of the software development requirement is triggered, and a prompt is given to re-formulate the second expected launch time and the first expected launch time;

[0007] If not, extract and record the required function points filled in based on the preset required function template from the required plan to obtain a required function list, and read and save the developed code function points from the development code of the software development project to obtain a code function list;

[0008] If the circular matching result of the requirement function list and the code function list is a matching result in which the list records of the requirement function list do not match the list records of the code function list, a risk warning for the online launch of the software development requirement is triggered.

[0009] Optionally, before extracting and recording the required function points filled in based on the preset required function template from the required plan to obtain the required function list, the method further includes:

[0010] Build a preset requirement function template including title bar and title content;

[0011] Fill in each demand function point according to the preset demand function template to obtain the corresponding demand plan;

[0012] Among them, the title bar is the required function identifier and digital symbols, and the title content is the functional description of the required function point.

[0013] Optionally, extracting and recording the demand function points filled in based on the preset demand function template from the demand plan to obtain a demand function list includes:

[0014] Parsing and checking the demand plan using natural language processing technology, and determining whether a title bar exists in the parsed plan document;

[0015] If there is a title bar, extract and record the required function points filled in based on the preset required function template from the plan document to obtain a required function list;

[0016] If the title bar does not exist, the extraction of required function points will be stopped, and the online risk warning of the software development requirements will be triggered.

[0017] Optionally, if the title bar exists, the required function points filled in based on the preset required function template are extracted from the plan document and recorded to obtain a required function list, including:

[0018] If a title bar exists, the title content corresponding to the title bar is identified from the plan document, and one or more corresponding required function points are formed and recorded according to the title content to obtain a required function list.

[0019] Optionally, the step of reading and saving developed code function points from the development code of the software development project to obtain a code function list includes:

[0020] Set a target annotation for identifying the method name, add a corresponding target annotation to each method name in the development code, and add the code function developed by the development code under each method name described by the Chinese annotation after the target annotation; wherein the Chinese annotation is consistent with the function description in the demand plan;

[0021] Identify whether each method name in the development code of the software development project references the target annotation. If so, read and save the Chinese annotation on the corresponding method name to obtain a code function list.

[0022] Optionally, if the circular matching result of the requirement function list and the code function list is a matching result in which the list record of the requirement function list does not match the list record of the code function list, triggering an online risk warning of the software development requirement includes:

[0023] Read the number of required function points in the required function list and the number of code function points in the code function list;

[0024] If the number of required function points is greater than the number of code function points, a risk warning for the launch of the software development requirement is triggered;

[0025] If the number of required function points is less than or equal to the number of code function points, all list records in the required function list are determined as list records to be matched, and each list record in the code function list is looped through one by one to detect whether the list record in the code function list is matched with the list record to be matched;

[0026] If the result of the circular matching is a matching result in which the to-be-matched list record of the requirement function list does not match any list record of the code function list, a risk warning for the online launch of the software development requirement is triggered.

[0027] Optionally, the software development requirement launch risk identification method further includes:

[0028] When the code development is completed, check whether the number of abnormal data of the required function type in the program abnormal data exceeds the preset abnormal number threshold;

[0029] If the preset abnormal number threshold is exceeded, the online risk warning of the software development requirements will be triggered.

[0030] In a second aspect, the present application discloses a software development requirement launch risk identification device, comprising:

[0031] A time judgment module is used to obtain a demand plan for a software development project and judge whether a first expected launch time of the demand plan is earlier than a second expected launch time determined after evaluating the development workload;

[0032] a prompt trigger module, configured to trigger a risk prompt for the launch of the software development requirement, and prompt the user to re-formulate the second expected launch time and the first expected launch time;

[0033] A list acquisition module is used to extract and record the required function points filled in based on the preset required function template from the demand plan to obtain a required function list, and read and save the developed code function points from the development code of the software development project to obtain a code function list;

[0034] The function point matching module is used to trigger the online risk warning of the software development requirements if the circular matching result of the requirement function list and the code function list is a matching result in which the string information of the requirement function list does not match the string information of the code function list.

[0035] In a third aspect, the present application discloses an electronic device, comprising:

[0036] Memory, used to store computer programs;

[0037] A processor is used to execute the computer program to implement the steps of the software development requirement online risk identification method disclosed above.

[0038] In a fourth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned software development requirement online risk identification method are implemented.

[0039] It can be seen that the present application discloses a method for identifying the risk of software development demand launch, including: obtaining the demand plan of the software development project, and judging whether the first expected launch time of the demand plan is earlier than the second expected launch time determined after evaluating the development workload; if so, triggering the launch risk prompt of the software development demand, and prompting to re-formulate the second expected launch time and the first expected launch time; if not, extracting and recording the demand function points filled in based on the preset demand function template from the demand plan to obtain the demand function list, and reading and saving the developed code function points from the development code of the software development project to obtain the code function list; if the circular matching result of the demand function list and the code function list is that there is a matching result that the list record of the demand function list does not match the list record of the code function list, then triggering the software development demand launch risk prompt. It can be seen that the possible conflict of the expected launch time of the demand plan can be discovered in advance, and timely adjustments can be made to avoid problems caused by rushing to launch due to time constraints. Ensure that the demand function matches the developed code function to reduce the situation where the function is missing or wrong after launching. Strict functional matching checks can help develop software that better meets requirements and improve software stability and reliability. The clear correspondence between required functions and code functions makes it easier for project managers to track and monitor effectively. Timely risk warnings can also enable project teams to respond quickly, optimize resource allocation and task scheduling, and reduce the cost of rework and repairs due to launch failures or functional mismatches. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0041] Figure 1 A flow chart of a method for identifying risks in software development requirements online disclosed in this application;

[0042] Figure 2 A timing diagram of a method for identifying risks in various stages of software development requirements disclosed in this application;

[0043] Figure 3 This is a schematic diagram of the structure of a software development demand online risk identification device disclosed in this application;

[0044] Figure 4 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0046] At present, the entire life cycle of software development for products or business needs has been digitally managed, including the demand stage, development stage, and testing stage, and the entire process of project flow is managed in the project management system. Daily iterative development is basically based on one demand dimension, from the business demand personnel proposing the demand to development, testing, and online, forming a closed loop. The demand development process is a long link with many influencing factors. It is often easy to discover the risk of delayed launch of the demand in the later stage, but the business party often urgently needs to launch the demand to solve the actual business needs. How to avoid such situations and realize risk identification at different stages of the software development project, so as to timely discover the online risks and notify personnel to adjust, so as to avoid various problems that are discovered near the online stage and cause business impacts that cannot be launched as planned.

[0047] To this end, the present invention provides a software development demand online risk identification solution, which can perform risk identification at different stages of a software development project, automatically identify risks and provide timely warnings.

[0048] Reference Figure 1As shown, an embodiment of the present invention discloses a method for identifying risks of software development requirements going online, including:

[0049] Step S11: Obtain a demand plan for a software development project, and determine whether a first expected launch time of the demand plan is earlier than a second expected launch time determined after evaluating the development workload.

[0050] In this embodiment, in the process of determining the risk of software development project launch, refer to Figure 2 As shown, the business personnel first write the business requirements corresponding to the software development project and submit them to the requirements analyst. Then, the business personnel, requirements analysts, developers and testers organize meetings to clarify and analyze the requirements, so that the development and testing can fully understand the requirements and sort out the functional development points. In the requirement proposal stage, the requirements analyst establishes the requirement tasks in the project management system to form the basic data of the requirement plan, so that when the requirements are automatically identified for the online risk, the requirements plan of the software development project can be obtained from the project management system. The requirement plan specifically includes: requirement number, requirement name, priority (urgent, high, medium, low), development person in charge, test person in charge, current stage, expected working hours, actual working hours, business expected online time (first expected online time) and other basic data.

[0051] Further, see Figure 2 As shown, requirements are clarified during the project development and coding phase. After the requirements are clarified, developers will sort out the functions and evaluate the workload. They will fill in the estimated working hours of the requirements plan in the system to obtain the IT expected launch time (the second expected launch time), and then proceed with coding development. When the development is completed, the system modifies the requirements plan to test, and the system automatically calculates the actual working hours and updates the actual working hours of the requirements plan to obtain the actual launch time and whether the requirements launch is delayed.

[0052] It should be noted that in the development and coding stage, after obtaining the second expected online time, it is directly determined whether the first expected online time is earlier than the second expected online time, so as to evaluate whether there is a conflict between the second expected online time in the development and coding process and the first expected online time in the demand proposal stage, and obtain the corresponding plan evaluation result.

[0053] Step S12: If yes, triggering the online risk reminder of the software development requirement, and prompting to re-formulate the second expected online time and the first expected online time.

[0054] In this embodiment, because the development of software business usually depends on the support of the launch of related software projects. If the first expected launch time set in the demand plan cannot be launched on time, the business process may be blocked, resulting in the business being unable to proceed according to the scheduled plan. Figure 2 As shown in the figure, if the plan evaluation result is that the first expected launch time is earlier than the second expected launch time, the "plan conflict" monitoring is triggered, and the system automatically generates a risk warning record to prompt relevant stakeholders to discuss and re-evaluate, and analyze the reasons and actual situation for not meeting business requirements, such as: the development workload is indeed large, the plan evaluation is too redundant, and there are not enough developers, etc., to avoid business personnel waiting for the launch with great expectations, and finally knowing that it cannot be launched as scheduled when the launch is approaching, because the single information asymmetry brings mutual goals and responsibilities. It should be noted that the first expected launch time and the second expected launch time are regular monitoring indicators. In addition, other regular monitoring indicators can be set to further monitor the risk of demand launch in multiple dimensions, such as: the number of changes to the first requirement in the demand plan and the number of changes to the second requirement in the development coding stage, the first development resources (manpower, time, technical equipment, etc.) pre-planned in the demand plan and the second development resources in the actual development coding stage during the project development process. Such single regular monitoring indicators support configuration. The basic elements of regular monitoring indicator configuration are regular monitoring indicator name, indicator monitoring rules, reminder method, whether to enable, etc., and support dynamic increase and decrease. The system automatically reads the configuration list and performs automatic monitoring and automatic warning according to the indicator monitoring rules.

[0055] For example: If the requirements of a project change too frequently during the development process, it may cause delays in the development schedule, increase costs, and even affect the quality of the final product. Therefore, the name of the general monitoring indicator: Frequency of requirement changes, indicator monitoring rules: Count the number of requirement changes within a certain period of time (number of second requirement changes), and calculate the average number of changes per week or month (number of first requirement changes). Reminder method: When the number of second requirement changes exceeds the set threshold (such as more than 3 times per week), a reminder will be issued via email and system pop-up window. Among them, the set threshold is determined based on the number of first requirement changes. Enabled: Enabled.

[0056] Step S13: If not, extract and record the demand function points filled in based on the preset demand function template from the demand plan to obtain a demand function list, and read and save the developed code function points from the development code of the software development project to obtain a code function list.

[0057] In this embodiment, if the plan evaluation result is that the first expected online time is later than the second expected online time, it means that after the conventional monitoring indicators pass the risk identification monitoring, the demand deviation indicators are further monitored. The demand deviation indicator is a key factor for going online. If it is later discovered that the demand has deviated, it will lead to rework and the progress will be seriously delayed. Therefore, the sooner the demand deviation is discovered, the better. However, it is particularly difficult for the demand deviation indicator to be automatically identified by the system. The main reason for the deviation in demand is that the developers do not understand the demand in place or there are legacy issues in the development process. It is a difficult problem to judge whether the demand has been fully realized. Real-time monitoring of the entire stage is required to ensure that the deviation is minimized. For details, refer to Figure 2 As shown, the development coding phase and the testing phase are monitored in multiple dimensions: the demand function points in the demand plan are monitored and matched with the code function points in the development code, and the bug level in the bug (vulnerability) ticket in the testing phase and whether the problem has been resolved are monitored and judged.

[0058] In this embodiment, before extracting and recording the demand function points filled in based on the preset demand function template from the demand plan to obtain the demand function list, it also includes: constructing a preset demand function template including a title bar and title content; filling in each demand function point according to the preset demand function template to obtain the corresponding demand plan; wherein the title bar is the demand function identifier and a digital symbol, and the title content is the functional description of the demand function point. It can be understood that in order to achieve the goal of accurate demand function point extraction, a preset demand function filling template is adopted. After the standard is set, a standard demand template is formed. The demand personnel must write the demand according to this demand function filling template. The core of the preset demand function filling template is to preset a title bar for each demand function point. The title bar is fixed to start with "X+number", and the title content is an overview of the demand function. The template example is as follows:

[0059] XXX Requirements Document

[0060] 1. Background…

[0061] 2. Goal…

[0062] 3. Demand…

[0063] X1. Employee Management…

[0064] X2. Daily report management...

[0065] X+number, overview of required functions.

[0066] In this embodiment, when extracting the demand function list, the natural language processing technology is used to parse and check the demand plan, and it is determined whether there is a title bar in the parsed plan document; if there is a title bar, the demand function points filled in based on the preset demand function template are extracted and recorded from the plan document to obtain the demand function list. Specifically, if there is a title bar, the title content corresponding to the title bar is identified from the plan document, and one or more corresponding demand function points are formed and recorded according to the title content to obtain the demand function list. If there is no title bar, the extraction of demand function points is stopped, and the online risk warning of the software development requirements is triggered. It can be understood that by parsing the demand plan with the help of NLP (Natural Language Processing, natural language processing), the plan document is first checked to see whether it complies with the template specification. Specifically, it is identified whether the plan document includes a title bar of X+number. If it does not exist, it means that it does not comply with the template specification. If the plan document does not meet the specification requirements, the corresponding "no demand function point extracted" risk warning is directly triggered. Based on the requirement document submitted according to the specifications, recognition is performed to identify the text content after X+number, thereby forming multiple requirement function points, which are saved in the requirement function list.

[0067] In this embodiment, for obtaining developed code function points from development code, specifically, first set a target annotation for identifying the method name, add a corresponding target annotation to each method name in the development code, and add the code function developed by the development code under each method name described by the Chinese annotation after the target annotation; wherein the Chinese annotation is consistent with the function description in the demand plan; identify whether each method name in the development code of the software development project references the target annotation, and if so, read and save the Chinese annotation on the corresponding method name to obtain a code function list. It can be understood that the steps of non-intrusive automatic identification are performed in the code development stage. Specifically, a device for automatically identifying the required functional points corresponding to the method is set based on Java (object-oriented programming language) annotation technology, so that the device can be used to directly extract the code functional points in the development stage to form a code functional list. The specific implementation method is to add the set annotation @autoMatch to each method name in the Java development code. Based on the development specification requirements, each method must have a Chinese comment to simply describe what functions are implemented. The logic of the annotation @autoMatch is that if the method name references this annotation, the Chinese comment on the method name is automatically read, and then the Chinese comment is automatically saved to the specified code functional list table.

[0068] It should be noted that during the code development process, a code function point development specification needs to be formed. In the Chinese comments, it must be ensured that the overview is consistent with the required function description of the corresponding required function point to be developed. Specifically, this can be achieved by copying the overview of the required function in the requirement document. The functional explanation of the developer's self-organized language definition is not accepted. In this step, all will be saved in the code function list and will be identified in the step of reading the code function point.

[0069] Step S14: If the circular matching result of the requirement function list and the code function list is a matching result in which the list records of the requirement function list do not match the list records of the code function list, a risk warning for the online launch of the software development requirement is triggered.

[0070] In this embodiment, the number of required function points in the required function list and the number of code function points in the code function list are read; if the number of required function points is greater than the number of code function points, the online risk warning of the software development requirements is triggered; if the number of required function points is less than or equal to the number of code function points, all list records in the required function list are determined as to-be-matched list records, and each list record of the code function list is looped through one by one to detect whether the code function list has completed the list record matching with the to-be-matched list record; if the loop matching result is that there is a matching result that the to-be-matched list record of the required function list does not match each list record of the code function list, then the online risk warning of the software development requirements is triggered. It can be understood that if the required function list identifies 3 function points, namely employee management, attendance management, and daily report management; the contents automatically saved in the code function list are employee management, attendance management, daily report function implementation, and salary management. Two list data are read through the automatic comparison program, the required function list is list1, and the code function list table is list2.

[0071] 1. Size comparison, check whether the size (data volume) of list1 is less than or equal to the size of list2. Size represents the number of records contained in the list. The number of records in the code function list can be more than the number of records in the requirement function list, because developers still have some common component class development and implementation. However, if the number of records in the code function list is less than the number of records in the requirement function list, there must be missing functions. Therefore, first compare the number of records in the two lists to make an initial judgment on whether the required function points are missing. Specifically, if the number of records in the requirement function list is greater than the number of records in the code function list, the "missing function point" risk prompt of the software development requirement is triggered, which means that the initial judgment has not passed; if the number of records in the code function list is greater than or equal to the number of records in the requirement function list, it means that the initial judgment has passed, and the next technical step (2, one-by-one comparison) is executed.

[0072] 2. Compare one by one. First get the first record of list1 "employee management", then loop to take out each record of list2, and compare them through java's equal method (used to compare whether two objects are equal). The equal method can accurately check whether two strings are exactly the same. Through loop comparison, "employee management" can be found in list2, then end this loop and enter the next loop, take out the second record of list1 "attendance management", and then compare it with each content in list2 in turn. If a matching record is found, return ok. In this way, if it is found that "daily management" does not find an accurate match, it returns a match failure, triggering the risk prompt of "functional points may be missing" of the software development requirement, which means that the code does not fully realize the required functions. Manual inspection is required to see if there are any missing functions or missing functional descriptions. In summary, if all the required function points in the required function list can be mapped to the code function list and find 100% matching descriptions, it means that the requirements will be basically 100% complete. If not, the system will automatically alarm, which may be due to omissions in the function implementation, or the function is not described according to the specification. Manual intervention is required to check whether there are omissions or the code specification is not rigorous. The system will automatically alarm and remind manual inspection and verification. In this way, in order to determine whether there are omissions in the function points in the required function list, this solution adopts template-based writing of requirements, non-intrusive identification of codes, and automatic matching of tables for automatic monitoring and automatic warning, reducing the number of delayed launches.

[0073] In this embodiment, after the code development is completed, the number of abnormal data of the required function type in the program abnormal data is detected to see if it exceeds the preset abnormal number threshold; if it exceeds the preset abnormal number threshold, the online risk prompt of the software development requirement is triggered. Figure 2As shown, after the code development is completed, it enters the testing phase. Specifically, modeling and analysis are performed through the bug data raised by the testers. Design a monitoring indicator, the indicator name is "demand deviation", and the indicator monitoring rule is that when the number of demand-related problems in the bug exceeds N, the system needs to automatically remind that there is a risk of demand deviation. After such an early warning is issued, the person in charge needs to decide whether it is necessary to review the development content of the developer and to use other means to check whether the demand is fully covered. The bug statistics rule designed in the monitoring rule is to count the problem types marked as demand in the bug tickets raised by the testers, which are defined as the number of demand-related problems. The set warning threshold is N, and N supports configuration to support phased adjustments, because this value is not static for scientific reasons. The specific value of N setting depends on data modeling analysis. The data modeling analysis is as follows:

[0074] Because there are different development teams, the level or quality of different development teams cannot be evaluated equally. Randomly select 50% of the development teams as the sample benchmark. For example, select 5 groups, A, B, C, D, and E;

[0075] Through the analysis of the existing project management data, the number of requirements for delayed launch in each group is counted, and then the number of requirement-related issues in the bug tickets of such requirements is counted. For example, the number of delayed launch requirements in Group A is 5, and the number of requirement-related issues for each online requirement is 2, 4, 3, 2, and 4 respectively. The number of requirement-related issues for a single delayed launch requirement in Group A is m1=(2+4+3+2+4) / 5. Similarly, the number for Group B is m2, the number for Group C is m3, the number for Group D is m4, and the number for Group E is m5.

[0076] The threshold N is obtained by taking the average value of each group, then N=(m1+m2+m3+m4+m5) / 5;

[0077] As the amount of data continues to increase, the reference value of N becomes more accurate, so dynamic modeling is implemented. Sampling is re-performed after a quarterly cycle. The latest N is obtained through the above data modeling and analysis, and then updated to the rule configuration.

[0078] Development quality monitoring indicators. This indicator also relies on the number of bugs in the testing phase to evaluate the quality of development from multiple angles, so as to identify whether there is a risk of delay as early as possible. Development quality monitoring indicator 1, set the bug number monitoring threshold (configurable), which is set based on expert experience and the difficulty of the requirements. When the threshold is exceeded, the system automatically warns; Development quality monitoring indicator 2, set the bug return number threshold to 2, and set the threshold based on expert experience. If a bug is repaired more than 2 times, it means that the development quality is seriously poor. When a bug is returned by the tester 3 times, the system automatically warns of risks. It can be seen that by scientifically setting monitoring indicators, refined monitoring is achieved, and monitoring design for demand deviation is realized.

[0079] When the requirements are developed and tested, and the test acceptance is passed, the product is launched and put into use. After the launch, the requirements analyst updates the actual launch time in the requirements plan. The system automatically determines the actual launch time and the first expected launch time to mark whether it is delayed.

[0080] It can be seen that the present application discloses a method for identifying the risk of software development demand launch, including: obtaining the demand plan of the software development project, and judging whether the first expected launch time of the demand plan is earlier than the second expected launch time determined after evaluating the development workload; if so, triggering the launch risk prompt of the software development demand, and prompting to re-formulate the second expected launch time and the first expected launch time; if not, extracting and recording the demand function points filled in based on the preset demand function template from the demand plan to obtain the demand function list, and reading and saving the developed code function points from the development code of the software development project to obtain the code function list; if the circular matching result of the demand function list and the code function list is that there is a matching result that the list record of the demand function list does not match the list record of the code function list, then triggering the software development demand launch risk prompt. It can be seen that the possible conflict of the expected launch time of the demand plan can be discovered in advance, and timely adjustments can be made to avoid problems caused by rushing to launch due to time constraints. Ensure that the demand function matches the developed code function to reduce the situation where the function is missing or wrong after launching. Strict functional matching checks can help develop software that better meets requirements and improve software stability and reliability. The clear correspondence between required functions and code functions makes it easier for project managers to track and monitor effectively. Timely risk warnings can also enable project teams to respond quickly, optimize resource allocation and task scheduling, and reduce the cost of rework and repairs due to launch failures or functional mismatches.

[0081] Reference Figure 3 As shown, the present invention also discloses a software development requirement online risk identification device, including:

[0082] The time judgment module 11 is used to obtain the demand plan of the software development project and judge whether the first expected online time of the demand plan is earlier than the second expected online time determined after evaluating the development workload;

[0083] a prompt triggering module 12, configured to trigger a risk prompt for the launch of the software development requirement if yes, and prompt to re-formulate the second expected launch time and the first expected launch time;

[0084] A list acquisition module 13 is used to extract and record the required function points filled in based on the preset required function template from the demand plan to obtain a required function list, and read and save the developed code function points from the development code of the software development project to obtain a code function list;

[0085] The function point matching module 14 is used to trigger an online risk warning for software development requirements if the circular matching result of the requirement function list and the code function list is a matching result in which the string information of the requirement function list does not match the string information of the code function list.

[0086] It can be seen that the present application discloses obtaining the demand plan of a software development project, and judging whether the first expected launch time of the demand plan is earlier than the second expected launch time determined after evaluating the development workload; if so, triggering the launch risk prompt of the software development demand, and prompting to re-formulate the second expected launch time and the first expected launch time; if not, extracting and recording the demand function points filled in based on the preset demand function template from the demand plan to obtain the demand function list, and reading and saving the developed code function points from the development code of the software development project to obtain the code function list; if the circular matching result of the demand function list and the code function list is a matching result that there is a list record of the demand function list and a list record of the code function list that does not match, then triggering the launch risk prompt of the software development demand. It can be seen that the possible conflict of the expected launch time of the demand plan can be discovered in advance, and timely adjustments can be made to avoid problems caused by rushing to launch due to time constraints. Ensure that the demand function matches the developed code function to reduce the situation where the function is missing or wrong after going online. Through strict function matching checks, it is helpful to develop software that better meets the needs and improve the stability and reliability of the software. The correspondence between required functions and code functions is clarified, which facilitates project managers to conduct effective tracking and monitoring. Timely risk warnings can enable the project team to respond quickly, optimize resource allocation and task scheduling, and reduce the rework and repair costs required due to online failures or functional mismatches.

[0087] Furthermore, the present application also discloses an electronic device. Figure 4 is a structural diagram of an electronic device 20 according to an exemplary embodiment. Figure 4 The content hereof cannot be considered as any limitation on the scope of use of this application.

[0088] Figure 4 A schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the software development requirement online risk identification method disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0089] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0090] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0091] In addition, the memory 22, as a carrier for storing resources, can be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0092] Among them, the operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, so as to realize the operation and processing of the massive data 223 in the memory 22 by the processor 21, which can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program that can be used to complete the software development demand online risk identification method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks. In addition to data received by the electronic device and transmitted from an external device, the data 223 can also include data collected by its own input and output interface 25, etc.

[0093] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned software development requirement launch risk identification method is implemented. The specific steps of the method can refer to the corresponding contents disclosed in the aforementioned embodiments, and will not be repeated here.

[0094] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0095] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. The steps of the method or algorithm described in conjunction with the embodiments disclosed herein can be implemented directly with hardware, a software module executed by a processor, or a combination of the two. The software module can be placed in a random access memory RAM (Random Access Memory), memory, read-only memory ROM (Read Only Memory), electrically programmable EPROM (Electrically Programmable Read Only Memory), electrically erasable programmable EEPROM (ElectricErasable Programmable Read Only Memory), register, hard disk, removable disk, CD-ROM (CompactDisc-Read Only Memory), or any other form of storage medium known in the technical field.

[0096] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0097] The scheme provided by the present invention is introduced in detail above. Specific examples are used in this article to illustrate the principle and implementation mode of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation mode and application scope. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A method for identifying risks in software development requirements, characterized in that: include: Obtaining a demand plan for a software development project, and determining whether a first expected launch time of the demand plan is earlier than a second expected launch time determined after evaluating the development workload; If so, a risk warning for the launch of the software development requirement is triggered, and a prompt is given to re-formulate the second expected launch time and the first expected launch time; If not, extract and record the required function points filled in based on the preset required function template from the required plan to obtain a required function list, and read and save the developed code function points from the development code of the software development project to obtain a code function list; If the circular matching result of the requirement function list and the code function list is a matching result in which the list record of the requirement function list does not match the list record of the code function list, then a launch risk warning of the software development requirement is triggered; The step of reading and saving the developed code function points from the development code of the software development project to obtain a code function list includes: Set a target annotation for identifying the method name, add a corresponding target annotation to each method name in the development code, and add the code function developed by the development code under each method name described by the Chinese annotation after the target annotation; wherein the Chinese annotation is consistent with the function description in the demand plan; Identify whether each method name in the development code of the software development project references the target annotation. If so, read and save the Chinese annotation on the corresponding method name to obtain a code function list.

2. The software development requirement launch risk identification method according to claim 1, characterized in that: Before extracting and recording the required function points filled in based on the preset required function template from the required plan to obtain the required function list, the method further includes: Build a preset requirement function template including title bar and title content; Fill in each demand function point according to the preset demand function template to obtain the corresponding demand plan; Among them, the title bar is the required function identifier and digital symbols, and the title content is the functional description of the required function point.

3. The software development requirement launch risk identification method according to claim 2, characterized in that: The extracting and recording of the demand function points filled in based on the preset demand function template from the demand plan to obtain a demand function list includes: Parsing and checking the demand plan using natural language processing technology, and determining whether a title bar exists in the parsed plan document; If there is a title bar, extract and record the required function points filled in based on the preset required function template from the plan document to obtain a required function list; If the title bar does not exist, the extraction of required function points will be stopped, and the online risk warning of the software development requirements will be triggered.

4. The software development requirement launch risk identification method according to claim 3 is characterized in that: If the title bar exists, the required function points filled in based on the preset required function template are extracted and recorded from the plan document to obtain a required function list, including: If a title bar exists, the title content corresponding to the title bar is identified from the plan document, and one or more corresponding required function points are formed and recorded according to the title content to obtain a required function list.

5. The software development requirement launch risk identification method according to claim 1, characterized in that: If the circular matching result of the requirement function list and the code function list is that there is a matching result in which the list record of the requirement function list does not match the list record of the code function list, triggering the online risk prompt of the software development requirement includes: Read the number of required function points in the required function list and the number of code function points in the code function list; If the number of required function points is greater than the number of code function points, a risk warning for the launch of the software development requirement is triggered; If the number of required function points is less than or equal to the number of code function points, all list records in the required function list are determined as list records to be matched, and each list record in the code function list is looped through one by one to detect whether the list record in the code function list is matched with the list record to be matched; If the result of the circular matching is a matching result in which the to-be-matched list record of the requirement function list does not match any list record of the code function list, a risk warning for the online launch of the software development requirement is triggered.

6. The method for identifying risks of software development requirements going online according to any one of claims 1 to 5, characterized in that: Also includes: When the code development is completed, check whether the number of abnormal data of the required function type in the program abnormal data exceeds the preset abnormal number threshold; If the preset abnormal number threshold is exceeded, the online risk warning of the software development requirements will be triggered.

7. A software development requirement online risk identification device, characterized in that: include: A time judgment module is used to obtain a demand plan for a software development project and judge whether a first expected launch time of the demand plan is earlier than a second expected launch time determined after evaluating the development workload; a prompt trigger module, configured to trigger a risk prompt for the launch of the software development requirement, and prompt the user to re-formulate the second expected launch time and the first expected launch time; A list acquisition module is used to extract and record the required function points filled in based on the preset required function template from the demand plan to obtain a required function list, and read and save the developed code function points from the development code of the software development project to obtain a code function list; A function point matching module, for triggering a risk warning for the launch of software development requirements if a circular matching result of the requirement function list and the code function list is a matching result in which the string information of the requirement function list does not match the string information of the code function list; The list acquisition module is specifically used to set a target annotation for identifying a method name, so as to add a corresponding target annotation to each method name in the development code, and add the code functions developed by the development code under each method name described by the Chinese annotation after the target annotation; wherein the Chinese annotation is consistent with the function description in the demand plan; and identify whether each method name in the development code of the software development project references the target annotation, and if so, read and save the Chinese annotation on the corresponding method name to obtain a code function list.

8. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor is used to execute the computer program to implement the steps of the software development requirement online risk identification method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein, when the computer program is executed by a processor, the steps of the software development requirement online risk identification method as described in any one of claims 1 to 6 are implemented.

Citation Information

Patent Citations

  • Project management method and system

    CN112817843A

  • CI-based automatic demand progress difference analysis method and management server

    CN113448561A

  • Project progress real-time monitoring method and device, electronic equipment and storage medium

    CN114462969A

  • Software development kit generation method and device, equipment and storage medium

    CN115543419A

  • Demand publishing method and device, electronic equipment and storage medium

    CN115964021A