Some Lessons Learned in Conducting Software Engineering Surveys in China

被引:0
|
作者
Ji, Junzhong [1 ]
Li, Jingyue
Conradi, Reidar
Liu, Chunnian [1 ]
Ma, Jianqiang
Chen, Weibing [1 ]
机构
[1] Beijing Univ Technol, Beijing Municipal Key Lab Multimedia & Intelligen, Beijing 100022, Peoples R China
关键词
Empirical software engineering methods; survey; lessons learned; data collection; questionnaire validation;
D O I
暂无
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Component-Based Software Engineering (CBSE) with Open Source Software and Commercial-Off-the-Shelf (COTS) components, Open Source Software (OSS) based development, and Software Outsourcing (SO) are becoming increasingly important for the Chinese software industry. It is therefore necessary to establish pragmatic and possibly nation-specific guidelines for Chinese software companies regarding the use of CBSE, OSS, and SO. Such guidelines should be based on insights from actual practice, which are in our case, obtained through surveys. A European state-of-the-practice survey on COTS- and OSS-oriented CBSE was conducted in Germany, Italy, and Norway in 2004-2005. We repeated similar surveys in China, with an extended survey on OSS and SO. We encountered many difficulties in conducting the surveys, but in most cases managed to find working solutions. We report on the lessons learned while conducting these surveys. In particular, we address issues relating to sampling, contacting respondents, data collection, and data validation. The main lessons are: 1) it was necessary to cooperate with a third-party organization with close relations to Chinese software companies; 2) it was necessary to assign researchers to this third-party organization to facilitate data collection and to control the quality of the data collected; and 3) an email survey, after an initial telephone call to establish contact, was the best method for getting questionnaires completed by Chinese respondents.
引用
收藏
页码:168 / +
页数:4
相关论文
共 50 条
  • [1] Lessons Learned from Conducting Industry Surveys in Software Testing
    Kanij, Tanjila
    Merkel, Robert
    Grundy, John
    [J]. 2013 1ST INTERNATIONAL WORKSHOP ON CONDUCTING EMPIRICAL STUDIES IN INDUSTRY (CESI), 2013, : 63 - 66
  • [2] A software engineering lessons learned repository
    Harrison, W
    [J]. 27TH ANNUAL NASA GODDARD/IEEE SOFTWARE ENGINEERING WORKSHOP - PROCEEDINGS, 2003, : 139 - 143
  • [3] Conducting on-line surveys in software engineering
    Punter, T
    Ciolkowski, M
    Freimut, B
    John, I
    [J]. 2003 INTERNATIONAL SYMPOSIUM ON EMPIRICAL SOFTWARE ENGINEERING, PROCEEDINGS, 2003, : 80 - 88
  • [4] Software engineering masters programs - Lessons learned
    Jovanovic, V
    MacNeil, P
    Matlen, D
    Modesitt, K
    Shoemaker, D
    [J]. 15TH CONFERENCE ON SOFTWARE ENGINEERING EDUCATION AND TRAINING, PROCEEDINGS, 2002, : 253 - 255
  • [5] Software Engineering Team Project lessons learned
    Hnatkowska, Bogumila
    [J]. E-INFORMATICA SOFTWARE ENGINEERING JOURNAL, 2013, 7 (01) : 77 - 85
  • [6] Software requirements negotiation: Some lessons learned
    Boehm, B
    Egyed, A
    [J]. PROCEEDINGS OF THE 1998 INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, 1998, : 503 - 506
  • [7] Lessons Learned Managing Distributed Software Engineering Courses
    Holmes, Reid
    Craig, Michelle
    Reid, Karen
    Stroulia, Eleni
    [J]. 36TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING (ICSE COMPANION 2014), 2014, : 321 - 324
  • [8] Teaching global software engineering: experiences and lessons learned
    Niazi, Mahmood
    [J]. IET SOFTWARE, 2015, 9 (04) : 95 - 102
  • [9] LESSONS LEARNED TEACHING ADA IN THE CONTEXT OF SOFTWARE ENGINEERING
    TOMAYKO, JE
    [J]. JOURNAL OF SYSTEMS AND SOFTWARE, 1989, 10 (04) : 281 - 283
  • [10] Applying empirical software engineering to software architecture: challenges and lessons learned
    Davide Falessi
    Muhammad Ali Babar
    Giovanni Cantone
    Philippe Kruchten
    [J]. Empirical Software Engineering, 2010, 15 : 250 - 276