The Agile Safety Case
The Agile Safety Case
复制标题
敏捷安全案例
DOI：
10.1007/978-3-319-70265-0
复制
发表时间：
2018
期刊：
影响因子：
--
通讯作者：
T. Myklebust
中科院分区：
文献类型：
--
作者：
T. Stålhane;T. Myklebust
在过去的几年里，为了缩短上市时间、降低成本和提高质量，在开发安全关键型软件时，越来越多地使用敏捷开发方法。敏捷安全案例迫使申请人具体说明质量和安全过程以及技术安全方面，使认证过程能够与开发并行进行，并使认证机构能够在项目中的任何时候评估当前信息。从瀑布/ v模型过渡到敏捷模型会影响安全案例的几个部分。只有少数国际安全标准，如EN 5129（铁路）和ISO 26262（汽车），要求开发安全案例。在未来，我们期望更多的安全标准将包括一个安全案例的方法。铁路安全标准EN 50129确实包含了一个主题列表，这些主题甚至可以包含在其他领域的安全案例中。
During the last years, there has been an increasing use of agile development methods when developing safety-critical software in order to shorten the time to market, to reduce costs and to improve quality. The Agile Safety Case forces the applicant to be specific about the quality and safety process together with technical safety aspects, enabling the certification process to be done in parallel with development and enabling the certification body to evaluate the current information at any time in the project. Moving from a waterfall/V-model to an agile model affect several parts of the safety case. Only a few international safety standards, like e.g. EN 5129 (Railway) and ISO 26262 (Automotive), require a safety case to be developed. In the future, we expect that more safety standards will include a safety case approach. The railway safety standard EN 50129 does include a list of topics that can be included in safety cases even for other domains.