Conducting experiments on software evolution

Authors:
Dag I. K. Sjøberg;Erik Arisholm;Magne Jørgensen
Affiliations:
Simula Research Laboratory, NO-0316 Oslo, NORWAY;Simula Research Laboratory, NO-0316 Oslo, NORWAY;Simula Research Laboratory, NO-0316 Oslo, NORWAY
Venue:
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Year:
2001

Citing 8
Cited 3

Object-oriented design

Object-oriented design
Ginger2: An Environment for Computer-Aided Empirical Software Engineering

IEEE Transactions on Software Engineering
Towards a framework for empirical assessment of changeability decay

Journal of Systems and Software - Special issue on empirical studies of software development and evolution
Empirical Studies of Evolving Systems

Empirical Software Engineering
Assessing the Changeability of two Object-Oriented Design Alternatives—a Controlled Experiment

Empirical Software Engineering
Using Students as Subjects—A Comparative Study ofStudents and Professionals in Lead-Time Impact Assessment

Empirical Software Engineering
Hints for Reviewing Empirical Work in Software Engineering

Empirical Software Engineering
Quality and Understandability of Use Case Models

ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming

Synthetic designs: a new form of true experimental design for use in information systems development

Proceedings of the 2007 ACM SIGMETRICS international conference on Measurement and modeling of computer systems
Applying empirical software engineering to software architecture: challenges and lessons learned

Empirical Software Engineering
The value of design rationale information

ACM Transactions on Software Engineering and Methodology (TOSEM) - In memoriam, fault detection and localization, formal methods, modeling and design

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software evolution is a challenging issue. For example, how do we judge whether one kind of structure supports evolution better than another kind of structure without comparing them in a fairly controlled way? In this paper we claim that certain aspects of software evolution should be evaluated in controlled experiments with first students, and then professionals, as subjects. Although we may have to compromise on longevity (due to enormous costs), we may observe cause-effect relationships in experiments that cannot be identified in case studies. We describe various challenges of conducting such experiments. We illustrate these issues by a controlled experiment on changeability decay conducted with students and a planned, more realistic extension with mostly software professionals as subjects.