arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2104.00725cs.SE
收藏

评估软件变更的暴露:DiPiDi方法

Assessing the Exposure of Software Changes: The DiPiDi Approach

Mehran Meidani, Maxime Lamothe, Shane McIntosh

摘要:

上下文:更改具有许多构建时配置设置的软件应用程序可能会引入意外的副作用。例如,旨在特定于平台的更改(例如,Windows)或产品配置(例如,社区版本)可能会影响其他平台或配置。此外,旨在应用于一组平台或配置的更改可能无意中被限制为子集。事实上,理解源代码变更的暴露是基于变更的开发方法中重要的风险缓解步骤。目的:在这个实验中,我们试图评估DiPiDi,我们的方法来评估暴露的源代码更改静态分析构建规范的原型实现。在评估源代码更改的暴露时,我们将评估重点放在开发人员的有效性和效率上。方法:我们将衡量开发人员在执行五项任务时的有效性和效率,在这些任务中,他们必须确定可交付成果和变更传播的条件。我们将参与者分为三组:没有明确的工具支持,由现有的影响分析工具支持,并支持DiPiDi。

英文摘要:

Context: Changing a software application with many build-time configuration settings may introduce unexpected side-effects. For example, a change intended to be specific to a platform (e.g., Windows) or product configuration (e.g., community editions) might impact other platforms or configurations. Moreover, a change intended to apply to a set of platforms or configurations may be unintentionally limited to a subset. Indeed, understanding the exposure of source code changes is an important risk mitigation step in change-based development approaches. Objective: In this experiment, we seek to evaluate DiPiDi, a prototype implementation of our approach to assess the exposure of source code changes by statically analyzing build specifications. We focus our evaluation on the effectiveness and efficiency of developers when assessing the exposure of source code changes. Method: We will measure the effectiveness and efficiency of developers when performing five tasks in which they must identify the deliverable(s) and conditions under which a change will propagate. We will assign participants into three groups: without explicit tool support, supported by existing impact analysis tools, and supported by DiPiDi.

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

↑