System and method to estimate resource usage for a software development project

• US 20030018952A1
• Filed: 07/13/2001
• Published: 01/23/2003
• Est. Priority Date: 07/13/2001
• Status: Abandoned Application

• Current Assignee: William H. Roetzheim
• Original Assignee: William H. Roetzheim
• Inventors: Roetzheim, William H.
• Application Number:
  US09/904,644
• Publication Number:
  US 20030018952A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 11/3616 using software metrics
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

An adaptable resource estimating system operates on a computer system and uses a highly flexible parametric rule. The parametric rule receives values, including values relating to each of a software project type, a software lifecycle, and a software standard. More particularly, a user chooses a software project type from a set of available software project types, a software lifecycle from a set of available software lifecycles, and a software standard from a set of available software standards. The chosen project type, lifecycle, and standard may be related or unrelated, and may be changed independent of the others. Responsive to choosing the project type, the lifecycle, and the standard, the adaptable resource estimating system sets values in the parametric rule. The parametric rule executes and resource estimates are prepared regarding resource utilization for the particular chosen project type, lifecycle, and standard.

Claims

1. A method of estimating an outcome for a software development project, comprising:

selecting a parametric rule having a plurality of variables;

choosing a project type, a lifecycle, and a standard for the software development project;

assigning a type factor responsive to choosing the project type;

assigning a lifecycle factor responsive to choosing the lifecycle;

assigning a standard factor responsive to choosing the standard;

using the type factor, the lifecycle factor, and the standard factor as variables in the parametric rule; and

generating the outcome.

2. The method according to claim 1 wherein the outcome is a software effort estimate for the software development project.

3. The method according to claim 1 wherein the outcome is a software defect report for the software development project.

4. The method according to claim 1 wherein the outcome is a software development schedule for the software development project.

5. The method according to claim 1 wherein the outcome is a estimated cost for the software development project.

6. The method according to claim 1 wherein assigning the lifecycle factor includes extracting the lifecycle factor from a look-up table.

7. The method according to claim 1 wherein assigning the standard factor includes extracting the standard factor from a look-up table.

8. The method according to claim 1 wherein using the lifecycle factor includes using the lifecycle factor as a linear variable in the parametric rule.

9. The method according to claim 1 wherein using the standard factor includes using the standard factor as a linear variable in the parametric rule.

10. The method according to claim 1 wherein using the lifecycle factor includes using the an inverse of the lifecycle factor as a linear variable in the parametric rule.

11. The method according to claim 1 wherein using the standard factor includes using an inverse of the standard factor as a linear variable in the parametric rule.

12. The method according to claim 1 wherein the parametric rule further uses a size factor indicative of the number of lines of code to be written in the software development project.

13. The method according to claim 12 wherein the size factor is generated by using an internet point metric.

14. The method according to claim 12 wherein the size factor is generated by using Domino point metric.

15. The method according to claim 1 wherein the parametric rule further uses an environmental factor indicative of environmental conditions specific to the software development project.

16. The method according to claim 1 further including using a generic lifecycle template to generate a work product breakdown.

17. The method according to claim 16, wherein the chosen lifecycle is mapped to the generic lifecycle template.

18. The method according to claim 1 further including using a generic standard template to generate a document requirement report.

19. The method according to claim 16, wherein the chosen standard is mapped to the generic standard template.

20. The method according to claim 1 wherein the parametric rule uses the type factor, the lifecycle factor, the standard factor, an environment factor, and a size element.

21. The method according to claim 20 wherein the parametric rule is used to determine an effort, and has the general form of “

EFFORT=TYPE FACTOR*LIFECYCLE FACTOR*STANDARD FACTOR*ENVIRONMENT FACTOR*SIZE ELEMENT.”

22. The method according to claim 21 wherein the parametric rule is in the form of “

EFFORT=Σ

Env(l)*M(a)*Life*Std*KSLOC<sup>M(b)+Σ

Env(s)</sup>”

.

23. The method according to claim 21 further including using a defect parametric rule and a defect factor associated with the project type, the defect parametric rule having the form of “

DEFECT=DEFECT FACTOR*EFFORT*(1/LIFECYCLE FACTOR)*(1/STANDARD FACTOR)”

.

24. The method according to claim 21 further including using a schedule parametric rule and a schedule factor associated with the project type, the schedule parametric rule having the form of “

Schedule=T(a)*Effort<sup>T(b)+(Σ

env(s)/5</sup>)”

.