Organizations developing safety-critical software are increasingly seeking to create better practices by meshing agile and plan-driven development processes. Significant differences between the agile and the plan-driven processes make meshing difficult, and very little empirical evidence on using agile processes for safety-critical software development exists. There are four areas of concern, in particular, for meshing the development of safety-critical software concerning: documentation, requirements, life cycle and testing. We report on a case study of a pharmaceutical organization in which a Scrum process was implemented to support agile software development in a plan-driven safety-critical project. The purpose was to answer the following research question: For safety-critical software, what can a software team do to mesh agile and plan-driven processes effectively? The main contribution of the paper is an elaborated understanding of meshing in the four areas of concern and how the conditions for safety-critical software influence them. We discuss how meshing within the four areas of concern is a contribution to existing research.

中文翻译：

---

安全关键软件中的敏捷开发和计划驱动开发：案例研究

开发安全关键软件的组织越来越多地寻求通过将敏捷和计划驱动的开发流程相结合来创建更好的实践。敏捷过程和计划驱动过程之间的显着差异使得网格划分变得困难，并且几乎没有关于使用敏捷过程进行安全关键软件开发的经验证据。有四个关注领域，特别是对于安全关键软件开发的网格化，涉及：文档、需求、生命周期和测试。我们报告了一个制药组织的案例研究，其中实施了 Scrum 流程以支持计划驱动的安全关键项目中的敏捷软件开发。目的是回答以下研究问题：对于安全关键软件，软件团队可以做些什么来有效地融合敏捷和计划驱动的流程？本文的主要贡献是对四个关注领域中的网格划分以及安全关键软件的条件如何影响它们的详细理解。我们讨论了四个关注领域内的网格划分如何对现有研究做出贡献。