Guidelines for conducting and reporting case study research in software engineering

Runeson, Per; Höst, Martin

doi:10.1007/s10664-008-9102-8

Cited by 2,855 publications

(2,399 citation statements)

References 54 publications

Supporting

Mentioning

2,190

Contrasting

Unclassified

Order By: Relevance

“…This section discusses the validity of our case study using validation scheme defined by Runeson and Höst [2009]. The construct validity, the internal validity, and the external validity are presented.…”

Section: Validity Discussionmentioning

confidence: 99%

Usage of Tests in an Open-Source Community

Verhaeghe

Anquetil

Ducasse

et al. 2017

Proceedings of the 12th Edition of the International Workshop on Smalltalk Technologies

View full text Add to dashboard Cite

During the development, it is known that tests ensure the good behavior of applications and improve their quality. We studied developers testing behavior inside the Pharo community in the purpose to improve it. In this paper, we take inspiration from a paper of the literature to enhance our comprehension of test habits in our open source community. We report results of a field study on how often the developers use tests in their daily practice, whether they make use of tests selection and why they do. Results are strengthened by interviews with developers involved in the study. The main findings are that developers run tests every modifications of their code they did; most of the time they practice test selection (instead of launching an entire test suite); however they are not accurate in their selection; they change their selection depending on the duration of the tests and; contrary to expectation, test selection is not influenced by the size of the test suite.

show abstract

Section: Validity Discussionmentioning

confidence: 99%

Usage of Tests in an Open-Source Community

Verhaeghe

Anquetil

Ducasse

et al. 2017

Proceedings of the 12th Edition of the International Workshop on Smalltalk Technologies

View full text Add to dashboard Cite

show abstract

“…However, providing a general experiment design is demanding, as the design depends on the respective subject and context. Apart from the general experiment process, several smaller guidelines exist to direct researchers through the process, e.g., the goal template from the TAME project (Basili & Rombach, 1988), experimentation packages providing reusable designs, templates, and so forth (e.g., in the context of self-organizing project teams (Kuhrmann & Münch, 2016b), we created such a template; another example can be found in Fucci, Turhan & Oivo (2015)), and, pragmatically, case study designs, which can be derived from, e.g., Runeson & Höst (2009), who provide advice on planning and a guideline on reporting case study research.…”

Section: Formal and Semi-formal Experimentsmentioning

confidence: 99%

Guidelines for using empirical studies in software engineering education

Fagerholm

Kuhrmann

Münch

2017

PeerJ Computer Science

View full text Add to dashboard Cite

Software engineering education is under constant pressure to provide students with industry-relevant knowledge and skills. Educators must address issues beyond exercises and theories that can be directly rehearsed in small settings. Industry training has similar requirements of relevance as companies seek to keep their workforce up to date with technological advances. Real-life software development often deals with large, software-intensive systems and is influenced by the complex effects of teamwork and distributed software development, which are hard to demonstrate in an educational environment. A way to experience such effects and to increase the relevance of software engineering education is to apply empirical studies in teaching. In this paper, we show how different types of empirical studies can be used for educational purposes in software engineering. We give examples illustrating how to utilize empirical studies, discuss challenges, and derive an initial guideline that supports teachers to include empirical studies in software engineering courses. Furthermore, we give examples that show how empirical studies contribute to high-quality learning outcomes, to student motivation, and to the awareness of the advantages of applying software engineering principles. Having awareness, experience, and understanding of the actions required, students are more likely to apply such principles under real-life constraints in their working life.

show abstract

“…Runeson and Höst [Runeson and Höst 2009] identify four areas of validity threats for a case-study, such as ours:…”

Section: Validity Threatsmentioning

confidence: 99%

Assessing Large-Project Courses

Vasilevskaya

Broman

Sandahl

2015

ACM Trans. Comput. Educ.

View full text Add to dashboard Cite

In a modern computing curriculum, large project courses are essential to give students hands-on experience of working in a realistic software engineering project. Assessing such projects is, however, extremely challenging. There are various aspects and tradeoffs of assessments that can affect the course quality. Individual assessments can give fair grading of individuals, but may loose focus of the project as a group activity. Extensive teacher involvement is necessary for objective assessment, but may affect the way students are working. Continuous feedback to students can enhance learning, but may be hard to combine with fair assessment. Most previous work focuses on some specific assessment aspect, whereas we in this paper present an assessment model that consists of a collection of assessment activities, each covering different aspects. We have applied, developed, and improved these activities during a seven-year period. To evaluate the usefulness of the model, we perform questionnaire-based surveys over a two-years period. Furthermore, we design and execute an experiment that studies to what extent students can perform fair peer assessment and to what degree the assessments of students and teachers agree. We analyze the results, discuss findings, and summarize lessons learned.

show abstract

Guidelines for conducting and reporting case study research in software engineering

Cited by 2,855 publications

References 54 publications

Usage of Tests in an Open-Source Community

Usage of Tests in an Open-Source Community

Guidelines for using empirical studies in software engineering education

Assessing Large-Project Courses

Contact Info

Product

Resources

About