@article {Simula.SE.116,
	title = {The Effect of Task Order on the Maintainability of Object-Oriented Software},
	journal = {Information and Software Technology},
	volume = {51},
	number = {2},
	year = {2009},
	month = {February},
	pages = {293-305},
	publisher = {Elsevier},
	abstract = {This paper presents results from a quasi-experiment that investigates how the sequence in which maintenance tasks are performed affects the time required to perform them and the functional correctness of the changes made. Specifically, the study compares how time required and correctness are affected by (1) starting with the easiest change task and progressively performing the more difficult tasks (Easy-First), versus (2) starting with the most difficult change task and progressively performing the easier tasks (Hard-First). In both cases, the experimental tasks were performed on two alternative types of design of a Java system to assess whether the choice of the design strategy moderates the effects of task order on effort and correctness. The results show that the time spent on making the changes is not affected significantly by the task order of the maintenance tasks, regardless of the type of design. However, the correctness of the maintainability tasks is significantly higher when the task order of the change tasks is Easy-First compared to Hard-First, again regardless of design. A possible explanation for the results is that a steeper learning curve (Hard-First) causes the programmer to create software that is less maintainable overall.},
	doi = {10.1016/j.infsof.2008.03.005},
	author = {Alf Inge {Wang} and Arisholm, Erik}
}
@article {Simula.SE.121,
	title = {Improving the Effectiveness of Root Cause Analysis in Post Mortem Analysis: a Controlled Experiment},
	journal = {Information and Software Technology},
	volume = {51},
	number = {1},
	year = {2009},
	month = {January},
	pages = {150-161},
	publisher = {Elsevier},
	abstract = {Retrospective analysis is a way to share knowledge following the completion of a project or major milestone. However, in the busy workday of a software project, there is rarely time for such reviews and there is a need for effective methods that will yield good results quickly without the need for external consultants or experts. Building on an existing method for retrospective analysis and theories of group involvement, we propose improvements to the root cause analysis phase of a lightweight retrospective analysis method known as post mortem analysis (PMA). In particular, to facilitate brainstorming during the root cause analysis phase of the PMA, we propose certain processual changes to facilitate more active individual participation and the use of less rigidly structured diagrams. We conducted a controlled experiment to compare this new variation of the method with the existing one, and conclude that in our setting of small software teams with no access to an experienced facilitator, the new variation is more effective when it comes to identifying possible root causes of problems and successes. The modified method also produced more specific starting points for improving the software development process.},
	doi = {doi:10.1016/j.infsof.2008.02.003},
	author = {Finn Olav {Bj{\o}rnson} and Alf Inge {Wang} and Arisholm, Erik}
}
@inproceedings {Simula.SE.3,
	title = {Educational Approach to an Experiment in a Software Archiecture Course},
	journal = {20th Conference on Software Engineering Education and Training (CSEE\&T 2007)},
	year = {2007},
	pages = {291-300},
	publisher = {IEEE Computer Society},
	type = {Conference},
	abstract = {This paper reports experiences from an experiment in a software architecture course where the focus was both on giving students valuable education as well as getting important empirical results. The paper describes how the experiment was integrated in the course, and presents an evaluation of the experiment from an educational point of view. Further, the paper reflects on the costs and the benefits of carrying out an experiment in the context of a software architecture course for the involved stakeholders namely the researchers, the students, and the instructors. The main results show that we managed to integrate the experiment in the course, that the students learned several aspects of software architecture through the experiment, and that the main motivation for putting effort into the experiment was to prove own skills. We also describe some guidelines for planning and executing experiments as a part of a software engineering course.},
	isbn = {0-7695-2893-7},
	author = {Alf Inge {Wang} and Arisholm, Erik and Jaccheri, Letizia}
}
@inbook {Sjoberg.2003.1,
	title = {Challenges and Recommendations When Increasing the Realism of Controlled Software Engineering Experiments},
	booktitle = {Empirical Methods and Studies in Software Engineering: Experiences from ESERNET},
	series = {Lecture Notes in Computer Science, Volume 2765},
	year = {2003},
	pages = {24-38},
	publisher = {Springer},
	organization = {Springer},
	chapter = {Part II: Method Chapters},
	address = {Berlin / Heidelberg},
	abstract = {An important goal of most empirical software engineering experiments is the transfer of the research results to industrial applications. To convince industry about the validity and applicability of the results of controlled software engineering experiments, the tasks, subjects and the environments should be as realistic as practically possible. Such experiments are, however, more demanding and expensive than experiments involving students, small tasks and pen-and-paper environments. This chapter describes challenges of increasing the realism of controlled experiments and lessons learned from the experiments that have been conducted at Simula Research Laboratory.},
	isbn = {978-3-540-40672-3},
	author = {Sj{\o}berg, Dag Ingar Kondrup and Anda, Bente Cecilie Dahlum and Arisholm, Erik and Dyb{\r a}, Tore and J{\o}rgensen, Magne and Karahasanovic, Amela and Vok{\'a}c, Marek},
	editor = {Conradi, Reidar and Alf Inge {Wang}}
}
