Difference between revisions of "Auto IWG WP5"

From Eclipsepedia

Jump to: navigation, search
(Qualification Roadmap (contact: Oscar Slotosch, Validas))
 
(45 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==== WP5: Eclipse Qualification Kit (ISO26262)====
+
==== WP5: Eclipse Qualification Process Support ====
This is work package 5 of the [[Automotive Industry Working Group]].
+
The content has been created from the work package 5 of the [[Automotive Industry Working Group]] in the years 2012 and 2013.
 +
In 2014 it is applied to build a qualification kit for an Eclipse-based build framework of a big automotive supplier.
  
* WP Lead: Virtual Vehicle (M. Driussi)
+
== Summary ==
  
== Intent ==
+
The main result of the working group is that it is possible to qualify software that has been developed with Eclipse.
 +
The choosen approach conforms to the DO-330, ISO 26262, IEC 61508, EN 50128 and is based on a qualification model
 +
that contains the relevant infomation to generate the required qualification documents.
  
Based on the requirements of ISO26262 for the development of safety-critical applications in vehicles, a qualification / classification of tools, which are used in the development process, will be required.
+
The following results have been achieved for Eclipse
WP5 has set itself the goal to work on this topic for Eclipse Plugins, which are used in this context.
+
* Qualification Process
Taking into consideration several standards (ISO, EN, DO, IEC) we want to elaborate a guideline for Eclipse Plugin developers / validators, which is conform to ISO26262 and DO-330. Furthermore we want to provide an Eclipse Tool Qualification Kit.
+
* Roadmap for Tool Support
 +
* Qualification Model (Internal Draft)
 +
* Tool Development Plan (Internal Draft)
 +
* Tool Qualification Plan (Internal Draft)
 +
* Overview Document "How-To-Qualify Eclipse-Based Tools" (Draft), see [https://wiki.eclipse.org/images/c/cb/HowToQualifyEclipseBasedTools.pdf HowToQualifyEclipseBasedTools.pdf]
 +
The other internal docuemtns have to be reviewed and validated before beeing published. This can be done during cooperation with interested tool providers.
  
== Meetings and Activities ==
+
== Qualification Process and Roadmap ==
  
Kick off Meeting 07.03.2012. The meeting protocol can be found here [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00151.html]
+
The goal is not to qualify Eclipse completly but to enable tool developers using Eclispe as a plattform to develop qualifyable plugins.
  
Webex session every two weeks on Wednesday 13 to 15 pm.
+
We have identified the DO-330 as first, domain independant tool qualification standard that satisfies the requirements of
Next Webex Meeting 18.04.2012 13p.m. (Outlook appointment)
+
the main safety standards and hence we use the DO-330 as baseline for tool qualification.
  
== Next Steps ==
+
We have specified a roadmap to provide an infrastructure that support the develment of qualifyable Eclipse plugins by
 +
gathering all relevant qualification information (from requirements to tests) in the tool qualification model.
 +
See http://wiki.eclipse.org/images/2/2c/QualificationRoadmapOverview.pdf
 +
An overview of the concept has been published at the openCert 2012 conference, see
 +
http://wiki.eclipse.org/images/7/75/ModelBasedToolQuali.pdf and http://wiki.eclipse.org/images/9/95/ModelBasedToolQualificationPresentation.pdf
  
* Discuss the Roadmap internally / expand it / change it. The Roadmap can be found here [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00149.html]
+
There is a qualification model and a development process using this model that is compliant to DO-330 (all TQLs).
* Build the working team to contribute to the roadmap.
+
Furthermore there is a project plan to implement Eclipse-based tool support to ease the development of qualifiable plugins.
* All interested parties are invited to participate. Commitment on next Telco 21.03.2012, 13:00 to 15:00 pm in order to create a list of contact persons and companies.
+
However before starting to implement this qualification support, in an Eclipse project that extends the Eclipse plugin
 +
mechanism there has to be the market demand and the financing for this project.  
  
== Qualification Roadmap (contact: Oscar Slotosch, Validas) ==
+
Our current experience is that it suffices to fill the qualification model manually and to build a qualification kit
 +
based on this manual information. This is compliant to all standards, but not for the highest TQLs (1,2,3) of the DO-330.
 +
The effort for creating a tool qualification kit depends on the available features and test cases.
 +
Typically this is an effort for some weeks or months and requires cooperation from the provider of the tool and our qualification experts.
 +
While the Eclipse infrastructure is not in place we can use the Validas tool qualification tools to qualify Eclipse-based tools.
 +
see http://www.validas.de/toolqualification.html
  
See http://wiki.eclipse.org/images/1/1e/EclipseQualificationProcess.pdf for an overview (as presented on 4th april by Validas)
+
With this step by step approach there is no need start with development of big automated infrastructure, but it enables us to qualify
 +
Eclipse tools now. See the presentation in Ludwigsburg https://wiki.eclipse.org/images/6/65/EclipseRoadmap2103.pdf for more details.
  
*WP5.1 Definition of Goals & Requirements
+
== History ==
*WP5.2 Elaborate Proposal
+
The qualification support has been developer from the Eclipse automotive working group 5 in accordance with the
*WP5.3 Demonstrate Proposal
+
Polarsys working group.
*WP5.4 Implement Proposal (extend Eclipse Pluging Framework within an Eclipse Project)
+
*WP5.5 Qualify any plugin that requires qualification
+
  
In WP5 we decided to use the DO-330 as basis for qualification of Eclipse-based tools, since
+
* WP Lead: Virtual Vehicle (M. Driussi)
it fits to the ISO 26262 but also to other standards like the DO-178C,..
+
* Roadmap Lead: Validas AG (O. Slotosch)
We propose to extend the Eclipse plugin mechanism to additional data that contains
+
all required information for qualification of the plugin.
+
By building a formal (EMF) model for this data we can automate many steps during
+
the development and qualification process like: Determination of the tool confidence level,
+
determination of the qualification state, verification of syntactical consistency and completeness
+
and generation of requried documents from the requirements specification until the test report with
+
MC/DC coverage of the code.
+
Furthermore we create generic documents that ensure the DO-330 compliance of the process
+
Like "How-To Qualify Eclipse-Based Tools", "Tool Development Plan", "Tool Verification Plan",...
+
+
----
+
  
We (Validas, virtual vehicle) are currently working on the topic. Other will be requested to provide reviews and feedback.
+
Meetings and Activities:
  
The following results have been achieved to elaborate the proposal
+
Kick off Meeting 07.03.2012. The meeting protocol can be found here [http://wiki.eclipse.org/images/e/ef/Eclipse_Automotive_IWG_WP5_Telco_07_03_2012_Minutes_of_Meeting.pdf]
  
*Checklist for DO-330 compliance (cannot be published due to RTCA restrictions)
+
Webex session every two weeks on Wednesday 13 to 15 pm.  
*Example requirements document (will be checked for DO-330 compliance), see http://wiki.eclipse.org/images/f/fc/TCAToolRequirements.zip
+
Next Webex Meeting 22.08.2012 13p.m. (invitation is coming via email)
*EMF-Model do3300.ecore to capture requirements, see http://wiki.eclipse.org/images/8/85/Do330.zip
+
 
+
----
+
  
The current state of the roadmap is in a presentation that is extended stepwise until it covers all aspects of the DO-330. We report the new supported steps within our telcos.
+
A List of past Minutes of Meeting
The following steps have been achieved:
+
* 21.03.2012 [http://wiki.eclipse.org/images/b/bf/Eclipse_Automotive_IWG_Telco_21032012_Mintues_of_Meeting_WP5.pdf]
*First Steps (21th of march 2012) see http://wiki.eclipse.org/images/8/8d/EclipseRoadmapFirst.pdf
+
* 04.04.2012 [http://wiki.eclipse.org/images/e/ed/Eclipse_Automotive_IWG_Telco_04042012_Minutes_of_Meeting.pdf]
*Second steps (4th april 2012) http://wiki.eclipse.org/images/6/63/EclipseRoadmapSecond.pdf
+
* 18.04.2012 [http://wiki.eclipse.org/images/3/38/Eclipse_Automotive_IWG_Telco_18042012_Minutes_of_Meeting.pdf]
*Third Steps (18th april 2012) http://wiki.eclipse.org/images/0/02/EclipseRoadmapThird.pdf  
+
* 02.05.2012 [http://wiki.eclipse.org/images/7/7f/Eclipse_Automotive_IWG_Telco_02052012_Minutes_of_Meeting.pdf]
Since the presentations are extended, it suffices to read the latest.
+
* 16.05.2012 [http://wiki.eclipse.org/images/4/42/Eclipse_Automotive_IWG_Telco_16052012_Minutes_of_Meeting.pdf]
 +
* 30.05.2012 [http://wiki.eclipse.org/images/d/db/Eclipse_Automotive_IWG_Telco_30052012_Minutes_of_Meeting.pdf]
 +
* 13.06.2012 [http://wiki.eclipse.org/images/6/68/Eclipse_Automotive_IWG_Telco_13062012_Minutes_of_Meeting.pdf]
 +
* 27.06.2012 [http://wiki.eclipse.org/images/b/ba/Eclipse_Automotive_IWG_Telco_27062012_Minutes_of_Meeting.pdf]
 +
* 08.08.2012 [http://wiki.eclipse.org/images/4/40/Eclipse_Automotive_IWG_Telco_08082012.pdf]
 +
* Crystal-UseCase description [http://wiki.eclipse.org/images/0/0c/Crystal_UseCase_Proposal_AUTO_IWG_WP5_v03.pdf]
 +
* 28.10.2013 (Ludwigsburg), see https://wiki.eclipse.org/images/6/65/EclipseRoadmap2103.pdf
  
 
<br>
 
<br>

Latest revision as of 18:13, 5 February 2014

Contents

[edit] WP5: Eclipse Qualification Process Support

The content has been created from the work package 5 of the Automotive Industry Working Group in the years 2012 and 2013. In 2014 it is applied to build a qualification kit for an Eclipse-based build framework of a big automotive supplier.

[edit] Summary

The main result of the working group is that it is possible to qualify software that has been developed with Eclipse. The choosen approach conforms to the DO-330, ISO 26262, IEC 61508, EN 50128 and is based on a qualification model that contains the relevant infomation to generate the required qualification documents.

The following results have been achieved for Eclipse

* Qualification Process
* Roadmap for Tool Support
* Qualification Model (Internal Draft)
* Tool Development Plan (Internal Draft)
* Tool Qualification Plan (Internal Draft)
* Overview Document "How-To-Qualify Eclipse-Based Tools" (Draft), see HowToQualifyEclipseBasedTools.pdf

The other internal docuemtns have to be reviewed and validated before beeing published. This can be done during cooperation with interested tool providers.

[edit] Qualification Process and Roadmap

The goal is not to qualify Eclipse completly but to enable tool developers using Eclispe as a plattform to develop qualifyable plugins.

We have identified the DO-330 as first, domain independant tool qualification standard that satisfies the requirements of the main safety standards and hence we use the DO-330 as baseline for tool qualification.

We have specified a roadmap to provide an infrastructure that support the develment of qualifyable Eclipse plugins by gathering all relevant qualification information (from requirements to tests) in the tool qualification model. See http://wiki.eclipse.org/images/2/2c/QualificationRoadmapOverview.pdf An overview of the concept has been published at the openCert 2012 conference, see http://wiki.eclipse.org/images/7/75/ModelBasedToolQuali.pdf and http://wiki.eclipse.org/images/9/95/ModelBasedToolQualificationPresentation.pdf

There is a qualification model and a development process using this model that is compliant to DO-330 (all TQLs). Furthermore there is a project plan to implement Eclipse-based tool support to ease the development of qualifiable plugins. However before starting to implement this qualification support, in an Eclipse project that extends the Eclipse plugin mechanism there has to be the market demand and the financing for this project.

Our current experience is that it suffices to fill the qualification model manually and to build a qualification kit based on this manual information. This is compliant to all standards, but not for the highest TQLs (1,2,3) of the DO-330. The effort for creating a tool qualification kit depends on the available features and test cases. Typically this is an effort for some weeks or months and requires cooperation from the provider of the tool and our qualification experts. While the Eclipse infrastructure is not in place we can use the Validas tool qualification tools to qualify Eclipse-based tools. see http://www.validas.de/toolqualification.html

With this step by step approach there is no need start with development of big automated infrastructure, but it enables us to qualify Eclipse tools now. See the presentation in Ludwigsburg https://wiki.eclipse.org/images/6/65/EclipseRoadmap2103.pdf for more details.

[edit] History

The qualification support has been developer from the Eclipse automotive working group 5 in accordance with the Polarsys working group.

  • WP Lead: Virtual Vehicle (M. Driussi)
  • Roadmap Lead: Validas AG (O. Slotosch)

Meetings and Activities:

Kick off Meeting 07.03.2012. The meeting protocol can be found here [1]

Webex session every two weeks on Wednesday 13 to 15 pm. Next Webex Meeting 22.08.2012 13p.m. (invitation is coming via email)

A List of past Minutes of Meeting