DMCA
Protocols in the use of Empirical Software Engineering Artifacts
| Citations: | 4 - 1 self |
BibTeX
@MISC{Basili_protocolsin,
author = {Victor R. Basili and Marvin V. Zelkowitz},
title = {Protocols in the use of Empirical Software Engineering Artifacts},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
If empirical software engineering is to grow as a valid scientific endeavor, the ability to acquire, use, share, and compare data collected from a variety of sources must be encouraged. This is necessary to validate the formal models being developed within computer science. However, within the empirical software engineering community this has not been easily accomplished. This paper analyses experience from a number of projects, and defines the issues, which include the following: (1) How should data, testbeds, and artifacts be shared? (2) What limits should be placed on who can use them and how? How does one limit potential misuse? (3) What is the appropriate way to credit the organization and individual that spent the effort collecting the data, developing the testbed, and building the artifact? (4) Once shared, who owns the evolved asset? As a solution to these issues, the paper proposes a framework for an empirical software engineering artifact agreement, which is intended to address the needs for both creator and user of such artifacts and should foster a market in making available and using such artifacts. If this framework for sharing software engineering artifacts is commonly accepted, it should encourage artifact owners to make the artifacts accessible to others (gaining credit is more likely and misuse is less likely), and it may be easier for other researchers to request artifacts since there will be a well-defined protocol for how to deal with relevant matters. 1.
Keyphrases
empirical software engineering artifact well-defined protocol limit potential misuse empirical software engineering community evolved asset relevant matter software engineering artifact empirical software engineering artifact agreement valid scientific endeavor empirical software engineering appropriate way artifact owner formal model computer science
