Populating software repositories: Incentives and domain-specific software

doi:10.1016/0164-1212(94)00133-8

Journal of Systems and Software

Volume 30, Issue 3, September 1995, Pages 187-199

https://doi.org/10.1016/0164-1212(94)00133-8 Get rights and content

Abstract

Reusable Software Libraries (RSLs) often form the core on an organizational reuse strategy. Although RSLs provide a place to deposit software for use by others, RSLs do not guarantee reuse success. The implementation of an RSL depends on many factors including the availability of quality and useful software. Domain-specific considerations most often determine the usefulness of software and therefore should influence how an organization populates an RSL. This article presents IBM's¹ experiences with a corporate RSL, reuse incentive programs, and summarizes the results of an enterprise-wide initiative to develop reusable software for the RSL. The article explains some of the issues surrounding a large RSL and defines a three-phased progression typical of corporate reuse libraries.

References (36)

Air Force Defense Software Repository System (AFDSRS). Contact the AFDSRS Customer Assistance Office, Bldg 856, Room...
Guillermo Arango
Domain Analysis Methods
B.H. Barnes et al.
Making Reuse Cost Effective
IEEE Software
(1991)
Dorothea Bauer
A Reusable Parts Center
IBM Systems Journal
(1993)
Roger Beck et al.
Architectures for Large-Scale Reuse
AT & T Technical Journal
(1992)
Klaus Berg
CLASSLIB-Class Management and Reuse Suupport on a MVS Mainframe
Mauro Ciardi et al.
SIP Library Project: A New Methodology for Designing OSI Systems Implementations
L. Coglianese et al.
Core Avionics Domain Analysis
L.H. Coglianese et al.
DSSA ADAGE: An Environment for Architecture Based Avionics Development
Sholom Cohen
Process and Products for Software Reuse in Ada

Cameron Donaldson

InQuisiX: An Electronic Catalog for Software Reuse

Darleen A. Druyun

Software Reuse Incentive Policy

Crosstalk: The Defense Software Engineering Report

(1994)

Albert Endres

Lessons Learned in an Industrial Software Lab

IEEE Software

(1993)

Hassan Gomaa

A Reuse-Oriented Approach for Structuring and Configuring Distribute Applications

Software Engineering Journal

(1993)

Martin Griss

Software Reuse: From Library to Factory

IBM Systems Journal

(1993)

Angelo J. Incorvaia et al.

Case Studies in Software Reuse

Sadahiro Isoda

Experience Report on Software Reuse Project: It's Structure, Activities, and Statistical Results

Manfred Lenz et al.

Software Reuse Through Building Blocks

IEEE Software

(1987)

Cited by (30)

Development of the Arctic Research Mapping Application (ARMAP): Interoperability challenges and solutions
2011, Computers and Geosciences
Citation Excerpt :
Implementing geospatial data standards increases data portability (Albrecht, 1999; Bernard and Ostländer, 2008) and encourages data providers to adapt standards that increase the interoperability, and therefore the likely popularity and usability of their data (Bernard and Ostländer, 2008; Díaz et al., 2011). Software developers are also benefited by the adoption of data standards to improve access to data, and data manipulation, fusion, and visualization, thereby improving the functionality, scalability, and usefulness of their software (Poulin, 1995; The Joint Data Standards Study, 2005). Our experience has shown that having ready access to Arctic data and metadata has been one of the most time-consuming elements during the development of ARMAP.
Ensuring interoperability between WebGIS applications is essential for maximizing access to data, data sharing, and data manipulation. Interoperability is maximized through the adoption of best practices, use of open standards, and utilization of spatial data infrastructure (SDI). While many of the interoperability challenges like infrastructure, data exchange, and file formats are common between applications, some regions like the Arctic present specific challenges including the need for presenting data in one or more polar projections. This paper describes the Arctic Research Mapping Application (ARMAP) suite of online interactive maps, web services, and virtual globes (the ARMAP suite; http://armap.org/) and several of the interoperability challenges and solutions encountered in development to date. ARMAP is a unique science and logistic tool supporting United States and international Arctic science by providing users with the ability to access, query, and browse information and data. Access to data services include a text-based search utility, an Internet Map Server client (ArcIMS), a lightweight Flex client, ArcGIS Explorer and Google Earth virtual globes, and Open Geospatial Consortium (OGC) compliant web services, such as Web Map Service (WMS) and Web Feature Service (WFS). Through the ARMAP suite, users can view a variety of Arctic map layers and explore pertinent information about United States Arctic research efforts. The Arctic Research Logistics Support Service (ARLSS) database is the informational underpinning of ARMAP. Avoiding duplication of effort has been a key priority in the development of the ARMAP applications. The ARMAP suite incorporates best practices that facilitate interoperability such as Federal Geographic Data Committee (FGDC) metadata standards, web services for embedding external data and serving framework layers, and open standards such as Open Geospatial Consortium (OGC) compliant web services. Many of the features and capabilities of ARMAP are expected to greatly enhance the development of an Arctic SDI.
Assessing the cost-effectiveness of software reuse: A model for planned reuse
2004, Journal of Systems and Software
Information systems development is typically acknowledged as an expensive and lengthy process, often producing code that is of uneven quality and difficult to maintain. Software reuse has been advocated as a means of revolutionizing this process. The claimed benefits from software reuse are reduction in development cost and time, improvement in software quality, increase in programmer productivity, and improvement in maintainability. Software reuse entails undeniable costs of creating, populating, and maintaining a library of reusable components. There is anecdotal evidence to suggest that some organizations benefit from reuse. However, many software developers practicing reuse claim these benefits without formal demonstration thereof. There is little research to suggest when the benefits are expected and to what extent they will be realized. For example, does a larger library of reusable components lead to increased savings? What is the impact of component size on the effectiveness of reuse? This research seeks to address some of these questions. It represents the first step in a series wherein the effects of software reuse on overall development effort and costs are modeled with a view to understanding when it is most effective.
Product information systems engineering: An approach for building product models by reuse of patterns
2003, Robotics and Computer-Integrated Manufacturing
This paper deals with an approach for Product Information Systems (PIS) engineering by reuse of patterns. Patterns form generic solutions to problems frequently occurring during PIS specification and implementation. The pattern approach provides an engineering guide to model data by organizing hierarchically and functionally modeling problems and the manner to resolve them. Their use would contribute to accelerate building and implementing product and process models during PIS specification and implementation. Two kind of patterns are distinguished: business patterns used for specification and providing solutions for application field problems and software patterns used for implementation and providing solutions for technical problems (software). A special interest is given to identify and specify different business patterns for product modeling during PIS specification.
However, a pattern-based approach can be developed only for disciplines which acquired a certain maturity, i.e. those for which there is both a consensus around a finite set of problems and a variety of known solutions for solving these problems. There is no universal agreement on the knowledge needed in product information systems, let alone on the representation of this knowledge and we therefore find it impossible to discuss product information systems without reference to what kind of knowledge is being managed. The first step consisted thus of constructing a general reference framework based on PIS concepts, providing a common terminology and a semantic of the principal concepts managed in PIS and proposing various models to fix these concepts. It forms a basis for exploring the problems frequently occurring during PIS specification. A pattern language is thus defined to resolve the identified problems, basing partially on existing design pattern catalogues.
Incentive compatibility and systematic software reuse
2001, Journal of Systems and Software
Citation Excerpt :
All three of these approaches – behaviorally based, outcome-based, and socialization-based – assume that some particular structure of work is given and necessarily leads to severe goal misalignments. This is indeed the case with the idealized view of reuse, and may serve to explain the amount of attention in the reuse literature devoted to countering incentive problems (Isoda, 1995; Poulin, 1995). However, we believe that attempting to introduce a radical new process and at the same time attempting to manage severe incentive conflicts is a high risk undertaking for most organizations.
Systematic software reuse has emerged as a promising route to improved software development productivity and quality. Many large corporations have initiated systematic reuse programs, and many reuse frameworks have been developed to guide organizations in these efforts. Yet, in spite of this, systematic reuse in practice has been difficult to achieve. In this paper we argue that a key inhibitor has been the incentive conflict inherent in traditional programs of reuse. We reach this conclusion based on an analysis of interview data gathered from 15 projects across eight different sites in a company once viewed as a leader in the reuse movement. We found that one key contributor to the absence of widespread systematic reuse in this firm was a perception among project teams that reuse was incompatible with prevailing project team priorities and incentives, such as to complete projects on time and within budget. Based on this finding, we undertake a survey of different approaches to establishing reuse described in the literature, and analyze them to determine whether incentive incompatibility is inherent in the nature of software reuse for larger organizations. We conclude that it is not, and provide guidance on how such organizations can design an incentive-compatible program of reuse, i.e., one that generates a climate in which developers and teams view reuse as having a more favorable “value proposition” according to the prevailing incentives operating at the team level.
Asset-based system and software system development - A frame-based approach
1998, Information and Software Technology
Previous works on software reusability has shown that an asset-based systems development strategy to software reuse is effective in identifying reusable design components. This strategy requires moving away from traditional and stand-alone applications development toward an integrated approach. This paper will review previous work on using frames for knowledge representation and will show how an implementation strategy based on the frame-based representation can be useful as a possible implementation approach for the asset-based systems development strategy.
Categorization of approaches to extend and reuse OCL
2022, Proceedings - ACM/IEEE 25th International Conference on Model Driven Engineering Languages and Systems, MODELS 2022: Companion Proceedings

View all citing articles on Scopus

View full text

Populating software repositories: Incentives and domain-specific software

Abstract

Domain Analysis Methods

Making Reuse Cost Effective

IEEE Software

A Reusable Parts Center

IBM Systems Journal

Architectures for Large-Scale Reuse

AT & T Technical Journal

CLASSLIB-Class Management and Reuse Suupport on a MVS Mainframe

SIP Library Project: A New Methodology for Designing OSI Systems Implementations

Core Avionics Domain Analysis

DSSA ADAGE: An Environment for Architecture Based Avionics Development

Process and Products for Software Reuse in Ada

InQuisiX: An Electronic Catalog for Software Reuse

Software Reuse Incentive Policy

Crosstalk: The Defense Software Engineering Report

Lessons Learned in an Industrial Software Lab

IEEE Software

A Reuse-Oriented Approach for Structuring and Configuring Distribute Applications

Software Engineering Journal

Software Reuse: From Library to Factory

IBM Systems Journal

Case Studies in Software Reuse

Experience Report on Software Reuse Project: It's Structure, Activities, and Statistical Results

Software Reuse Through Building Blocks

IEEE Software