ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Safety Certification of Software-intensive Systems with Reusable Components Akhela nSC WP100 - WP200 – Working Session Massimiliano Turco (Akhela - ) SafeCer P7 September 25-27, 2013 Riga

27 th of September 2013, Riga Page 2 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number WP100 and WP200 activity GPM (WP100, MDH) and CTF \CAR (WP200, Akhela & AdaCore) integration. The main scope of this activity is aimed to integrate the GPM with the Platform (CAR\CTF), in order to perform a specific certification process. In this perspective, it’s key to determinate an “input” able to initialize the system (CAR/CTF and tools, sequence of tools and, consequently, artefacts to track). This input has been identified by MDH in a xml file, modeled in SPEM2.0/EPF. Details to be finalized.

27 th of September 2013, Riga Page 3 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number CTF and CAR: Quick overview The CAR has to work out and store the reference to the CAR imported artifacts (location) and their traceability links and dependency links, calculated on the basis of the rules defined in the CAR input model, containing the most general relationship between the artifact classes involved in the certification process. As well, the CAR has to performs the impact analysis, which checks the artifact updated status and consequently detects the artifacts to be regenerated in order to make the artifact status consistent and the system still certifiable. The CTF has to execute the tool chain, generating new artifacts or the old ones which need to be update.

27 th of September 2013, Riga Page 4 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number GPM integration design analysis Interaction with the CTF. It is focused on identifying the “families” of tools required by a certification process such as requirement management tools, modelling tools, IDE, compilers, static analysis tools and so on. Interaction with the CAR. It is a mechanism to manage the certification artifacts produced by the activities described in a domain-specific processes, obtained by selecting Generic Process elements and domain-specific variants. The core idea is to deduce an artifact-centric process model and use it to configure the CAR. SafeCer proposes a Generic Process Model (GPM) aimed to integrate certification and development of component-based systems. A domain-specific process (accordingly to GPM) is an input (e.g. as an xml file) to the component model and tool framework, based on the SafeCer requirements and needs of the SafeCer demonstrators.

27 th of September 2013, Riga Page 5 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number

27 th of September 2013, Riga Page 6 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number WP120 Process: the key research element of this work package will be the development of the co-certification process and associated techniques for certifying systems developed using a product-line engineering approach. WP220: CTF, CAR and GPM interaction GPM integration design analysis Integration between WP100 (GPM) and WP200 (CAR and CTF)

27 th of September 2013, Riga Page 7 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Aimed to integrate the GPM with the Platform, in order to perform a specific certification process it’s key to determinate an xml as input to initialize the system (CAR/CTF and tools, sequence of tools and, consequently, artefacts to track) Definition of interface with CAR/CTF possibly by September 2013 Which process elements should the process models contain? (e.g. Tools for CTF and artefacts for CAR) Provision of the XML related to the processes, modeled in SPEM2.0/EPF GPM integration design analysis [3] Integration between WP100 (GPM) and WP200 (CAR and CTF)

27 th of September 2013, Riga Page 8 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number GPM integration design analysis [4] Portion of XML related to the ISO26262 process, modeled in SPEM2.0/EPF (MDH) CTF is “in charge” of the tools, so it could extract the tools info from the input process xml file. We have to discuss the details about the xml structure, involving also AdaCore and their CAR module.

27 th of September 2013, Riga Page 9 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Forthcoming activities and potential risks Release of a intermediate software prototype able to perform a possible simplified certification process (GPM/CTF/CAR), possibly covering one of the planned UC (or part of it). Risk: put in place a fully working integration with CTF/CAR & GPM.