AN EMPIRICAL TEST OF OBJECT-BASED OUTPUT MEASUREMENT METRICS IN A COMPUTER AIDED SOFTWARE ENGINEERING (CASE) ENVIRONMENT

Existing output measurement metrics for cost estimation and development productivity need to be re-examined to determine their performance in computer aided software engineering (CASE) development environments. This paper critiques and empirically evaluates four approaches to the measurement of outputs. Two of the metrics, raw function counts and function points, are based on the function point analysis methodology pioneered by Albrecht and Gaffney at IBM (ALBR83). The second two, object counts and object points, are based on a new approach -- object points analysis -- that is introduced here for the first time. The latter metrics are specialized for output measurement in object-based CASE environments that include a centralized object repository. Estimation results for nineteen large-scale CASE projects show that the new metrics have the potential to yield as accurate, yet easier to obtain estimates than function points-based measures.Information Systems Working Papers Serie

TRACKING THE 'LIFE CYCLE TRAJECTORY': METRICS AND MEASURES FOR CONTROLLING PRODUCTIVITY OF COMPUTER AIDED SOFTWARE ENGINEERING (CASE) DEVELOPMENT

This paper proposes a new vision for the measurement and management of development productivity related to computer aided software engineering (CASE) technology. We propose that productivity be monitored and controlled in each phase of software development life cycle, a measurement approach we have termed life cycle trajectory measurement. Recent advances in CASE technology that make low cost automated measurement possible have made it feasible to collect life cycle trajectory measures. We suggest that current approaches for productivity management involve the use of static metrics that are available only at the beginning and end of the project. Yet the depth of the insights needed to make proactive adjustments in the software development process requires monitoring the range of activities across the entire software development life cycle. This can only be accomplished with metrics that can measure performance parameters in each phase of the life cycle. We develop metrics that have the ability to measure and estimate software outputs from each intermediate phase of the development life cycle. These metrics are based on a count of the objects and modules that are used as building blocks for application development in repository object-based CASE environments. The viability of such object-based metrics for life cycle trajectory measurement has been empirically tested for the software construction phase using project data generated in Integrated CASE development environments.Information Systems Working Papers Serie

Next generation software environments : principles, problems, and research directions

The past decade has seen a burgeoning of research and development in software environments. Conferences have been devoted to the topic of practical environments, journal papers produced, and commercial systems sold. Given all the activity, one might expect a great deal of consensus on issues, approaches, and techniques. This is not the case, however. Indeed, the term "environment" is still used in a variety of conflicting ways. Nevertheless substantial progress has been made and we are at least nearing consensus on many critical issues.The purpose of this paper is to characterize environments, describe several important principles that have emerged in the last decade or so, note current open problems, and describe some approaches to these problems, with particular emphasis on the activities of one large-scale research program, the Arcadia project. Consideration is also given to two related topics: empirical evaluation and technology transition. That is, how can environments and their constituents be evaluated, and how can new developments be moved effectively into the production sector

MANAGING DEVELOPMENT PRODUCTIVITY OF THE COMPUTER AIDED SOFTWARE ENGINEERING (CASE) PROCESS WITH DYNAMIC LIFE CYCLE TRAJECTORY METRICS

This paper proposes a new vision for the measurement and management of development productivity related to computer aided software engineering (CASE) technology. We propose that they be monitored and controlled via the application of dynamic software development "life cycle trajectory metrics." This view develops out of management accounting approaches for process control and recent advances in CASE technology that make automated measurement possible. We suggest that current approaches involve the use of "static metricsâ for estimation and evaluation, with the result that the depth of the insights they can provide to management is necessarily limited. They only provide "point estimatesâ of output or productivity at the beginning and end of the project. Yet to manage software development proactively for improved efficiency and effectiveness, management needs to track the range of activities and effort across the entire software development life cycle. This can only be accomplished when timely and relevant information is obtained about the software size output, as well as costs, via âdynamic metrics,â which provide a richer phase-by-phase view.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

OUTPUT MEASUREMENT METRICS IN AN OBJECT-ORIENTED COMPUTER AIDED SOFTWARE ENGINEERING (CASE) ENVIRONMENT: CRITIQUE, EVALUATION AND PROPOSAL

Output measurement metrics for the software development process need to be re-examined to determine their performance in the new, radically changed CASE development environment. This paper critiques and empirically evaluates several approaches to the measurement of outputs from the CASE process. The primary metric evaluated is the function points method developed by Albrecht. A second metric tested is a short-form variation of function points that is easier and quicker to calculate. We also propose a new output metric called object points and a related short-form, which are specialized for output measurement in object-oriented CASE environments that include a central object repository. These metrics are proposed as more intuitive and lower cost approaches to measuring the CASE outputs. Our preliminary results show that these metrics have the potential to yield as accurate, if not better, estimates than function points-based measures.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

Ada training evaluation and recommendations from the Gamma Ray Observatory Ada Development Team

The Ada training experiences of the Gamma Ray Observatory Ada development team are related, and recommendations are made concerning future Ada training for software developers. Training methods are evaluated, deficiencies in the training program are noted, and a recommended approach, including course outline, time allocation, and reference materials, is offered

TOOLS FOR MANAGING REPOSITORY OBJECTS

Information Systems Working Papers Serie