Abstract
AbstractSafety-critical systems manufacturers have the duty of care, i.e., they should take correct steps while performing acts that could foreseeably harm others. Commonly, industry standards prescribe reasonable steps in their process requirements, which regulatory bodies trust. Manufacturers perform careful documentation of compliance with each requirement to show that they act under acceptable criteria. To facilitate this task, a safety-centered planning-time framework, called ACCEPT, has been proposed. Based on compliance-by-design, ACCEPT capabilities (i.e., processes and standards modeling, and automatic compliance checking) permit to design Compliance-aware Engineering Process Plans (CaEPP), which are able to show the planning-time allocation of standard demands, i.e., if the elements set down by the standard requirements are present at given points in the engineering process plan. In this paper, we perform a case study to understand if the ACCEPT produced models could support the planning of space software engineering processes. Space software is safety and mission-critical, and it is often the result of industrial cooperation. Such cooperation is coordinated through compliance with relevant standards. In the European context, ECSS-E-ST-40C is the de-facto standard for space software production. The planning of processes in compliance with project-specific ECSS-E-ST-40C applicable requirements is mandatory during contractual agreements. Our analysis is based on qualitative criteria targeting the effort dictated by task demands required to create a CaEPP for software development with ACCEPT. Initial observations show that the effort required to model compliance and processes artifacts is significant. However, such an effort pays off in the long term since models are, to some extend, reusable and flexible. The coverage level of the models is also analyzed based on design decisions. In our opinion, such a level is adequate since it responds to the information needs required by the ECSS-E-ST-40C framework.
Publisher
Springer Science and Business Media LLC
Subject
Law,Artificial Intelligence
Reference79 articles.
1. Ahmad E, Raza B, Feldt R, Nordebäck T (2010) Ecss standard compliant agile software development: an industrial case study. In: Proceedings of the 2010 national software engineering conference, pp 1–6
2. Armbrust O, Ocampo A, Soto M (2005) Tracing process model evolution: a semi-formal process modeling approach. In: ECMDA Traceability Workshop, pp 57–66
3. Bartolini C, Giurgiu A, Lenzini G, Robaldo L (2016) Towards legal compliance by correlating standards and laws with a semi-automated methodology. In: Benelux conference on artificial intelligence. Springer, pp 47–62
4. Baumgarten G, Rosinger M, Todino A, de Juan Marín R (2015) Spem 2.0 as process baseline meta-model for the development and optimization of complex embedded systems. In: 2015 IEEE international symposium on systems engineering (ISSE). IEEE, pp 155–162
5. Blackwelder B, Coleman K, Colunga-Santoyo S, Harrison JS, Wozniak D (2016) The volkswagen scandal
Cited by
9 articles.
订阅此论文施引文献
订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献