This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Effort Models for Early Estimation of Process Control Applications
October 1992 (vol. 18 no. 10)
pp. 915-924

Models are developed to estimate lines of code and function counts directly from user application features of process control systems early in the software development lifecycle. Since the application features are known with reasonable degree of confidence during early stages of development, it is possible to extend the use of the constructive cost model (COCOMO) and function-points-based approach for early software cost estimation. Alternative feature-based models that estimate size and effort using application features and productivity factors are developed. The feature-based models have been shown to estimate software effort with the least error.

[1] T. Abdel-Hamid and S. Madnick, "Impact of schedule estimation on software project behavior,"IEEE Software, pp. 69-75, July 1986.
[2] A.J. Albrecht and J. Gaffney, "Software function, source lines of code, and development effort prediction: A software science validation,"IEEE Trans. Software Eng., vol. SE-9, pp. 639-648, June 1983.
[3] A.J. Albrecht, "AD/M productivity measurement and estimate validation,"Document Number CIS&A Guideline 313, IBM, 1984.
[4] 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.
[5] R.D. Bankeret al., "Factors affecting software maintenance productivity: An exploratory study," inProc. 8th Int. Conf. Information Systems, pp. 160-175, 1987.
[6] R.D. Bankeret al., "Software Complexity and Maintainability,"Proc. 10th Int. Conf. on Information Systems, pp. 247-255, 1989.
[7] R.D. Bankeret al., "A model to evaluate variables impacting the productivity of software maintenance projects,"Management Science, vol. 37, pp. 1-18, Jan. 1991.
[8] M. Barbacciet al., "The software engineering institute: Bridging practice and potential,"IEEE Software, pp. 4-21, Nov. 1985.
[9] C. Behrens, "Measuring the productivity of computer systems development activities with function points,"IEEE Trans. Software Eng., vol. SE-9, pp. 648-652, June 1983.
[10] B. W. Boehm,Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
[11] B.W. Boehm, "Software engineering economics,"IEEE Trans. Software Eng., vol. SE-10, pp. 4-21, Jan. 1984.
[12] B. Boehm, "Improving software productivity,"Computer, vol. 20, no. 9, pp. 43-57, Sept. 1987.
[13] Conte, S.D. et al. 1986.Software Engineering Metrics and Models. Menlo Park, Calif., Benjamin/Cummings.
[14] F. Hayes-Rothet al., Building Expert Systems. New York: Addison Wesley, 1983.
[15] D.R. Jeffery, "The relationship between team size, experience, and attitudes and software development productivity," inProc. IEEE Computer Society COMPSAC 87, pp. 2-8, 1987.
[16] D.R. Jeffery and G. Low, "Calibrating estimation tools for software development,"Software Eng. J., pp. 215-221, July 1990.
[17] C. Jones,Programming Productivity. New York: McGraw-Hill, 1986.
[18] C. Jones, "The productivity report card,"Software News, vol. 6, pp. 19, Sept. 1986.
[19] C.F. Kemerer, "An empirical validation of software cost estimation models,"Commun. ACM, vol. 30, no. 5, pp. 416-429, May 1987.
[20] C.F. Kemerer, "Reliability of function points measurement: A field experiment," Working Paper, MIT, Cambridge, MA, 1990.
[21] C.F. Kemerer, "Software cost estimation models," inSoftware Engineers Reference Handbook. Surrey, UK: Butterworth's Scientific Limited, 1991.
[22] L.A. Marascuilo and R. C. Serlin,Statistical Methods for the Social and Behavioral Sciences. New York: Freeman, 1988.
[23] L.H. Putnam, "A general empirical solution to the macro software sizing problem,"IEEE Trans. Software Eng., vol. SE-4, pp. 345-361, Apr. 1978.
[24] H.A. Rubin, "Macro-estimation of software development parameters: The ESTIMACS system," inSOFTFAIR-Software Development: Tools, Techniques, and Alternatives. New York: IEEE, pp. 109-118, 1983.
[25] S. Siegel and N. J. Castellan,Nonparametric Statistics for the Behavioral Sciences. New York: McGraw-Hill, 1988.
[26] C.R. Symons, "Function point analysis: Difficulties and improvements,"IEEE Trans. Software Eng., vol. SE-14, pp. 2-11, Jan. 1988.
[27] S.M. Thebaut, "Model evaluation in software metrics research," in J. Gentle, Ed.,Computer Science and Statistics: Proc. Fifteenth Symp. Interface, pp. 277-285, 1983.
[28] S. Vicinanzaet al., "Software effort estimation: An exploratory study of expert performance,"Information Systems Research, vol. 2, pp. 243-262, Dec. 1991.
[29] C.D. Wrigley and A. S. Dexter, "Software development estimation models: A review and critique," inProc. ASAC Conf., University of Toronto, 1987.

Index Terms:
early estimation; process control applications; lines of code; function counts; user application features; process control systems; software development lifecycle; constructive cost model; function-points-based approach; software cost estimation; feature-based models; application features; productivity factors; software effort; least error; process computer control; software cost estimation; software engineering a
Citation:
T. Mukhopadhyay, S. Kekre, "Software Effort Models for Early Estimation of Process Control Applications," IEEE Transactions on Software Engineering, vol. 18, no. 10, pp. 915-924, Oct. 1992, doi:10.1109/32.163607
Usage of this product signifies your acceptance of the Terms of Use.