scispace - formally typeset
Open AccessJournal ArticleDOI

Methodological Issues in Observational Studies

Nyyti Saarimäki
- 14 Nov 2019 - 
- Vol. 44, Iss: 3, pp 24-24
TLDR
In this paper, the authors define a methodology for applying observational studies in empirical software engineering, providing guidelines on how to conduct such studies, how to analyze the data, and how to report the studies themselves.
Abstract
Background: Starting from the 1960s, practitioners and researchers have looked for ways to empirically investigate new technologies such as inspecting the effectiveness of new methods, tools, or practices. With this purpose, the empirical software engineering domain started to identify different empirical methods, borrowing them from various domains such as medicine, biology, and psychology. Nowadays, a variety of empirical methods are commonly applied in software engineering, ranging from controlled and quasi-controlled experiments to case studies, from systematic literature reviews to the newly introduced multivocal literature reviews. However, to date, the only available method for proving any cause-effect relationship are controlled experiments. Objectives: The goal of the thesis is introducing new methodologies for studying causality in empirical software engineering. Methods: Other fields use observational studies for proving causality. They allow observing the effect of a risk factor and testing this without trying to change who is or is not exposed to it. As an example, with an observational study it is possible to observe the effect of pollution on the growth of a forest or the effect of different factors on development productivity without the need of waiting years for the forest to grow or exposing developers to a specific treatment. Conclusion: In this thesis, we aim at defining a methodology for applying observational studies in empirical software engineering, providing guidelines on how to conduct such studies, how to analyze the data, and how to report the studies themselves.

read more

Citations
More filters
Book

Test Driven Development: By Example

Beck
TL;DR: Drive development with automated tests, a style of development called “Test-Driven Development” (TDD for short), which aims to dramatically reduce the defect density of code and make the subject of work crystal clear to all involved.
Proceedings ArticleDOI

The Technical Debt Dataset

TL;DR: The Technical debt dataset is proposed, a curated set of project measurement data from 33 Java projects from the Apache Software Foundation that aims to open up diverse opportunities for Technical Debt research, enabling researchers to compare results on common projects.
Journal ArticleDOI

Does code quality affect pull request acceptance? An empirical study

TL;DR: This work investigates whether code quality issues such as code smells, antipatterns, and coding style violations in the pull request code affect the chance of its acceptance when reviewed by a maintainer of the project.
References
More filters
Journal ArticleDOI

A spiral model of software development and enhancement

Barry Boehm
- 01 May 1988 - 
TL;DR: An outline is given of the process steps involved in the spiral model, an evolving risk-driven approach that provides a framework for guiding the software process and its application to a software project is shown.
Proceedings ArticleDOI

Performing systematic literature reviews in software engineering

TL;DR: This tutorial is designed to provide an introduction to the role, form and processes involved in performing Systematic Literature Reviews, and to gain the knowledge needed to conduct systematic reviews of their own.
Journal ArticleDOI

Guidelines for conducting and reporting case study research in software engineering

TL;DR: This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies, and presents recommended practices and evaluated checklists for researchers and readers of case study research.
Journal ArticleDOI

Randomized, controlled trials, observational studies, and the hierarchy of research designs.

TL;DR: The results of well-designed observational studies (with either a cohort or a case-control design) do not systematically overestimate the magnitude of the effects of treatment as compared with those in randomized, controlled trials on the same topic.