Computerized interactive tool for developing a software product that provides convergent metrics for estimating the final size of the product throughout the development process using the life-cycle model

• US 5,729,746 A
• Filed: 10/23/1995
• Issued: 03/17/1998
• Est. Priority Date: 12/08/1992
• Status: Expired due to Term

• Current Assignee: Ricky Jack Leonard
• Original Assignee: Ricky Jack Leonard
• Inventors: Leonard, Ricky Jack
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): Richey, Michael T.
• Application Number:
  US08/551,939
• Time in Patent Office: 876 Days
• Field of Search: 364/286, 395/701, 395/703, 395/702, 395/710
• US Class Current: 717/101
• CPC Class Codes: G06F 8/20 Software design

Abstract

A computerized interactive tool for developing a software product that provides estimates of the final lines of code of the software product at several points during the software development process to properly allocate programming effort resources. The estimates converge with actual results as the software development process progresses from one phase to the next.

Claims

1. An interactive computerized tool for estimating the final lines of code of the software product being developed at various phases of the development process using a life cycle model, including a requirements definition phase, requirements analysis phase, preliminary design phase and detailed design phase, said tool comprising:

a) a computer system including an interactive software operating in said computer system;

b) said software comprising the steps of asking the user whether the user is in the requirements definition phase, requirements analysis phase, preliminary design phase, or detailed design phase;

b) if at the requirements definition phase, said software including the steps of drawing data flow diagrams, leveling the data flow diagrams to generate a data dictionary data variables and calculating the final lines of code for the software product being developed from the data flows diagrams;

c) if at the requirements analysis phase, said software including the steps of updating the data dictionary data variables and calculating the final lines of code for the software product being developed from the number of data flow diagrams and the data dictionary;

d) if at the preliminary design phase, said software including the steps of transforming the data flow diagrams into structure charts to generate logic and control variables and calculating the final lines of code for the software product being developed from the data flow diagrams and the number of logic and control variables; and

e) if at the detailed design phase, said software including the steps of translating the mini-specs into pseudocode to generate static variables and calculating the final lines of code for the software product being developed from the data dictionary, logic and control variables and static variables.

2. The tool as in claim 1, wherein:

a) the lines of code is calculated at the requirements definition phase from the equation,

space="preserve" listing-type="equation">LOC.sub.n ≈

29.027+3.892*DF+e,

where

LOC_n =number of lines of code,

DF=number of data flows between modules,

e=standard error for regression.

3. The tool as in claim 1, wherein:

a) the lines of code is calculated at the requirements analysis phase from the equation,

space="preserve" listing-type="equation">LOC.sub.n =-11.434+3.072*DF+5.843*DD+e,

where

LOC_n =number of lines of code,

DF=number of data flows between modules,

DD=number of unique data elements in the data dictionary,

e=standard error for regression.

4. The tool as in claim 1, wherein:

a) the lines of code is estimated at the preliminary design phase from the equation,

space="preserve" listing-type="equation">LOC.sub.n ≈

-5.729+1.942*DF+12.654*LC+e,

where

LOC_n =number of lines of code,

DF=number of data flows between modules,

DD=number of data dictionary,

LC=the number of logical and control variables,

e=standard error for regression.

5. The tool as in claim 1, wherein:

a) the lines of code at the detailed design phase is calculated from the equation,

space="preserve" listing-type="equation">LOC.sub.n ≈

-11.593+1.799*DF+2.51*DD+8.545*LC+6.033*SV+e, ≈

1.583+5.429*(DD+LC+SV)+e, ≈

1.583+5.429*(VARS)+e,

where

LOC_n =lines of code,

DF=number of data flows between modules,

DD=number of unique data elements in the data dictionary,

LC=the number of logical and control variables,

SV=the number of static variables,

VARS=the sum of the number of unique variables within a software module,

e=standard error for regression.

6. A software storage disk, comprising:

a) disk;

b) software encoded on said disk;

c) said software being adapted for estimating the final lines of code of the software product being developed at various phases of the development process using a life cycle model, including a requirements definition phase, requirements analysis phase, preliminary design phase and detailed design phase;

d) said software comprising the steps of asking the user whether the user is in the requirements definition phase, requirements analysis phase, preliminary design phase, or detailed design phase;

e) if at the requirements definition phase, said software including the steps of drawing data flow diagrams, leveling the data flow diagrams to generate a data dictionary data variables and calculating the final lines of code for the software product being developed from the data flows diagrams;

f) if at the requirements analysis phase, said software including the steps of updating the data dictionary data variables and calculating the final lines of code for the software product being developed from the number of data flow diagrams and the data dictionary;

g) if at the preliminary design phase, said software including the steps of transforming the data flow diagrams into structure charts to generate logic and control variables and calculating the final lines of code for the software product being developed from the data flow diagrams and the number of logic and control variables; and

h) if at the detailed design phase, said software including the steps of translating the mini-specs into pseudocode to generate static variables and calculating the final lines of code for the software product being developed from the data dictionary, logic and control variables and static variables.

7. The disk as in claim 6, wherein:

a) the lines of code is calculated at the requirements definition phase from the equation,

space="preserve" listing-type="equation">LOC.sub.n ≈

29.027+3.892*DF+e,

where

LOC_n =number of lines of code,

DF=number of data flows between modules,

e=standard error for regression.

8. The disk as in claim 6, wherein:

a) the lines of code is calculated at the requirements analysis phase from the equation,

space="preserve" listing-type="equation">LOC.sub.n =-11.434+3.072*DF+5.843*DD+e,

where

LOC_n =number of lines of code,

DF=number of data flows between modules,

DD=number of unique data elements in the data dictionary,

e=standard error for regression.

9. The disk as in claim 6, wherein:

a) the lines of code is estimated at the preliminary design phase from the equation,

space="preserve" listing-type="equation">LOC.sub.n ≈

-5.729+1.942*DF+12.654*LC+e,

where

LOC_n =number of lines of code,

DF=number of data flows between modules,

DD=number of data dictionary,

LC=the number of logical and control variables,

e=standard error for regression.

10. The disk as in claim 6, wherein:

a) the lines of code at the detailed design phase is calculated from the equation,

space="preserve" listing-type="equation">LOC.sub.n ≈

-11.593+1.799*DF+2.51*DD+8.545*LC+6.033*SV+e, ≈

1.583+5.429*(DD+LC+SV)+e, ≈

1.583+5.429*(VARS)+e,

where

LOC_n =lines of code,

DF=number of data flows between modules,

DD=number of unique data elements in the data dictionary,

LC=the number of logical and control variables,

SV=the number of static variables,

VARS=the sum of the number of unique variables within a software module,

e=standard error for regression.