This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Size Estimation of Object-Oriented Systems
May 1990 (vol. 16 no. 5)
pp. 510-522

The strengths and weaknesses of existing size estimation techniques are discussed. The nature of software size estimation is considered. The proposed method takes advantage of a characteristic of object-oriented systems, the natural correspondence between specification and implementation, in order to enable users to come up with better size estimates at early stages of the software development cycle. Through a statistical approach the method also provides a confidence interval for the derived size estimates. The relation between the presented software sizing model and project cost estimation is also considered.

[1] A. J. Albrecht and J. E. Gaffney, "Software function, source lines of code, and development effort prediction: A software science validation,"IEEE Trans. Software Eng., vol. SE-9, no. 6, pp. 639-647, Nov. 1983.
[2] J. W. Bailey and V. R. Basili, "A meta-model for software development resource expenditures," inProc. 5th Int. Conf. on Software Eng., Mar. 1981, pp. 107-116.
[3] B. W. Boehm,Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
[4] G. Booch, "Object-oriented development,"IEEE Trans. Software Eng., vol. SE-12, pp. 211-221, Feb. 1986.
[5] R. N. Britcher and F. E. Gaffney, "Reliable size estimation for software decomposed as state machines," inProc. COMPSAC 1985, pp. 104-106.
[6] A. Bryant and J. A. Kirkham, "B. A. Boehm software engineering economics" A review essay,"ACM SIGSOFT Software Eng. Notes, vol. 8, no. 3, pp. 44-60, July 1983.
[7] S.D. Conte, H.E. Dunsmore, and V.Y. Shen,Software Engineering: Metrics and Models, Benjamin/Cummings, Menlo Park, Calif., 1986.
[8] F. R. Freiman and R. E. Park, "Price software model version 3: An overview" inProc. IEEE-PINY Workshop Quantitative Software Models, Oct. 1979, pp. 32-41.
[9] G. P. Fitsos, "Vocabulary effects in software science," inProc. COMPSAC 1980, pp. 751-756.
[10] S. Gross, K. B. Tom, and E. E. Ayers, "Software sizing and cost estimation study" inProc. 19th Annu. Dep. Defense Cost Analysis Symp., Xerox Training Center, Leesburg, VA, Sept. 17-20, 1985.
[11] J. R. Herd, J. N. Postak, W. E. Russel, and K. R. Stewart, "Software cost estimation study--Study results," Doty Associates, Inc., Rockville, MD, Final Tech. Rep. RADC-TR-77-220, June 1977.
[12] M. Itakura and A. Takayanagi, "A model for estimating program size and its evaluation," inProc. Sixth Int. Conf. Software Engineering, Sept. 1982, pp. 104-109.
[13] K. A. Jamsa, "Object-oriented design vs structured design--A student's perspective,"ACM SIGSOFT Software Eng. Notes, vol. 9, no. 1, pp. 43-49, Jan. 1984.
[14] R. W. Jensen, "A comparison of the Jensen and COCOMO schedule and cost estimation models," inProc. Int. Soc. Parametric Analysis, 1984, pp. 96-106.
[15] L. Ledbetter and B. Cox, "Software ICs,"Byte, vol. 10, no. 6, pp. 307-316, June 1985.
[16] A. V. Levitin, "On predicting program size by program vocabulary," inProc. IEEE COMPSAC 1985, pp. 98-103.
[17] A. V. Levitin, "How to measure program size and how not to," inProc. IEEE COMPSAC 1986, pp. 314-318.
[18] A. V. Levitin, "Investigating predictability of program size," inProc. IEEE COMPSAC 1987, pp. 231-235.
[19] B. Liskov and J. Guttag,Abstraction and Specification in Program Development. Cambridge, MA: MIT Press, 1986.
[20] T. de Marco,Structured Analysis and System Specification. Englewood Cliffs, NJ: Prentice-Hall, 1979.
[21] Parnas, D.L., "A Technique for Software Module Specification with Examples,"Comm. ACM, Vol. 15, No. 5, May 1972, pp. 330-336.
[22] Parnas, D.L. 1972. On the Criteria to be Used in Decomposing Systems into Modules,Communications of the ACM, Vol.15, pp. 1053-1058.
[23] G. A. Pascoe, "Elements of object-oriented programming,"Byte, vol. 11, no. 8, pp. 139-144, Aug. 1986.
[24] R.S. Pressman,Software Eng.: A Practitioner's Approach, McGraw-Hill, New York, N.Y., 1987.
[25] L. H. Putman, "A general empirical solution to the macro software sizing and estimation problem,"IEEE Trans. Software Eng., vol. SE-4, no. 4, pp. 345-361, July 1978.
[26] L. H. Putnam and A. Fitzsimmons, "Estimating software costs,"Datamation, pp. 189-198, Sept. 1979; continued inDatamation, pp. 171-178, Oct. 1979, pp. 137-140, Nov. 1979.
[27] Ramamoorthy, C.V. et al. 1984. "Software Engineering: Problems and Perspectives."IEEE Computer, October, pp. 191-209.
[28] D. T. Ross and K. E. Scoman, "Structured analysis for requirements definition,"IEEE Trans. Software Eng., vol. SE-3, no. 1, Jan. 1977.
[29] M. Stark and E. Seidewitz, "Towards a general object-oriented development methodology," Goddard Space Flight Center, Greenbelt, MD, Internal Rep., 1986.
[30] M. Stark and E. Seidewitz, "Towards a general object-oriented ADA life-cycle," inProc. Joint Ada Conf., Mar. 1987, pp. 213-222.
[31] E. Seidewitz, "General object-oriented software development: Background and experience," inProc. 21st Hawaii Int. Conf. System Science, Jan. 1988.
[32] M. Stefik and D. G. Babrow, "Object-oriented programming: Themes and variations,"AI Mag., vol. 6, no. 4, pp. 40-62, Dec. 1985.
[33] C. R. Symons, "Function point analysis: Difficulties and improvements,"IEEE Trans. Software Eng., vol. 14, no. 1, pp. 2-11, Jan. 1988.
[34] R. C. Tausworthe, "Deep space network software cost estimation model," Jet Propulsion Lab., Pasadena, CA, Publ. 81-7, 1981.
[35] L. Tesler, "Programming experiences (with object-oriented languages),"Byte, vol. 11, no. 8, pp. 195-206, Aug. 1986.
[36] C. E. Walston and C. P. Felix, "A method of programming measurement and estimation,"IBM Syst. J., vol. 16, no. 1, pp. 54-73, 1977.
[37] A. S. Wang, "The estimation of software size and effort: An approach based on the evolution of software metrics," Ph.D. dissertation, Dep. Comput. Sci., Purdue Univ., Aug. 1984.
[38] G. W. Weinberg and E. L. Schulman, "Goals and performance in computer programming,"Human Factors, vol. 16, no. 1, pp. 70-77, 1974.
[39] R. W. Wolverton, "Software costing," inSoftware Engineering, C. R. Vick and C. V. Ramamoorthy, Eds. New York: Van Nostrand, 1981.
[40] R. T. Yeh, P. Zave, A. P. Conn, and G. E. Cole, Jr., "Software requirements: New directions and perspectives," inSoftware Engineering, C. R. Vick and C. V. Ramamoorthy, Eds. New York: Van Nostrand, 1981.

Index Terms:
object-oriented systems; software size estimation; natural correspondence; specification; implementation; software development cycle; statistical approach; confidence interval; project cost estimation; object-oriented programming; software engineering.
Citation:
L.A. Laranjeira, "Software Size Estimation of Object-Oriented Systems," IEEE Transactions on Software Engineering, vol. 16, no. 5, pp. 510-522, May 1990, doi:10.1109/32.52774
Usage of this product signifies your acceptance of the Terms of Use.