A method and system for evaluating the efficiency of requirement transfer based on the software development process

Abstract

The present invention provides a method and system for evaluating the effectiveness of demand flow based on the software development process, comprising the following steps: obtaining the correspondence between requirements and projects from the requirements management module of the project management system; selecting items and statistically analyzing relevant attributes throughout the lifecycle of the demand flow; obtaining the requirements to be collected based on the team requirements configuration stored in the database; and performing data analysis and presentation. The present invention constructs a demand flow scoring system and creates a demand flow effectiveness evaluation system; this system enables the overall statistical information of the demand flow process to be observed, progressively progressing from macroscopic to detailed observations; through this scoring system, the effectiveness of the demand flow process can be measured, providing guidance for team demand changes and the next course of action.

Description

Technical Field

[0001] The present invention relates to the technical field of software R&D management, and in particular to a method and system for evaluating the efficiency of demand flow based on a software development process. Background Art

[0002] Currently, various project and transaction tracking tools or systems all include necessary demand management modules. In the demand management module, demand managers enter R&D task requirements, and R&D personnel circulate and update the requirements based on the R&D progress. The management module can reflect the current demand circulation and update process.

[0003] In the existing technology, each R&D team currently undertakes a number of demand goals, and the various requirements are arranged in a list in the management module.

[0004] However, the team cannot see the overall statistical information of the demand flow process and can only focus on local information. There is a lack of control over the demand flow from the macro to the details. There is no unified standard to measure the efficiency of demand flow. The team cannot measure the health of the current demand flow; there is no effective comparison of demand flow efficiency between teams, and timely response decisions based on the current situation of demand flow efficiency. Summary of the Invention

[0005] The purpose of the present invention is to provide a method and system for evaluating the efficiency of demand flow based on the software development process, so as to solve the problems raised in the above background technology.

[0006] To achieve the above-mentioned object, the present invention provides the following technical solution: a method for evaluating the efficiency of demand flow based on the software development process, comprising the following steps:

[0007] Obtain the correspondence between requirements and projects from the requirements management module of the project management system; obtain the correspondence between R&D teams and projects from the R&D personnel management system; store the correspondence between R&D teams and projects in the database; open an API interface to the outside world, so that each team can dynamically add, delete or modify the corresponding projects of the team according to its own organizational structure adjustments;

[0008] Throughout the lifecycle of demand flow, we select demand task statistics-related attributes, milestone-related attributes, release iteration-related attributes, and key task-related attributes as performance indicators for evaluating demand flow.

[0009] Obtain the requirements to be collected based on the team requirements configuration stored in the database; call the API in the requirements management system to obtain the original data of the requirements process; process the original data according to statistical requirements and combine it into useful information items; store the generated information items in the database;

[0010] During the data analysis process, the health of the demand flow is measured using five scores: "Demand Task Completion Status Score," "Demand Task Throughput Status Score," "Milestone Progress Status Score," "Iteration Status Score," and "Overall Demand Process Score," to guide the team's further decision-making.

[0011] The demand flow data in demand management is secondary counted according to pre-specified attributes, and the statistical data is displayed externally through charts.

[0012] Preferably, when selecting the characteristic attributes of demand flow:

[0013] Demand task statistics: The demand task statistics attribute includes three sub-attributes: "Ongoing demand tasks," "Overdue demand tasks," and "Interval demand task throughput." These attributes are used to count the number of tasks whose completion times fall within the demand deadline, the number of tasks that are not completed within the demand deadline, and the average number of tasks completed per day during the selected time period.

[0014] Milestone Progress: A milestone represents a significant change or step in project development. The "Milestone Progress" statistics capture the number of milestones at different levels of completion, measuring the health of key nodes in the demand flow. Currently, milestone completion levels are defined as 0-49%, 50%-79%, 80%-99%, and 100%.

[0015] Iterations: Iterations count the number of times a requirement task is iteratively developed within a specified time period. The more iterations within a specified time period, the smoother the demand flow and the smoother the project progress.

[0016] Department key tasks: Department key tasks are important indicators that reflect the flow of demand outside of milestones. Currently, department key tasks are divided into five levels: 0-49%, 50%-79%, 80%-99% and 100%. Statistics are collected to determine the number of tasks that fall within these four ranges.

[0017] Preferably, during data analysis:

[0018] Demand task completion status score: Based on the feature values extracted when selecting the demand flow feature attributes, if the number of overdue demand tasks within a specified time is n, the demand task completion status score is as follows:

[0019] S i =100×(0.5 1 / 3 ) (0.5×n)

[0020] Demand task throughput status score: Based on the feature values extracted when selecting the demand flow feature attributes, the interval demand task throughput is r, and the number of team members is p. The formula for per capita demand task throughput is as follows:

[0021]

[0022] Milestone progress score: Based on the feature values extracted when selecting the demand flow feature attributes, the number of milestones completed at a specified time point is W f The number of unfinished milestones is W u , the milestone completion degree of an unfinished project is Y io , the standard completion of an unfinished project is defined as:

[0023]

[0024] Where T n Indicates the current time, Y ic Indicates the start time of the project numbered i, Y ip represents the planned completion time of the project numbered i;

[0025] The milestone score calculation formula is as follows:

[0026]

[0027] m i The total number of uncompleted milestones in project number i

[0028] W u =∑m i The sum of all uncompleted milestones for all projects is W u

[0029] It represents the total number of uncompleted milestones after weighting the uncompleted milestones of all projects;

[0030] Iteration status score: Based on the feature values extracted when selecting the demand flow feature attributes, the total number of days in the specified time is d, the total number of iterations is m, and the formula for the average number of iterations per day is as follows:

[0031]

[0032] Iteration status score: S l =100×30×a

[0033] The overall scores for the demand flow process are as follows:

[0034] S=0.4×0.3×S i +0.4×0.7×S j+0.5×S k +0.1×S l .

[0035] Preferably, when displaying data, the "key tasks of the department" are displayed in a pie chart according to the five levels of completion when the demand flow characteristic attributes are selected;

[0036] Milestone Progress is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart allows you to drill down to the specific milestone completion status.

[0037] The "Iteration Count" is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart will display a dot chart of the entire iteration process, showing the temporal relationship of the iterations.

[0038] Use a radar chart to display the team score data obtained during data analysis, and also compare this data with the average score data of all teams.

[0039] A demand flow efficiency evaluation system based on the software development process includes: a team demand configuration module, a demand flow feature attribute selection module, a data acquisition module, a data analysis module, and a data display module. The demand flow feature attribute selection module obtains information from the team demand configuration module, the data acquisition module obtains information from the demand flow feature attribute selection module, the data analysis module obtains information from the data acquisition module, and the data display module obtains information from the data analysis module.

[0040] Preferably, the team demand configuration module is used to obtain the correspondence between demand and projects from the demand management module of the project management system; obtain the correspondence between R&D teams and projects from the R&D personnel management system; store the correspondence between R&D teams and projects in the database; open an API interface to the outside world, and each team can dynamically add, delete or modify the projects corresponding to the team according to its own organizational structure adjustments.

[0041] Preferably, the demand flow characteristic attribute selection module is used to select demand task statistics-related attributes, milestone-related attributes, release iteration-related attributes and key task-related attributes as performance indicators for evaluating demand flow throughout the entire life cycle of demand flow;

[0042] Demand task statistics: The demand task statistics attribute includes three sub-attributes: "Ongoing demand tasks," "Overdue demand tasks," and "Interval demand task throughput." These attributes are used to count the number of tasks whose completion times fall within the demand deadline, the number of tasks that are not completed within the demand deadline, and the average number of tasks completed per day during the selected time period.

[0043] Milestone Progress: A milestone represents a significant change or step in project development. The "Milestone Progress" statistics capture the number of milestones at different levels of completion, measuring the health of key nodes in the demand flow. Currently, milestone completion levels are defined as 0-49%, 50%-79%, 80%-99%, and 100%.

[0044] Iterations: Iterations count the number of times a requirement task is iteratively developed within a specified time period. The more iterations within a specified time period, the smoother the demand flow and the smoother the project progress.

[0045] Department key tasks: Department key tasks are important indicators that reflect the flow of demand outside of milestones. Currently, department key tasks are divided into four levels: 0-49%, 50%-79%, 80%-99% and 100%. Statistics are collected to determine the number of tasks that fall within these four ranges.

[0046] Preferably, the data collection module is used to obtain the requirements to be collected according to the team requirement configuration stored in the database; call the API in the requirement management system to obtain the original data of the requirement process; process the original data according to statistical requirements and combine them into useful information items; and store the generated information items in the database;

[0047] Demand task completion status score: Based on the feature values extracted when selecting the demand flow feature attributes, if the number of overdue demand tasks within a specified time is n, the demand task completion status score is as follows:

[0048] S i =100×(0.5 1 / 3 ) (0.5×n)

[0049] Demand task throughput status score: Based on the feature values extracted when selecting the demand flow feature attributes, the interval demand task throughput is r, and the number of team members is p. The formula for per capita demand task throughput is as follows:

[0050]

[0051] Milestone progress score: Based on the feature values extracted when selecting the demand flow feature attributes, the number of milestones completed at a specified time point is W f The number of unfinished milestones is W u , the milestone completion degree of an unfinished project is Y io , the standard completion of an unfinished project is defined as:

[0052]

[0053] Where T nIndicates the current time, Y ic Indicates the start time of the project numbered i, Y ip represents the planned completion time of the project numbered i;

[0054] The milestone score calculation formula is as follows:

[0055]

[0056] m i The total number of uncompleted milestones in project number i

[0057] W u =∑m i The sum of all uncompleted milestones for all projects is W u

[0058] It represents the total number of uncompleted milestones after weighting the uncompleted milestones of all projects;

[0059] Iteration status score: Based on the feature values extracted when selecting the demand flow feature attributes, the total number of days in the specified time is d, the total number of iterations is m, and the formula for the average number of iterations per day is as follows:

[0060]

[0061] Iteration status score: S l =100×30×a

[0062] The overall scores for the demand flow process are as follows:

[0063] S=0.4×0.3×S i +0.4×0.7×S j +0.5×S k +0.1×S l .

[0064] Preferably, the data analysis module is used to measure the health of demand flow through five scores, namely "demand task completion status score", "demand task throughput status score", "milestone progress status score", "iteration status score" and "overall score of demand process" during the data analysis process, to provide guidance for the team's further decision-making.

[0065] Preferably, the data display module is used to perform secondary statistics on the demand flow data in demand management according to pre-specified attributes, and display the statistical data externally through charts;

[0066] "Key Department Tasks" is displayed in a pie chart based on the five levels of completion when selecting the characteristic attributes of demand flow;

[0067] Milestone Progress is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart allows you to drill down to the specific milestone completion status.

[0068] The "Iteration Count" is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart will display a dot chart of the entire iteration process, showing the temporal relationship of the iterations.

[0069] Use a radar chart to display the team score data obtained during data analysis, and also compare this data with the average score data of all teams.

[0070] Compared with the prior art, the present invention has the following beneficial effects:

[0071] The demand flow efficiency evaluation method and system based on the software development process proposed in the present invention selects several attributes such as demand task statistics related attributes, milestone related attributes, release iteration related attributes and key task related attributes; the entire information processing flow from configuration entry, feature attribute selection, data collection, to scoring system construction and data display; the scoring quantification idea of the demand flow process, as well as the selection of indicators and the corresponding calculation method, constructs a demand flow scoring system and creates a demand flow efficiency evaluation system; through this system, the overall statistical information of the demand flow process can be observed, and it can be gradually progressed from the macro to the detailed observation; through this scoring system, the efficiency of the demand flow process can be measured, providing guidance for the team's demand changes and the next action direction. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 This is a block diagram of the evaluation system of the present invention. DETAILED DESCRIPTION

[0073] In order to clearly and completely describe the objectives and technical solutions of the present invention and make the advantages more clearly understood, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are part of the embodiments of the present invention, not all of them, and are only used to explain the embodiments of the present invention, not to limit the embodiments of the present invention. All other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0074] In the description of the present invention, it should be noted that the terms "center," "middle," "upper," "lower," "left," "right," "inner," "outer," "top," "bottom," "side," "vertical," "horizontal," and the like, indicating positions or location relationships, are based on the positions or location relationships shown in the accompanying drawings and are intended only to facilitate the description of the present invention and simplify the description. They are not intended to indicate or imply that the devices or components referred to must have a specific orientation, be constructed, or operate in a specific orientation. Therefore, they should not be construed as limiting the present invention. Furthermore, the terms "one," "first," "second," "third," "fourth," "fifth," and "sixth" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0075] In the description of the present invention, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed, detachable, or integral connections; mechanical or electrical connections; direct or indirect connections through an intermediate medium; and internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on the specific circumstances.

[0076] For the purpose of simplicity and illustration, the principles of the embodiments are described primarily with reference to examples. In the following description, many specific details are provided to provide a thorough understanding of the embodiments. However, it will be apparent to those skilled in the art that these embodiments may not be limited to these specific details in practice. In some instances, well-known methods and structures are not described in detail to avoid unnecessarily obscuring the understanding of these embodiments. In addition, all embodiments may be used in combination with each other.

[0077] See also Figure 1 The present invention provides a technical solution: a method for evaluating the efficiency of demand flow based on the software development process, characterized by comprising the following steps:

[0078] Obtain the correspondence between requirements and projects from the requirements management module of the project management system; obtain the correspondence between R&D teams and projects from the R&D personnel management system; store the correspondence between R&D teams and projects in the database; open an API interface to the outside world, so that each team can dynamically add, delete or modify the corresponding projects of the team according to its own organizational structure adjustments;

[0079] Throughout the lifecycle of demand flow, we select demand task statistics-related attributes, milestone-related attributes, release iteration-related attributes, and key task-related attributes as performance indicators for evaluating demand flow.

[0080] Demand task statistics: The demand task statistics attribute includes three sub-attributes: "Ongoing demand tasks," "Overdue demand tasks," and "Interval demand task throughput." These attributes are used to count the number of tasks whose completion times fall within the demand deadline, the number of tasks that are not completed within the demand deadline, and the average number of tasks completed per day during the selected time period.

[0081] Milestone Progress: A milestone represents a significant change or step in project development. The "Milestone Progress" statistics capture the number of milestones at different levels of completion, measuring the health of key nodes in the demand flow. Currently, milestone completion levels are defined as 0-49%, 50%-79%, 80%-99%, and 100%.

[0082] Iterations: Iterations count the number of times a requirement task is iteratively developed within a specified time period. The more iterations within a specified time period, the smoother the demand flow and the smoother the project progress.

[0083] Departmental key tasks: These are important indicators that reflect demand flow beyond milestones. Currently, departmental key tasks are divided into four levels: 0-49%, 50%-79%, 80%-99%, and 100%. Statistics are collected to determine the number of tasks that fall within these four ranges.

[0084] Obtain the requirements to be collected based on the team requirements configuration stored in the database; call the API in the requirements management system to obtain the original data of the requirements process; process the original data according to statistical requirements and combine it into useful information items; store the generated information items in the database;

[0085] During the data analysis process, the health of the demand flow is measured using five scores: "Demand Task Completion Status Score," "Demand Task Throughput Status Score," "Milestone Progress Status Score," "Iteration Status Score," and "Overall Demand Process Score," to guide the team's further decision-making.

[0086] Demand task completion status score: Based on the feature values extracted when selecting the demand flow feature attributes, if the number of overdue demand tasks within a specified time is n, the demand task completion status score is as follows:

[0087] S i =100×(0.5 1 / 3 ) (0.5×n)

[0088] Demand task throughput status score: Based on the feature values extracted when selecting the demand flow feature attributes, the interval demand task throughput is r, and the number of team members is p. The formula for per capita demand task throughput is as follows:

[0089]

[0090] Milestone progress score: Based on the feature values extracted when selecting the demand flow feature attributes, the number of milestones completed at a specified time point is W f The number of unfinished milestones is W u , the milestone completion degree of an unfinished project is Y io , the standard completion of an unfinished project is defined as:

[0091]

[0092] Where T n Indicates the current time, Y ic Indicates the start time of the project numbered i, Y ip represents the planned completion time of the project numbered i;

[0093] The milestone score calculation formula is as follows:

[0094]

[0095] m i The total number of uncompleted milestones in project number i

[0096] W u =∑m i The sum of all uncompleted milestones for all projects is W u

[0097] It represents the total number of uncompleted milestones after weighting the uncompleted milestones of all projects;

[0098] Iteration status score: Based on the feature values extracted when selecting the demand flow feature attributes, the total number of days in the specified time is d, the total number of iterations is m, and the formula for the average number of iterations per day is as follows:

[0099]

[0100] Iteration status score: S l =100×30×a

[0101] The overall scores for the demand flow process are as follows:

[0102] S=0.4×0.3×S i +0.4×0.7×S j +0.5×S k +0.1×S l

[0103] Conduct secondary statistics on demand flow data in demand management according to pre-specified attributes, and display the statistical data externally through charts;

[0104] "Key Department Tasks" is displayed in a pie chart based on the five levels of completion when selecting the characteristic attributes of demand flow;

[0105] Milestone Progress is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart allows you to drill down to the specific milestone completion status.

[0106] The "Iteration Count" is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart will display a dot chart of the entire iteration process, showing the temporal relationship of the iterations.

[0107] Use a radar chart to display the team score data obtained during data analysis, and also compare this data with the average score data of all teams.

[0108] A demand flow efficiency evaluation system based on the software development process is characterized by: including: a team demand configuration module, a demand flow feature attribute selection module, a data acquisition module, a data analysis module, and a data display module. The demand flow feature attribute selection module obtains information from the team demand configuration module, the data acquisition module obtains information from the demand flow feature attribute selection module, the data analysis module obtains information from the data acquisition module, and the data display module obtains information from the data analysis module.

[0109] The team requirement configuration module is used to obtain the correspondence between requirements and projects from the requirement management module of the project management system; obtain the correspondence between R&D teams and projects from the R&D personnel management system; store the correspondence between R&D teams and projects in the database; and open an API interface to the outside world, so that each team can dynamically add, delete or modify the projects corresponding to the team according to its own organizational structure adjustments.

[0110] The demand flow characteristic attribute selection module is used to select demand task statistics-related attributes, milestone-related attributes, release iteration-related attributes, and key task-related attributes as performance indicators for evaluating demand flow throughout the entire life cycle of demand flow;

[0111] Demand task statistics: The demand task statistics attribute includes three sub-attributes: "Ongoing demand tasks," "Overdue demand tasks," and "Interval demand task throughput." These attributes are used to count the number of tasks whose completion times fall within the demand deadline, the number of tasks that are not completed within the demand deadline, and the average number of tasks completed per day during the selected time period.

[0112] Milestone Progress: A milestone represents a significant change or step in project development. The "Milestone Progress" statistics capture the number of milestones at different levels of completion, measuring the health of key nodes in the demand flow. Currently, milestone completion levels are defined as 0-49%, 50%-79%, 80%-99%, and 100%.

[0113] Iterations: Iterations count the number of times a requirement task is iteratively developed within a specified time period. The more iterations within a specified time period, the smoother the demand flow and the smoother the project progress.

[0114] Department key tasks: Department key tasks are important indicators that reflect the flow of demand outside of milestones. Currently, department key tasks are divided into four levels: 0-49%, 50%-79%, 80%-99% and 100%. Statistics are collected to determine the number of tasks that fall within these four ranges.

[0115] The data collection module is used to obtain the requirements that need to be collected based on the team requirements configuration stored in the database; call the API in the requirements management system to obtain the original data of the requirements process; process the original data according to statistical requirements and combine it into useful information items; and store the generated information items in the database;

[0116] Demand task completion status score: Based on the feature values extracted when selecting the demand flow feature attributes, if the number of overdue demand tasks within a specified time is n, the demand task completion status score is as follows:

[0117] S i =100×(0.5 1 / 3 ) (0.5×n)

[0118] Demand task throughput status score: Based on the feature values extracted when selecting the demand flow feature attributes, the interval demand task throughput is r, and the number of team members is p. The formula for per capita demand task throughput is as follows:

[0119]

[0120] Milestone progress score: Based on the feature values extracted when selecting the demand flow feature attributes, the number of milestones completed at a specified time point is W f The number of unfinished milestones is W u , the milestone completion degree of an unfinished project is Y io , the standard completion of an unfinished project is defined as:

[0121]

[0122] Where T n Indicates the current time, Yic Indicates the start time of the project numbered i, Y ip represents the planned completion time of the project numbered i;

[0123] The milestone score calculation formula is as follows:

[0124]

[0125] m i The total number of uncompleted milestones in project number i

[0126] W u =∑m i The sum of all uncompleted milestones for all projects is W u

[0127] It represents the total number of uncompleted milestones after weighting the uncompleted milestones of all projects;

[0128] Iteration status score: Based on the feature values extracted when selecting the demand flow feature attributes, the total number of days in the specified time is d, the total number of iterations is m, and the formula for the average number of iterations per day is as follows:

[0129]

[0130] Iteration status score: S l =100×30×a

[0131] The overall scores for the demand flow process are as follows:

[0132] S=0.4×0.3×S i +0.4×0.7×S j +0.5×S k +0.1×S l .

[0133] The data analysis module is used to measure the health of demand flow through five scores during the data analysis process: "demand task completion status score", "demand task throughput status score", "milestone progress status score", "iteration status score" and "overall score of demand process", to provide guidance for the team's further decision-making.

[0134] The data display module is used to perform secondary statistics on the demand flow data in demand management according to pre-specified attributes, and display the statistical data externally through charts;

[0135] "Key Department Tasks" is displayed in a pie chart based on the five levels of completion when selecting the characteristic attributes of demand flow;

[0136] Milestone Progress is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart allows you to drill down to the specific milestone completion status.

[0137] The "Iteration Count" is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart will display a dot chart of the entire iteration process, showing the temporal relationship of the iterations.

[0138] Use a radar chart to display the team score data obtained during data analysis, and also compare this data with the average score data of all teams.

[0139] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A method for evaluating the efficiency of demand flow based on the software development process, characterized in that: The following steps are involved: Obtain the correspondence between requirements and projects from the requirements management module of the project management system; Obtain the correspondence between R&D teams and projects from the R&D personnel management system; store the correspondence between R&D teams and projects in the database; Open the API interface to the outside world, and each team can dynamically add, delete or modify the corresponding projects according to its own organizational structure adjustment; Throughout the lifecycle of demand flow, we select demand task statistics-related attributes, milestone-related attributes, release iteration-related attributes, and key task-related attributes as performance indicators for evaluating demand flow. Get the requirements that need to be collected based on the team requirements configuration stored in the database; Call the API in the demand management system to obtain the original data of the demand process; process the original data according to statistical requirements and combine it into useful information items; store the generated information items in the database; During data analysis, the health of the demand flow is measured using five scores: "Demand Task Completion Score," "Demand Task Throughput Score," "Milestone Progress Score," "Iteration Score," and "Overall Demand Process Score," to guide the team's further decision-making. Conduct secondary statistics on demand flow data in demand management according to pre-specified attributes, and display the statistical data externally through charts; When selecting the characteristic attributes of demand flow: Demand task statistics: Demand task statistics include three sub-attributes: Ongoing Demand Tasks, Overdue Demand Tasks, and Interval Demand Task Throughput. These statistics include the number of tasks whose completion times fall within the demand deadline, the number of tasks that remain uncompleted within the demand deadline, and the average daily number of completed tasks within the selected time period. Milestone Progress: A milestone represents a significant change or step in project development. "Milestone Progress" statistics capture the number of milestones at different levels of completion, measuring the health of key nodes in the demand flow. Currently, milestone completion levels are defined as 0-49%, 50%-79%, 80%-99%, and 100%. Iterations: Iterations count the number of times a requirement task is iteratively developed within a specified time period. The more iterations within a specified time period, the smoother the demand flow and the smoother the project progress. Departmental key tasks: These are important indicators that reflect demand flow beyond milestones. Currently, departmental key tasks are divided into four levels: 0-49%, 50%-79%, 80%-99%, and 100%. Statistics are collected to determine the number of tasks that fall within these four ranges. During data analysis: Demand task completion status score: Based on the feature values extracted when selecting the demand flow feature attributes, if the number of overdue demand tasks within a specified time is n, the demand task completion status score is as follows: S i ＝100×(0.5 1 / 3 ) (0.5×n) Demand task throughput status score: Based on the feature values extracted when selecting the demand flow feature attributes, the interval demand task throughput is r, and the number of team members is p. The formula for per capita demand task throughput is as follows: Milestone progress score: Based on the feature values extracted when selecting the demand flow feature attributes, the number of milestones completed at a specified time point is W f The number of unfinished milestones is W u , the milestone completion degree of an unfinished project is Y io , the standard completion of an unfinished project is defined as: Where T n Indicates the current time, Y ic Indicates the start time of the project numbered i, Y ip represents the planned completion time of the project numbered i; The milestone progress score is calculated as follows: m i is the total number of uncompleted milestones in project number i; It represents the total number of uncompleted milestones after weighting the uncompleted milestones of all projects; Iteration status score: Based on the feature values extracted when selecting the demand flow feature attributes, the total number of days in the specified time is d, the total number of iterations is m, and the formula for the average number of iterations per day is as follows: Iteration status score: S l =100×30×a The overall scores for the demand flow process are as follows: S=0.4×0.3×S i +0.4×0.7×S j +0.5×S k +0.1×S l ; When displaying data, "Department Key Tasks" is displayed in a pie chart based on the five levels of completion when selecting the demand flow characteristic attributes. Milestone Progress is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart allows you to drill down to the specific milestone completion status. "Iterations" are displayed using a bar chart by team. Clicking a team's bar chart displays a dot chart of the entire iteration process, showing the chronological relationship of iterations. Use a radar chart to display the team score data obtained during data analysis, and also compare this data with the average score data of all teams.

2. A requirements flow efficiency evaluation system based on the software development process, characterized by: include: Team demand configuration module, demand flow characteristic attribute selection module, data collection module, data analysis module, data display module. The demand flow characteristic attribute selection module obtains information from the team demand configuration module, the data collection module obtains information from the demand flow characteristic attribute selection module, the data analysis module obtains information from the data collection module, and the data display module obtains information from the data analysis module. The team demand configuration module is used to obtain the corresponding relationship between demand and project from the demand management module of the project management system; obtain the corresponding relationship between R&D team and project from the R&D personnel management system; and store the corresponding relationship between R&D team and project in the database; Open the API interface to the outside world, and each team can dynamically add, delete or modify the corresponding projects according to its own organizational structure adjustment; The demand flow characteristic attribute selection module is used to select demand task statistics-related attributes, milestone-related attributes, release iteration-related attributes and key task-related attributes as performance indicators for evaluating demand flow throughout the entire life cycle of demand flow; Demand task statistics: Demand task statistics include three sub-attributes: Ongoing Demand Tasks, Overdue Demand Tasks, and Interval Demand Task Throughput. These statistics include the number of tasks whose completion times fall within the demand deadline, the number of tasks that remain uncompleted within the demand deadline, and the average daily number of completed tasks within the selected time period. Milestone Progress: A milestone represents a significant change or step in project development. "Milestone Progress" statistics capture the number of milestones at different levels of completion, measuring the health of key nodes in the demand flow. Currently, milestone completion levels are defined as 0-49%, 50%-79%, 80%-99%, and 100%. Iterations: Iterations count the number of times a requirement task is iteratively developed within a specified time period. The more iterations within a specified time period, the smoother the demand flow and the smoother the project progress. Departmental key tasks: These are important indicators that reflect demand flow beyond milestones. Currently, departmental key tasks are divided into four levels: 0-49%, 50%-79%, 80%-99%, and 100%. Statistics are collected to determine the number of tasks that fall within these four ranges. The data collection module is used to obtain the requirements to be collected according to the team requirement configuration stored in the database; call the API in the requirement management system to obtain the original data of the requirement process; process the original data according to statistical requirements and combine it into useful information items; and store the generated information items in the database; Demand task completion status score: Based on the feature values extracted when selecting the demand flow feature attributes, if the number of overdue demand tasks within a specified time is n, the demand task completion status score is as follows: S i ＝100×(0.5 1 / 3 ) (0.5×n) Demand task throughput status score: Based on the feature values extracted when selecting the demand flow feature attributes, the interval demand task throughput is r, and the number of team members is p. The formula for per capita demand task throughput is as follows: Milestone progress score: Based on the feature values extracted when selecting the demand flow feature attributes, the number of milestones completed at a specified time point is W f The number of unfinished milestones is W u , the milestone completion degree of an unfinished project is Y io , the standard completion of an unfinished project is defined as: Where T n Indicates the current time, Y ic Indicates the start time of the project numbered i, Y ip represents the planned completion time of the project numbered i; The milestone score calculation formula is as follows: m i is the total number of uncompleted milestones in project number i; It represents the total number of uncompleted milestones after weighting the uncompleted milestones of all projects; Iteration status score: Based on the feature values extracted when selecting the demand flow feature attributes, the total number of days in the specified time is d, the total number of iterations is m, and the formula for the average number of iterations per day is as follows: Iteration status score: S l =100×30×a The overall scores for the demand flow process are as follows: S=0.4×0.3×S i +0.4×0.7×S j +0.5×S k +0.1×S l ; The data analysis module is used to measure the health of demand flow through five scores during the data analysis process: "demand task completion status score", "demand task throughput status score", "milestone progress status score", "iteration status score" and "overall score of the demand process", to guide the team's further decision-making; the data display module is used to perform secondary statistics on demand flow data in demand management according to pre-specified attributes and display the statistical data externally through charts; "Key Department Tasks" is displayed in a pie chart based on the five levels of completion when selecting the demand flow characteristic attributes; Milestone Progress is displayed using a bar chart based on the team dimension. Clicking on a team's bar chart allows you to drill down to the specific milestone completion status. "Iterations" are displayed using a bar chart by team. Clicking a team's bar chart displays a dot chart of the entire iteration process, showing the chronological relationship of iterations. Use a radar chart to display the team score data obtained during data analysis, and also compare this data with the average score data of all teams.

Images