This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Automating Output Size and Reuse Metrics in a Repository-Based Computer-Aided Software Engineering (CASE) Environment
March 1994 (vol. 20 no. 3)
pp. 169-187

Measurement of software development productivity is needed in order to control software costs, but it is discouragingly labor-intensive and expensive. Computer-aided software engineering (CASE) technologies/spl minus/especially repository-based, integrated CASE/spl minus/have the potential to support the automation of this measurement. We discuss the conceptual basis for the development of automated analyzers for function point and software reuse measurement for object-based CASE. Both analyzers take advantage of the existence of a representation of the application system that is stored within an object repository, and that contains the necessary information about the application system. We also discuss metrics for software reuse measurement, including reuse leverage, reuse value, and reuse classification that are motivated by managerial requirements and the efforts, within industry and the IEEE, to standardize measurement. The functionality and the analytical capabilities of state-of-the-art automated software metrics analyzers are illustrated in the context of an investment banking industry application that is similar to systems deployed at the New York City-based investment bank where these tools were developed and tested.

[1] A. J. Albrecht, "Measuring application development productivity," inProc. Joint SHARE, GUIDE, and IBM Application Development Symp., IBM, pp. 83-92, Oct. 1979.
[2] 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. 9, no. 6, pp. 639-647, Nov. 1983.
[3] U. Apte, C. S. Sankar, M. Thakur, and J. Turner, "Reusability strategy for development of information systems: Implementation experience of a bank,"MIS Quart., vol. 14, no. 4, pp. 421-431, Dec. 1990.
[4] R. D. Banker and R. J. Kauffman, "Reuse and productivity: An empirical study of integrated computer-aided software engineering (ICASE) at the First Boston Corporation,"MIS Quart., vol. 15, no. 3, pp. 375-401, Sept. 1991.
[5] R. D. Banker, R. J. Kauffman, and R. Kumar, "An empirical assessment of object-based output measurement metrics in computer aided software engineering,"J. Mgmt. Inform. Syst., vol. 6, Winter 1991-1992.
[6] R. D. Banker, R. J. Kauffman, and D. Zweig, "Factors affecting code reuse: Implications for a model of computer aided software engineering development performance,"Ctr. for Research on Inform. Syst., Tech. Rep., Stern School of Business, New York Univ., New York, NY, 1990.
[7] R. D. Banker, R. J. Kauffman, and D. Zweig, "Repository evaluation of software reuse,"IEEE Trans. Software Eng., vol. 19, pp. 379-389, Apr. 1993.
[8] B. W. Boehm,Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
[9] B. W. Boehm, and P. N. Papaccio, "Understanding and controlling software costs,"IEEE Trans. Software Eng., vol. 13, pp. 1462-1477, Oct. 1988.
[10] T. B. Bollinger and S. L. Fleeger, "Economics of reuse: Issues and alternatives,"Inform. Software Tech., vol. 32, pp. 643-652, Dec. 1990.
[11] G. Booch, "What is and what isn't object-oriented design,"Ed Yourdon's Software J., vol. 2, pp. 14-21, Summer 1989.
[12] B. M. Bouldin, "CASE: Measuring productivity--What are you measuring? Why are you measuring it?"Software Mag., vol. 9, pp. 30-39, Aug. 1989.
[13] H. B. Carstensen, "A real example of reusing Ada software," inProc. Conf. on Software Reusability and Maintainability. Tysons Comer, VA: National Institute for Software Quality and Productivity, 1987.
[14] P. S. Chen, "The entity-relationship approach to information modeling and analysis," inProc. 2nd Int. Conf. on the Entity-Relationship Approach. Saugus, CA: ER Institute, 1981.
[15] R. D. Cruickshank and J. E. Gaffney, "An economics model of software reuse," presented atMITRE-Washington Econ. Analysis Ctr. Conf. on Analytical Methods in Software Eng. Econ. 1, Washington, DC, July 1991.
[16] R. D. Cruickshank and J. E. Gaffney, "A software cost model of reuse within a single system," presented atMITRE-Washington Econ. Analysis Ctr. Conf. on Analytical Methods in Software Eng. Econ. II, Washington, DC, July 1992.
[17] G. B. Davis, "Commentary on information systems: Productivity gains from computer aided software engineering,"Acct. Horizons, vol. 2, pp. 90-93, June 1988.
[18] J. Brian Dreger,Function Point Analysis. Englewood Cliffs, NJ: Prentice-Hall, 1989.
[19] M. F. Dunn and J. C. Knight, "Software reuse in an industrial setting: A case study," inProc. 13th Int. Conf. Software Eng.Austin, TX: IEEE Comput. Soc. Press, 1991, pp. 329-338.
[20] E. M. Dusink, "Towards a design philosophy for reuse," inProc. Reuse in Practice Workshop, J. Baldo and C. Braun, eds. Pittsburgh, PA: Software Engineering Institute, 1989.
[21] G. Fischer, "Cognitive view of reuse and redesign,"IEEE Software, vol. 4, no. 4, pp. 60-72, July 1987.
[22] G. Fischer, S.R. Henninger, and D.F. Redmiles, "Cognitive tools for locating and comprehending software objects for reuse," inProc. Thirteenth Int. Conf. Software Engineering, pp. 318-328, 1991.
[23] J. T. Fisher, "IBM's repository: Can Big Blue establish OS/2 EE as the professional programmer's front end?"DBMS, pp. 42-49, Jan. 1990.
[24] J. B. Frakes, T. J. Biggerstaff, R. Prieto-Diaz, K. Matsumura, and W. Shaefer, "Software reuse: Is it delivering?" inProc. 13th Int. Conf. Software Eng., Austin, TX, IEEE Comput. Soc. Press, May 13-17, 1991, pp. 52-59.
[25] J. E. Gaffney,An Economics Foundation for Software Reuse. Herndon, VA: Software Productivity Consortium, 1989.
[26] J. E. Gaffney, Jr. and T. A. Durek "Software reuse--Key to enhanced productivity: some quantitative models,"Inform. Software Technol., vol. 31, no. 5, pp. 258-267, June 1989.
[27] G. W. Grammas and J. R. Klein, "Software productivity as a strategic variable,"Interfaces, vol. 15, no. 3, pp. 116-126, May-June 1985.
[28] P. A. V. Hall, "Software components and reuse: Getting more out of your code,"Inform. Software Tech., vol. 29, no. 1, pp. 38-43, Jan.-Feb. 1987.
[29] A. Hazzah, "Making ends meet: Repository manager,"Software Magazine, pp. 59-72, Dec. 1989.
[30] J. W. Hooper and R. O. Chester,Software Reuse: Guidelines and Methods. New York: Plenum, 1991.
[31] E. Horowitz and J. Munson, "An expansive view of reusable software,"IEEE Trans. Soft. Eng., vol. SE-10, no. 5, pp. 477-487, Sept. 1985.
[32] T. C. Jones, "Reusability in programming: A survey of the state of the art,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 484-494, Sept. 1984.
[33] D. Sweetman and J Munoz, "Measures of effectiveness and the performance of parallel architectures," presented at the Systems, Man, Cybern. Conf., 1989.
[34] C. F. Kemerer, "Reliability of function points measurement: A field experiment,"Commun. ACM, to appear in Feb. 1993.
[35] B. W. Kernighan, "The UNIX system and software reusability,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 513-518, Sept. 1984.
[36] B. J. Kitaoka, "Managing large repositories for reuse," inProc. Reuse in Practice Workshop, J. Baldo and C. Braun, Eds. Pittsburgh, PA: Software Engineering Institute, 1989.
[37] R. G. Lanergan and C. A. Grasso, "Software engineering with reusable designs and code,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 498-501, Sept. 1984.
[38] R. G. Lanergan and B. A. Poynton, "Reusable code: The application development of the future," inProc. IBM SHARE/GUIDE Software Symp.Monterey, CA: IBM, 1979.
[39] M. Murata and H. Takagi, "Two-layer modeling for local area networks,"IEEE Trans. Commun., vol. 36, no. 9, pp. 1022-1034, Sept. 1988.
[40] G. C. Low and D. R. Jeffrey, "Function points in the estimation and evaluation of the software process,"IEEE Trans. Software Eng., vol. 16, pp. 64-71, Jan. 1990.
[41] R. F. Mathis, "The last 10 percent,"IEEE Trans. Software Eng., vol. SE-12, no. 6, pp. 705-712, June 1986.
[42] Y. Matsumoto, "Some experiences in promoting reusable software: Presentation in higher abstract levels,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 502-512, Sept. 1984.
[43] C. McClure,The Three Rs of Software Automation: Re-engineering, Repository, Reusability. Englewood Cliffs, NJ: Prentice-Hall, 1992.
[44] B. Meyer, "Reuse: The case for object-oriented design,"IEEE Software, vol. 4, no. 2, pp. 50-64, Mar. 1987.
[45] B. Meyers,Object Oriented Software Construction. Englewood Cliffs, NJ: Prentice-Hall, 1988.
[46] J. M. Neighbors, "The DRACO approach to constructing software from reusable components,"IEEE Trans. Software Eng., vol. SE-10, no. 5, pp. 564-574, Sept. 1984.
[47] R.J. Norman and J.F. Nunamaker, Jr., "CASE Productivity Perceptions of Software-Engineering Professionals,"Comm. ACM, Sept. 1989, pp. 1102-1108.
[48] R. J. Norman, W. Stevens, E. J. Chikofsky, J. Jenkins, and B. L. Rubenstein, "CASE at the start of the 1990s," inProc. 13th Int. Conf. Software Eng.Austin, TX: IEEE Comput. Soc. Press, 1991, pp. 128-142.
[49] J. F. Nunamaker, Jr. and M. Chen, "Software productivity: A framework of study and an approach to reusable components," inProc. 22nd Hawaii Int. Conf. Syst. Sci., IEEE, Jan. 1989, pp. 959-968.
[50] J. F. Nunamaker and M. Chen, "Software productivity: Gaining competitive edges in an information society," inProc. 22nd Hawaii Int. Conf. Syst. Sci., 1989, pp. 957-958.
[51] Parnas, D.L., "A Technique for Software Module Specification with Examples,"Comm. ACM, Vol. 15, No. 5, May 1972, pp. 330-336.
[52] Parnas, D.L. 1972. On the Criteria to be Used in Decomposing Systems into Modules,Communications of the ACM, Vol.15, pp. 1053-1058.
[53] D. L. Parnas, "Some hypotheses about the uses hierarchy for operating systems," Tech. Rep., Technische Hochschule Darmstadt, Darmstadt, Fed. Rep. Germany, 1976.
[54] D. L. Parnas, "Designing software for ease of extension and contraction,"IEEE Trans. Software Eng., vol. SE-5, no. 2, pp. 128-137, Mar. 1979.
[55] R. Prieto-Diaz, "Classifying software for reusability,"IEEE Software, vol. 4, no. 1, pp. 6-16, Jan. 1987.
[56] A. Pollack, "The move to modular software,"New York Times. pp. D1-D2, Apr. 23, 1990.
[57] F.J. Polster, "Reuse of Software through Generation of Partial Systems,"IEEE Trans. Software Eng., March 1986, pp. 402-416.
[58] D. J. Reifer,Joint Integrated Avionics Working Group (JIAWG) Reusable Software Program Operational Concept Document. Torrance, CA: Reifer Consultants Inc., 1990.
[59] J. A. Senn and J. L. Wynekoop, "Computer aided software engineering in perspective," Tech. Rep., Inform. Tech. Mgmt. Ctr., Coll. Business Admin., Georgia State Univ., 1990.
[60] V. Seppanen, "Reusability in software engineering," inTutorial: Software Reusability, P. Freeman, Ed. Austin, TX: IEEE Comput. Soc. Press, 1987, pp. 286-297.
[61] "Standard for Software Productivity Metrics," IEEE Standard #1045-1992, IEEE Comput. Soc. Press, 1992.
[62] M. E. Swanson and S. K. Curry, "Implementing an asset management program at GTE data services,"Inform. Mgmt., vol. 16, 1989.
[63] C. R. Symons,Extended Function Points with Entity Type Complexity Rules. London: Nolan, Norton&Co., 1984.
[64] C. R. Symons, "Function Point Analysis: Difficulties and improvements,"IEEE Trans. Software Eng., vol. 14, pp. 2-10, Jan. 1988.
[65] W. Tracz, "Making reuse a reality,"IEEE Software, vol. 4, no. 4, July 1987.
[66] W. Tracz, "Ada reusability efforts: A survey of the state of the practice," inTutorial: Software Reuse--Emerging Technology, Austin, TX: IEEE Comput. Soc. Press, 1988, pp. 23-32.
[67] W. Tracz,Software Reuse: Emerging Technology, IEEE CS Press, Order No. 846-01, Los Alamitos, Calif., 1988.
[68] R. Veryard, "Information and Software Economics,"Inform. Software Tech., vol. 31, pp. 226-230, June 1989.
[69] T. Vogelsong, "Reusable Ada packages for information system development (RAPID)--An operational center for the excellence of software reuse," inProc. Reuse in Practice Workshop, J. Baldo and C. Braun, eds. Pittsburgh, PA: Software Engineering Institute, 1989.
[70] K. Zwanzig,Handbook for Estimating Function Points, GUIDE Project--DP-1234, GUIDE Int., Nov. 1984.

Index Terms:
software tools; object-oriented programming; software metrics; software reusability; bank data processing; output size; reuse metrics; repository-based computer-aided software engineering environment; CASE environment; software development productivity; software cost control; integrated CASE; conceptual basis; automated analyzers; function point; software reuse measurement; object-based CASE; object repository; reuse leverage; reuse classification; managerial requirements; state-of-the-art automated software metrics analyzers; investment banking industry application
Citation:
R.D. Banker, R.J. Kauffman, C. Wright, D. Zweig, "Automating Output Size and Reuse Metrics in a Repository-Based Computer-Aided Software Engineering (CASE) Environment," IEEE Transactions on Software Engineering, vol. 20, no. 3, pp. 169-187, March 1994, doi:10.1109/32.268919
Usage of this product signifies your acceptance of the Terms of Use.