The Community for Technology Leaders
Green Image
<p>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.</p>
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

D. Zweig, R. Banker, R. Kauffman and C. Wright, "Automating Output Size and Reuse Metrics in a Repository-Based Computer-Aided Software Engineering (CASE) Environment," in IEEE Transactions on Software Engineering, vol. 20, no. , pp. 169-187, 1994.
89 ms
(Ver 3.3 (11022016))