1 / 24

Akhela nSC WP200 – Status of the activity

Akhela nSC WP200 – Status of the activity Massimiliano Turco (Akhela - massimiliano.turco@akhela.com ) SafeCer P7 September 25-27, 2013 Riga. Presentation outline. WP200 objectives and deliverables WP210 overview WP220 overview WP230 overview D211.1_ D212.1: status

mio
Download Presentation

Akhela nSC WP200 – Status of the activity

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Akhela nSC WP200 – Status of the activity Massimiliano Turco (Akhela - massimiliano.turco@akhela.com ) SafeCer P7 September 25-27, 2013 Riga

  2. Presentation outline • WP200 objectives and deliverables • WP210 overview • WP220 overview • WP230 overview • D211.1_ D212.1: status • D221.1_ D222.1: status • WP200 deliverables and corrective actions • Forthcoming activities and potential risks

  3. WP200 objectives The WP200 objective is to transform the pSafeCer prototype framework of tools in a project-ready tool framework with a smart integrated tool chain, reusable components and a framework for the design, implementation, testing, validation of safety certifiable embedded systems; in addition, the CAR will provide support and automation for configuration management activities.

  4. WP210

  5. D211.1 PrototypeanalysisdocumentD212.1 PrototypeenhancementspecificationDocument • These deliverables are the output of the work package nSafeCer WP210 on “Integration of pSafeCer results”. • The main objective of WP210 is to integrate the results of pSafeCer by analyzing them and specifying which enhancements should be developed by nSafeCer.

  6. It provides an analysis of the current status of the pSafeCer tool framework highlighting what is missing and what should be extended/integrated/implemented in nSafeCer. • It highlights the drawbacks of the framework to support the certification process proposed in pSafeCer and the demonstrators that will be carried out in nSafeCer. • One of the main concerns is the status of integration of the CTF and other tools with the CAR, which is seen as pivotal for the certification process. • Other concerns are related to the missing support for the preparation of certification material and safety argumentation. Moreover, each tool of the framework needs some extensions mostly related to the SafeCer process and component models, contract verification, and dependability and safety analysis. • It includes a high-level specification of what will be implemented in nSafeCer.

  7. WP220

  8. D221.1_ D222.1 – Requirements, Architecture and Design Document for Tool Framework • This deliverable includes information about the enhancement design for the Tool Framework. • CTF and CAR integration design analysis • GPM integration design analysis • Improvement of pSafeCer tools and new tools • Mapping of Use Cases and tools • Facilities

  9. CTF and CAR integration design analysis [1] The integration of the CAR and CTF is interpreted as a mutual collaboration to implement the fundamentals tasks requested by the continuous certification objective: following the artefact evolution, regenerating the obsolete artefacts to keep the system certifiable and, maintaining artefact traceability information.

  10. CTF and CAR integration design analysis [2] 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.

  11. GPM integration design analysis [1] The interaction with the CTF is centered 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. SafeCer partners will be encouraged to integrated their own (or external) tools in the CTF, so as to develop an integrated tool chain covering most activities identified by the generic certification process. The interaction with the CAR consist in a mechanism to manage the certification artefacts produced by the activities described by the generic process and its domain-specific instantiations. The core idea is to deduce an artefact-centric process model and use it to configure the CAR.

  12. GPM integration design analysis [2] Integration between WP100 (GPM) and WP200 (CAR and CTF)

  13. GPM integration design analysis [3] Integration between WP100 (GPM) and WP200 (CAR and CTF) • 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

  14. 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.

  15. New Specific tools [1] • One of the goals of sub-WP220 is to develop new specific tools or their integration in the existent pSafecer Tool Framework. The tools will be categorized in the following categories providing languages and facilities that permit the interoperation of the following tool during the safety certification process: • Requirement Tool • Analysis and V&V Tool • Structural Design Tool • Functional Design Tool • IDE • Testing Tool • Furthermore, tools already presented in the Platform could be updated and or modified. Work-in-progress.

  16. New Specific tools [2] At the moment of writing the discussion is still open regarding new tools. UPM proposed the new tool PeabraiN PeabraiN is composed of a collection of PIPE tool-compliant modules for performance estimation and resource optimization based on bounds computation for Stochastic Petri Nets (SPNs).

  17. Mapping of Use Cases and tools [1] In the WP220 activity, an investigation has been performed regarding the planned Use Cases and the related tools indicated by the UC providers. This has been done, under the point of view of the CTF, for: better understanding the specific Use Case better knowing and identifying the related tools better understanding the sequence of tools and, most important, how this impacts on the CTF and CAR, respect the integration and then automatization of a specific certification process

  18. Mapping of Use Cases and tools [2]

  19. Facilities nSafeCer can add new wizards, templates and facilities that can be useful in the artifact lifecycle. MS Word plug-in proposed by Resiltech MS Word plug-in allows to import a list of requirements thanks to a document plug-in with an easy user interface. The interface should allow the user to highlight easily part of the text that is a requirements and the tool should populate a requirement DB from that. Output could be, for instance, in a format easily integrated into the CAR or in some format compatible with SQL DB.

  20. WP230

  21. WP200 deliverables

  22. WP200 Corrective Actions

  23. Forthcoming activities and potential risks • Software phase following the design of new addition and enhancement of the platform, as described above. Consequently, the D221.1_D222.1 should be labeled as a “living document” to be updated and aligned accordingly to the software developments. • 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.

More Related