Cost estimation models for reuse and prototype SW development life-cycles

ABSTRACT

The Cocomo cost estimation model was developed to estimate the cost of developing software utilizing the waterfall life-cycle model. The assumptions in the waterfall model account for many software development situations, but do not account for the actual development process when the requirements are known to be unstable or incomplete or when extensive code and design information are reused. The prototype and reuse life-cycle models, respectively, were developed to model these specific situations. The assumptions made by any life-cycle model directly influence its cost estimation model; therefore, when the life-cycle model is inappropriate, its cost estimation model is also inappropriate. This makes the Cocomo cost estimation model inadequate for estimating development effort for software developed utilizing the prototype or reuse software development life-cycle models. Two cost estimation models, one for the prototype software life-cycle model and one for the reuse software life-cycle model, are presented. Each cost estimation model is derived from the basic Cocomo model and modified to fit the characteristics of its respective life-cycle model.

REFERENCES

• 1: [ALB79] Allan J. Albrecht, "Measuring Application Development Productivity," Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, Oct. 79.
• 2: [BAS75] Victor R. Basili and Albert J. Turner, "Iterative Enhancement: A Practical Technique for Software Development," IEEE Transactions on Software Engineering, SE-1:4, Dec. 75, pp, 390-396.
• 3: [BEC83] Leland L. Beck and Thomas E. Perkins, "A Survey of Software Engineering Practice: Tools, Methods, and Results," IEEE Transactions on Software Engineering, SE-9:5, Sep. 83, pp. 541-561.
• 4: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 5: Barry W. Boehm , Terence E. Gray , Thomas Seewaldt, Prototyping versus specifying: a multiproject experiment, IEEE Transactions on Software Engineering, v.10 n.3, p.290-302, May 1984 [doi>10.1109/TSE.1984.5010238]
• 6: D N Card , V E Church , W W Agresti, An empirical study of software design practices, IEEE Transactions on Software Engineering, v.12 n.2, p.264-271, Feb. 1986
• 7: [FRA87] W. B. Frakes and B. A. Nehmeh, "Software Reuse Through Information Retrieval," Proceedings of COMPCON '87, Feb. 23-27, 1987, pp. 380-384.
• 8: Hassan Gomaa , Douglas B.H. Scott, Prototyping as a tool in the specification of user requirements, Proceedings of the 5th international conference on Software engineering, p.333-342, March 09-12, 1981, San Diego, California, United States
• 9: S Hekmatpour, Experience with evolutionary prototyping in a large software project, ACM SIGSOFT Software Engineering Notes, v.12 n.1, p.38-41, Jan. 1987 [doi>10.1145/24574.24577]
• 10: [JON84] T. Capers Jones, "Reusability in Programming: A Survey of the State of the Art," IEEE Transactions on Software Engineering, SE-10:5, Sep. 84, pp. 488-494.
• 11: [JON86] T. Capers Jones, Programming Productivity, McGraw-Hill Book Co., New York, 1986.
• 12: [KAP79] G. Kapur, "Toward Software Engineering," Computerworld, 13:46, Nov. 79.
• 13: [LAN79] Robert G. Lanergan and Brian A. Poynton, "Reusable Code - The Application Development Technique of the Future," Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium. Oct. 79, 127-136.
• 14: [LAN84] Rubert G. Lanergan, "Software Engineering With Reusable Designs and Code," IEEE Transactions on Software Engineering, SE-10:5, Sep. 84, pp. 498-501.
• 15: [LEN87] Manfred Lenz, "Software Reuse Through Building Blocks," IEEE Software, Jul. 87, pp. 34-42.
• 16: [LOV88] Tom Love, "The Economics of Reuse," Proceedings, 1988 IEEE Spring COMPCON. Feb. 88, pp. 238- 241.
• 17: [MAT87] Yoshihiro Matsumoto, "A Software Factory. An Overall Approach to Software Production," IEEE Tutorial on Reusability, 1987, pp. 155-178.
• 18: [NEI84] James N. Neighbors, "The Draco Approach to Constructing Software from Reusable Components," IEEE Transactions on Software Engineering, SE-10:5, Sep. 84, pp. 564-574.
• 19: [ROY70] W. W. Royce, "Managing the Developement of Large Software Systems: Concepts and Techniques," Proceedings, WESCON, Aug. 1970.
• 20: [SCH83] Laura Scharer, "The Prototyping Alternative," ITT Programming, 1:1, 1983, pp. 34-43.
• 21: Richard W. Selby, Analysing software reuse at the project and module design levels, Proc. of the 1st European Software Engineering Conference on ESEC '87, p.212-220, December 1987, Strasbourg, France
• 22: [STA83] Thomas A. Standish, "Software Reuse," Proceedings, Workshop on Reusability in Programming, Sep. 83, pp. 45-49.
• 23: Will Tracz, Software reuse myths, ACM SIGSOFT Software Engineering Notes, v.13 n.1, p.17-21, Jan. 1988 [doi>10.1145/43857.43859]
• 24: [TRA88o] Will Tracz, "Software Reuse Maxims," ACM SIGSOFT Software Engineering Notes, 13:4, Oct. 88, pp. 28-31.
• 25: [WOL74] Roy W. Wolverton, "The Cost of Developing Large-Scale Software," IEEE Transactions on Computers, C-23:6, Jun. 74, pp. 615-636.
• 26: [ZEL80] Marvin V. Zelkowitz, "A Case Study In Rapid Prototyping," Software Practice and Experience, 10:12, Dec. 80, pp. 1037-1042.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Life cycle

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

  I. Computing Methodologies
  I.6 SIMULATION AND MODELING

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Life cycle

General Terms:
Economics, Measurement