@inbook {18418,
	title = {Protocols in the use of empirical software engineering artifacts},
	booktitle = {Empirical Software EngineeringEmpirical Software Engineering},
	volume = {12},
	year = {2007},
	month = {2007///},
	pages = {107 - 119},
	publisher = {Springer},
	organization = {Springer},
	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 experiences 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. Such an agreement 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). 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.},
	author = {Basili, Victor R. and Zelkowitz, Marvin V and Sj{\o}berg,D. I.K and Johnson,P. and Cowling,A. J}
}
