arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 1703.09602cs.SE
收藏

非功能性需求与持续集成构建之间的相互作用

On the Interplay between Non-Functional Requirements and Builds on Continuous Integration

Klérisson V. R. Paixão, Crícia Z. Felício, Fernanda M. Delfim, Marcelo de A. Maia

摘要:

持续集成(CI)意味着整个开发团队在软件项目的主线上一起工作。CI系统自动化软件的构建。有时开发人员签入代码,这会中断构建。一个损坏的构建本身可能不是问题,但它有可能扰乱同事,因此它会影响团队的性能。在这项研究中,我们调查了1,283个软件项目的非功能需求(NFR)和构建状态之间的相互作用。我们发现NFR相关构建状态之间存在显着差异。因此,可以提出一些工具来改进CI,重点是防止CI失败的新方法,特别是与效率和可用性相关的构建。此外,将中断的构建恢复到正常状态所需的时间表明,所有NFR都呈双峰分布,一天内的峰值较高,六周内的峰值较低。我们的研究结果表明,Ruby的可维护性和Java的功能性和可靠性的计划时间表将减少与中断构建相关的延迟。

英文摘要:

Continuous Integration (CI) implies that a whole developer team works together on the mainline of a software project. CI systems automate the builds of a software. Sometimes a developer checks in code, which breaks the build. A broken build might not be a problem by itself, but it has the potential to disrupt co-workers, hence it affects the performance of the team. In this study, we investigate the interplay between nonfunctional requirements (NFRs) and builds statuses from 1,283 software projects. We found significant differences among NFRs related-builds statuses. Thus, tools can be proposed to improve CI with focus on new ways to prevent failures into CI, specially for efficiency and usability related builds. Also, the time required to put a broken build back on track indicates a bimodal distribution along all NFRs, with higher peaks within a day and lower peaks in six weeks. Our results suggest that more planned schedule for maintainability for Ruby, and for functionality and reliability for Java would decrease delays related to broken builds.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑