REGULATING APPLICATION TASK DEVELOPMENT

• US 20150324723A1
• Filed: 11/28/2012
• Published: 11/12/2015
• Est. Priority Date: 11/28/2012
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Ben-Yehuda, Itay, Shmiel, Ronen, Yom Tov, Nir
• Granted Patent: US 10,643,161 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/77 Software metrics
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work

Abstract

A technique includes receiving a plurality of metrics for a plurality of tasks associated with developing an application, where each of the metrics is associated with one of the tasks and indicates a progress of the associated task. The technique includes receiving weights, where each weight is associated with one of the tasks and indicates a user assigned importance of the associated task. The technique includes displaying with the tool an indicator to allow regulation of task development, where the displaying includes causing the tool to prioritize the tasks for future development of the application based at least in part on the metrics and the weights.

Claims

1. A method comprising:

receiving in a tool comprising a processor a plurality of metrics for a plurality of tasks associated with developing an application, each of the metrics being associated with one of the tasks and indicating a progress of the associated task;

receiving in the tool weights, each weight being associated with one of the tasks and indicating a user assigned importance of the associated task; and

displaying with the tool an indicator to allow regulation of task development, the displaying including causing the tool to prioritize the tasks for future development of the application based at least in part on the metrics and the weights.

2. The method of claim 1, wherein at least one of the metrics indicates a measure of the progress relative to a goal for the associated task.

3. The method of claim 2, wherein the goal identifies a performance threshold, and the at least one metric indicates a difference between a determined performance value for the associated task and the performance threshold.

4. The method of claim 2, wherein the goal identifies a code coverage threshold, and at the at least one metric indicates a difference between a determined code coverage for the associated task and the code coverage threshold.

5. The method of claim 1, wherein causing the tool to prioritize the tasks comprises:

for each task, determining a difference between a goal for the associated metric and the associated metric; and

for each task, determining an associated ranking of the task based at least in part on the difference and the associated weight.

6. The method of claim 1, wherein at least one of the tasks is refined in a plurality of iterations to develop the application, the method further comprising:

displaying the indicator to allow a progress of the metric to be tracked over the plurality of iterations.

7. The method of claim 1, wherein the tasks are refined in a plurality of iterations to develop the application, the method further comprising:

for each iteration, determining an aggregate value for the metrics; and

displaying the indicator to allow the aggregate value of the plurality of iterations to be tracked over time.

8. A system comprising:

an interface to receive data indicative of a plurality of metrics and a plurality of tool weights, wherein the plurality of tasks are associated with developing an application, each of the metrics being is associated with one of the tasks and indicates a progress of the associated task, and each weight is associated with one of the tasks and indicates a user assigned importance of the associated task; and

a tool comprising a processor to provide an indicator to allow regulation of task development, the tool being adapted to prioritize the tasks for future development of the application based at least in part on the metrics and the weights.

9. The system of claim 8, wherein at least one of the metrics indicates a measure of the progress relative to a goal for the associated task.

10. The system of claim 9, wherein the goal identifies a performance threshold, and at the at least one metric indicates a difference between a determined performance value for the associated task and the performance threshold.

11. The system of claim 9, wherein the goal identifies a code coverage threshold, and at the at least one metric indicates a difference between a determined code coverage for the associated task and the code coverage threshold.

12. The system of claim 8, wherein the tasks are refined in a plurality of iterations to develop the application, the tool being further adapted to:

for each iteration, determine an aggregate value for the metrics; and

generate an indicator to track the aggregate value of the plurality of iterations.

13. An article comprising a non-transitory storage medium to store instructions that when executed by a computer cause the computer to:

receive a plurality of metrics for a plurality of tasks associated with developing an application, each of the metrics being associated with one of the tasks and indicating a progress of the associated task;

receive weights, each weight being associated with one of the tasks and indicating a user assigned importance of the associated task; and

generate at least one indicator to regulate task development, the at least one indicator to prioritize the tasks for future development of the application based at least in part on the metrics and the weights.

14. The article of claim 13, wherein at least one of the metrics indicates a measure of the progress relative to a goal for the associated task.

15. The article of claim 14, wherein the goal identifies a performance threshold, and at the at least one metric indicates a difference between a determined performance value for the associated task and the performance threshold.