Reusability in software engineering

This paper surveys recent work concerning reusability in software engineering. The current directions in software reusability are discussed, and the two major approaches of reusable building blocks and reusable patterns studied. An extensive bibliography, parts of which are annotated, is included

FACTORS AFFECTING CODE REUSE: lMPLICATIONS FOR A MODEL OF COMPUTER AIDED SOFTWARE ENGINEERING DEVELOPMENT PERFORMANCE

An examination of code reuse at a large financial institution yields insights into the process of code reuse. The software development environment -- based on an integrated CASE system -- was designed to support code reuse, but at the end of its first two years we find that programmers are not taking full advantage of the reuse opportunities which the CASE environment provides, The organization has provided technical support for code reuse, but has not made organizational adjustments, and the technical solution alone does not suffice. We also review an existing economic model of CASE development performance that incorporates code reuse, suggesting refinements that are based upon our observations. Finally, we draw some conclusions about steps that managers can take to promote code reuse.Information Systems Working Papers Serie

THE BUSINESS CASE FOR AUTOMATING SOFTWARE METRICS IN OBJECT-ORIENTED COMPUTER AIDED SOFTWARE ENGINEERING ENVIRONMENTS

This paper makes the business case for automating the collection of software metrics for gauging development performance in integrated computer aided software engineering (CASE) environments that are characterized by an object-oriented development methodology and a centralized repository. The automation of function point analysis is discussed in the context of such an integrated CASE environment (ICE). We also discuss new metrics that describe three different dimensions of code reuse -- leverage, value and classification -- and examine the p,ossibility of utilizing objects as means to estimate software development labor and measure productivity. We argue that the automated collection of these software metrics opens up new avenues for refining the management of software development projects and controlling stra-egic costs.Information Systems Working Papers Serie

AUTOMATED SOFTWARE METRICS, REPOSITORY EVALUATION AND SOFTWARE ASSET MANAGEMENT: NEW TOOLS AND PERSPECTIVES FOR MANAGING INTEGRATED COMPUTER AIDED SOFTWARE ENGINEERING (I-CASE)

Automated collection of software metrics in computer aided software engineering (CASE) environments opens up new avenues for improving the management of software development operations, as well as shifting the focus of management's control efforts from "software projectâ to "software assets" stored in a centralized repository. Repository evaluation, a new direction for software metrics research in the 1990s, promises a fresh view of software development performance for a range of responsibility levels. We discuss the automation of function point and code reuse analysis in the context of an integrated CASE (I-CASE) environment deployed at a large investment bank in New York City. The development of an automated code reuse analysis tool prompted us to re-think how to measure and interpret code reuse in the I-CASE environment. The metrics we propose describe three dimensions of code reuse -- leverage, value and classification -- and we examine the value of applying them on a project and a repository-wide basis.Information Systems Working Papers Serie

AUTOMATING SOFTWARE DEVELOPMENT PRODUCTIVITY METRICS

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 -- especially object-oriented, integrated CASE -- have the potential to support the automation of this measurement. In this paper, we describe automated analyzers for function point and code reuse measurement. Both analyzers take advantage of the existence of a meta-model of the application system, stored within an object repository, which contains the necessary information about the application system. We also propose new metrics for code reuse analysis, including reuse leverage, reuse value and reuse classification. The state-of-the-art automated software metrics analyzers are illustrated in the context of an investment banking industry application.Information Systems Working Papers Serie

AUTOMATING OUTPUT SIZE AND REUSABILITY METRICS IN AN OBJECT-BASED COMPUTER AIDED SOFTWARE ENGINEERING (CASE) ENVIRONMENT

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 -- especially object-oriented, integrated CASE -- have the potential to support the automation of this measurement. In this paper, we discuss the conceptual development of automated analyzers for function point and software reusability 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 propose new metrics for software reusability measurement, including reuse leverage, reuse value and reuse classification. The functionality and analytic capabilities of state-of-the-art automated software metrics analyzers are illustrated in the context of an investment banking industry application.Information Systems Working Papers Serie

AUTOMATING OUTPUT SIZE AND REUSE METRICS IN A REPOSITORY-BASED COMPUTER AIDED SOFTWARE ENGINEERING (CASE) ENVIRONMENT

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 -- especially repository-based, integrated CASE -- have the potential to support the automation of this measurement. In this paper, we discuss 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.Information Systems Working Papers Serie

AUTOMATING OUTPUT SIZE AND REUSE METRICS IN A REPOSITORY-BASED COMPUTER AIDED SOFTWARE ENGINEERING (CASE) ENVIRONMENT

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 -- especially repository-based, integrated CASE -- have the potential to support the automation of this measurement. In this paper, we discuss 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.Information Systems Working Papers Serie