MONITORING THE SOFTWARE ASSET: REPOSITORY EVALUATION OF SOFTWARE REUSE

Traditionally, software management has focused primarily upon cost control. Today, with the emerging capabilities of computer aided software engineering (CASE) and corresponding changes in the development process, the opportunity exists to view software development as an activity that creates reusable software assets, rather than just expenses, for the corporation. With this opportunity comes the need to monitor software at the corporate level, as well as at that of the individual software development project. Integrated CASE environments can support such monitoring. In this paper we propose the use of a new approach called repository evaluation, and illustrate it in an analysis of the evolving repository-based software assets of two large firms that have implemented integrated CASE development tools. The analysis shows that these tools have supported high levels of software reuse, but it also suggests that there remains considerable unexploited reuse potential. Our findings indicate that organizational changes will be required before the full potential of the new technology can be realized.Information Systems Working Papers Serie

REPOSITORY EVALUATION OF SOFTWARE REUSE

The traditional unit of analysis and control for software managers is the software project, and subsequently the resulting application system. Today, with the emerging capabilities of computer-aided software engineering (CASE) and corresponding changes in the development process, productivity gains can be realized by reusing portions of the organization's inventory of existing application designs and code. With this opportunity, however, comes the need to monitor software reuse at the corporate level, as well as at the level of the individual software development project. Integrated CASE environments can support such monitoring. We illustrate the use and benefits of repository evaluation of software reuse through an analysis of the evolving repositories of two large firms that recently implemented integrated CASE development tools. The analysis shows that these tools have supported high levels of software reuse, but it also suggests that there remains considerable unexploited reuse potential. Our findings indicate that organizational changes will be required before the full potential of the new technology can be realized.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

Reusable software component life cycle

In order to decrease the time and effort of the software development process and increase the quality of the software product significantly, software engineering required new technologies. Nowadays, most software engineering design is based on reuse of existing system or components. Also, it is become a main development approach for business and commercial systems. The concept of reusability is widely used in order to reduce cost, effort, and time of software development. Reusability also increases the productivity, maintainability, portability, and reliability of the software products. That is the reusable software components are evaluated several times in other systems before. The problems faced by software engineers is not lack of reuse, but lack of widespread, systematic reuse. They know how to do it, but they do it informally. Therefore, strong attention must be given to this concept. This study aims to propose a systematic framework considers the reusability through software life cycle from two sides, build-for-reuse and build-by-reuse. Furthermore, the repository of reusable software components is considered, and the evaluation criteria from both sides are proposed. Finally, an empirical validation is conducted by apply the developed framework on a case study

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

Repository Evaluation of Software Reuse: An Empirical Study

The traditional unit of analysis and control for software managers is the software project, and subsequently the resulting application system. Today, with the emerging capabilities of computer-aided software engineering (CASE) and corresponding changes in the development process, productivity gains can be realized by reusing portions of the organization's inventory of existing application designs and code. With this opportunity, however, comes the need to monitor software reuse at the corporate level, as well as at the level of the individual software development project. Integrated CASE environments can support such monitoring. We illustrate the use and benefits of repository evaluation of software reuse through an analysis of the evolving repositories of two large firms that recently implemented integrated CASE development tools. The analysis shows that these tools have supported high levels of software reuse, but it also suggests that there remains considerable unexploited reuse potential. Our findings indicate that organizational changes will be required before the full potential of the new technology can be realized.Information Systems Working Papers Serie

Requirements Processes: An Experience Report

Processes are certainly a key element in software management. Defining and using processes is believed to be an important factor towards quality. Our paper describes a general process language and the experience on its use by two different research teams with two different requirements processes. The process language is the basic representation for a process reuse repository implemented as a web application. The web application was used in order to describe a process for requirements management and a process for interface generation based on requirements information. We present both processes as well as an evaluation of the prototype. Our results are a confirmation of the importance of process reuse and of the possibility of sharing requirements information by publication, on the web, of requirements processes

Software development: A paradigm for the future

A new paradigm for software development that treats software development as an experimental activity is presented. It provides built-in mechanisms for learning how to develop software better and reusing previous experience in the forms of knowledge, processes, and products. It uses models and measures to aid in the tasks of characterization, evaluation and motivation. An organization scheme is proposed for separating the project-specific focus from the organization's learning and reuse focuses of software development. The implications of this approach for corporations, research and education are discussed and some research activities currently underway at the University of Maryland that support this approach are presented

Software Reuse in Agile Development Organizations - A Conceptual Management Tool

The reuse of knowledge is considered a major factor for increasing productivity and quality. In the software industry knowledge is embodied in software assets such as code components, functional designs and test cases. This kind of knowledge reuse is also referred to as software reuse. Although the benefits can be substantial, software reuse has never reached its full potential. Organizations are not aware of the different levels of reuse or do not know how to address reuse issues. This paper proposes a conceptual management tool for supporting software reuse. Furthermore the paper presents the findings of the application of the management tool in an agile development organization

OntoMaven: Maven-based Ontology Development and Management of Distributed Ontology Repositories

In collaborative agile ontology development projects support for modular reuse of ontologies from large existing remote repositories, ontology project life cycle management, and transitive dependency management are important needs. The Apache Maven approach has proven its success in distributed collaborative Software Engineering by its widespread adoption. The contribution of this paper is a new design artifact called OntoMaven. OntoMaven adopts the Maven-based development methodology and adapts its concepts to knowledge engineering for Maven-based ontology development and management of ontology artifacts in distributed ontology repositories.Comment: Pre-print submission to 9th International Workshop on Semantic Web Enabled Software Engineering (SWESE2013). Berlin, Germany, December 2-5, 201