Six strategies for generalizing software engineering theories

    Research output: Contribution to journalArticleAcademicpeer-review

    46 Citations (Scopus)
    120 Downloads (Pure)

    Abstract

    General theories of software engineering must balance between providing full understanding of a single case and providing partial understanding of many cases. In this paper we argue that for theories to be useful in practice, they should give sufficient understanding of a sufficiently large class of cases, without having to be universal or complete. We provide six strategies for developing such theories of the middle range. In lab-to-lab strategies, theories of laboratory phenomena are developed and generalized to other laboratory phenomena. This is a characteristic strategy for basic science. In lab-to-field strategies, theories are developed of artifacts that first operate under idealized laboratory conditions, which are then scaled up until they can operate under uncontrolled field conditions. This is the characteristic strategy for the engineering sciences. In case-based strategies, we generalize about components of real-world cases, that are supposed to exhibit less variation than the cases as a whole. In sample-based strategies, we generalize about the aggregate behavior of samples of cases, which can exhibit patterns not visible at the case level. We discuss three examples of sample-based strategies. Throughout the paper, we use examples of theories and generalization strategies from software engineering to illustrate our analysis. The paper concludes with a discussion of related work and implications for empirical software engineering research.
    Original languageUndefined
    Pages (from-to)136-152
    Number of pages17
    JournalScience of computer programming
    Volume101
    DOIs
    Publication statusPublished - Apr 2015

    Keywords

    • IS-Design science methodology
    • SCS-Services
    • IR-93500
    • METIS-312474
    • EWI-25555

    Cite this

    @article{26c990771bd645428c33ea107259ceb5,
    title = "Six strategies for generalizing software engineering theories",
    abstract = "General theories of software engineering must balance between providing full understanding of a single case and providing partial understanding of many cases. In this paper we argue that for theories to be useful in practice, they should give sufficient understanding of a sufficiently large class of cases, without having to be universal or complete. We provide six strategies for developing such theories of the middle range. In lab-to-lab strategies, theories of laboratory phenomena are developed and generalized to other laboratory phenomena. This is a characteristic strategy for basic science. In lab-to-field strategies, theories are developed of artifacts that first operate under idealized laboratory conditions, which are then scaled up until they can operate under uncontrolled field conditions. This is the characteristic strategy for the engineering sciences. In case-based strategies, we generalize about components of real-world cases, that are supposed to exhibit less variation than the cases as a whole. In sample-based strategies, we generalize about the aggregate behavior of samples of cases, which can exhibit patterns not visible at the case level. We discuss three examples of sample-based strategies. Throughout the paper, we use examples of theories and generalization strategies from software engineering to illustrate our analysis. The paper concludes with a discussion of related work and implications for empirical software engineering research.",
    keywords = "IS-Design science methodology, SCS-Services, IR-93500, METIS-312474, EWI-25555",
    author = "Wieringa, {Roelf J.} and Maia Daneva",
    note = "eemcs-eprint-25555",
    year = "2015",
    month = "4",
    doi = "10.1016/j.scico.2014.11.013",
    language = "Undefined",
    volume = "101",
    pages = "136--152",
    journal = "Science of computer programming",
    issn = "0167-6423",
    publisher = "Elsevier",

    }

    Six strategies for generalizing software engineering theories. / Wieringa, Roelf J.; Daneva, Maia.

    In: Science of computer programming, Vol. 101, 04.2015, p. 136-152.

    Research output: Contribution to journalArticleAcademicpeer-review

    TY - JOUR

    T1 - Six strategies for generalizing software engineering theories

    AU - Wieringa, Roelf J.

    AU - Daneva, Maia

    N1 - eemcs-eprint-25555

    PY - 2015/4

    Y1 - 2015/4

    N2 - General theories of software engineering must balance between providing full understanding of a single case and providing partial understanding of many cases. In this paper we argue that for theories to be useful in practice, they should give sufficient understanding of a sufficiently large class of cases, without having to be universal or complete. We provide six strategies for developing such theories of the middle range. In lab-to-lab strategies, theories of laboratory phenomena are developed and generalized to other laboratory phenomena. This is a characteristic strategy for basic science. In lab-to-field strategies, theories are developed of artifacts that first operate under idealized laboratory conditions, which are then scaled up until they can operate under uncontrolled field conditions. This is the characteristic strategy for the engineering sciences. In case-based strategies, we generalize about components of real-world cases, that are supposed to exhibit less variation than the cases as a whole. In sample-based strategies, we generalize about the aggregate behavior of samples of cases, which can exhibit patterns not visible at the case level. We discuss three examples of sample-based strategies. Throughout the paper, we use examples of theories and generalization strategies from software engineering to illustrate our analysis. The paper concludes with a discussion of related work and implications for empirical software engineering research.

    AB - General theories of software engineering must balance between providing full understanding of a single case and providing partial understanding of many cases. In this paper we argue that for theories to be useful in practice, they should give sufficient understanding of a sufficiently large class of cases, without having to be universal or complete. We provide six strategies for developing such theories of the middle range. In lab-to-lab strategies, theories of laboratory phenomena are developed and generalized to other laboratory phenomena. This is a characteristic strategy for basic science. In lab-to-field strategies, theories are developed of artifacts that first operate under idealized laboratory conditions, which are then scaled up until they can operate under uncontrolled field conditions. This is the characteristic strategy for the engineering sciences. In case-based strategies, we generalize about components of real-world cases, that are supposed to exhibit less variation than the cases as a whole. In sample-based strategies, we generalize about the aggregate behavior of samples of cases, which can exhibit patterns not visible at the case level. We discuss three examples of sample-based strategies. Throughout the paper, we use examples of theories and generalization strategies from software engineering to illustrate our analysis. The paper concludes with a discussion of related work and implications for empirical software engineering research.

    KW - IS-Design science methodology

    KW - SCS-Services

    KW - IR-93500

    KW - METIS-312474

    KW - EWI-25555

    U2 - 10.1016/j.scico.2014.11.013

    DO - 10.1016/j.scico.2014.11.013

    M3 - Article

    VL - 101

    SP - 136

    EP - 152

    JO - Science of computer programming

    JF - Science of computer programming

    SN - 0167-6423

    ER -