一句话：通过多轮工业实验构建扎根理论，揭示开发者如何在源代码中识别设计问题及其症状特征。
设计问题普遍存在时可能导致系统重构甚至停用。由于设计文档缺失、非正式或过时，开发者常依赖源代码来识别设计问题，需要分析多种代码元素上表现出的症状，任务复杂。已有研究多关注识别技术，却很少了解开发者实际如何识别设计问题。本文通过来自5家软件公司的专业人员开展多轮工业实验，并构建扎根理论，解释开发者在实践中识别设计问题的过程。理论揭示了开发者认为有用的症状特征，并发现开发者常组合不同类型症状来识别同一个设计问题。该知识为理解相关现象和开发更有效的识别技术提供了基础。
The prevalence of design problems may cause re-engineering or even discontinuation of the system. Due to missing, informal or outdated design documentation, developers often have to rely on the source code to identify design problems. Therefore, developers have to analyze different symptoms that manifest in several code elements, which may quickly turn into a complex task. Although researchers have been investigating techniques to help developers in identifying design problems, there is little knowledge on how developers actually proceed to identify design problems. In order to tackle this problem, we conducted a multi-trial industrial experiment with professionals from 5 software companies to build a grounded theory. The resulting theory offers explanations on how developers identify design problems in practice. For instance, it reveals the characteristics of symptoms that developers consider helpful. Moreover, developers often combine different types of symptoms to identify a single design problem. This knowledge serves as a basis to further understand the phenomena and advance towards more effective identification techniques.
@inproceedings{paperbot4526,
title = {Identifying design problems in the source code},
author = {Leonardo Sousa and Anderson Oliveira and Willian Oizumi and Simone Barbosa and Alessandro Garcia and Jaejoon Lee and Marcos Kalinowski and Rafael de Mello and Baldoino Fonseca and Roberto Oliveira and Carlos Lucena and Rodrigo Paes},
booktitle = {ICSE},
year = {2018},
doi = {10.1145/3180155.3180239}
}