Member Checking in Software Engineering Research: Lessons Learned from an Industrial Case Study

被引:1
|
作者
Santos, Ronnie E. S. [1 ]
Magalhaes, Cleyton V. C. [1 ]
da Silva, Fabio Q. B. [1 ]
机构
[1] Univ Fed Pernambuco, Ctr Informat, Recife, PE, Brazil
来源
11TH ACM/IEEE INTERNATIONAL SYMPOSIUM ON EMPIRICAL SOFTWARE ENGINEERING AND MEASUREMENT (ESEM 2017) | 2017年
关键词
Qualitative Research; Case Study; Member Checking; Software Engineering; TRUSTWORTHINESS;
D O I
10.1109/ESEM.2017.29
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Context. Member checking can be defined as a research phase performed during a qualitative research in which the researcher compares her interpretations and understanding obtained from the data analysis with the view-points of participants to increase accuracy and consistency of results. This is an important step for any qualitative research. However, considering a sample of 66 case studies developed and published in the context of software engineering, only 10 studies briefly described the use of this technique. Method. In this article, we present a set of lessons learned obtained from planning and performing member checking to validate the results of an industrial case study performed in a large software company. Results. Member checking was effective to validate the findings obtained from the qualitative case study and was also useful to reveal important information not observed in the data analysis process. It has also shown to be effective to observe divergences among different groups of participants. Conclusion. We described how the member checking can be performed, and discussed seven lessons learned in this process. We expect that our experience can be useful to software engineering researchers while performing this research phase in case studies.
引用
收藏
页码:187 / 192
页数:6
相关论文
共 50 条
  • [1] AN INDUSTRIAL SOFTWARE ENGINEERING RETRAINING COURSE - DEVELOPMENT CONSIDERATIONS AND LESSONS LEARNED
    BENDAVID, A
    BENPORATH, MI
    LOEB, JZ
    RICH, M
    IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 1984, 10 (06) : 748 - 755
  • [2] Lessons Learned in a Decade of Research Software Engineering GPU Applications
    van Werkhoven, Ben
    Palenstijn, Willem Jan
    Sclocco, Alessio
    COMPUTATIONAL SCIENCE - ICCS 2020, PT VII, 2020, 12143 : 399 - 412
  • [3] LESSONS LEARNED IN AN INDUSTRIAL SOFTWARE LAB
    ENDRES, A
    IEEE SOFTWARE, 1993, 10 (05) : 58 - 61
  • [4] A software engineering lessons learned repository
    Harrison, W
    27TH ANNUAL NASA GODDARD/IEEE SOFTWARE ENGINEERING WORKSHOP - PROCEEDINGS, 2003, : 139 - 143
  • [5] Software testing with code-based test generators: data and lessons learned from a case study with an industrial software component
    Pietro Braione
    Giovanni Denaro
    Andrea Mattavelli
    Mattia Vivanti
    Ali Muhammad
    Software Quality Journal, 2014, 22 : 311 - 333
  • [6] Software testing with code-based test generators: data and lessons learned from a case study with an industrial software component
    Braione, Pietro
    Denaro, Giovanni
    Mattavelli, Andrea
    Vivanti, Mattia
    Muhammad, Ali
    SOFTWARE QUALITY JOURNAL, 2014, 22 (02) : 311 - 333
  • [7] INDUSTRIAL SOFTWARE ENGINEERING RETRAINING COURSE: DEVELOPMENT CONSIDERATIONS AND LESSONS LEARNED.
    Ben-David, Amram
    Ben-Porath, Moshe I.
    Loeb
    Rich, Michael
    IEEE Transactions on Software Engineering, 1984, SE-10 (06) : 748 - 755
  • [8] Dynamic Software Randomisation: Lessons Learned From an Aerospace Case Study
    Cros, Fabrice
    Kosmidis, Leonidas
    Wartel, Franck
    Morales, David
    Abella, Jaume
    Broster, Ian
    Cazorla, Francisco J.
    PROCEEDINGS OF THE 2017 DESIGN, AUTOMATION & TEST IN EUROPE CONFERENCE & EXHIBITION (DATE), 2017, : 103 - 108
  • [9] Software model checking in practice: An industrial case study
    Chandra, S
    Godefroid, P
    Palm, C
    ICSE 2002: PROCEEDINGS OF THE 24TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, 2002, : 431 - 441
  • [10] Lessons from industrial adoption of software engineering practices
    Grady, RB
    NINTH CONFERENCE ON SOFTWARE ENGINEERING EDUCATION, PROCEEDINGS, 1996, : 216 - 216