Jump to: navigation, search

Difference between revisions of "Auto IWG WP5"

(Qualification Roadmap)
 
(28 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
==== WP5: Eclipse Qualification Process Support ====
 
==== 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 ==
* Roadmap Lead: Validas AG (O. Slotosch)
+
  
== 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://wiki.eclipse.org/images/e/ef/Eclipse_Automotive_IWG_WP5_Telco_07_03_2012_Minutes_of_Meeting.pdf]
+
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 30.05.2012 13p.m. (Outlook appointment) [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00212.html]
+
the main safety standards and hence we use the DO-330 as baseline for tool qualification.
  
A List of past Minutes of Meeting
+
We have specified a roadmap to provide an infrastructure that support the develment of qualifyable Eclipse plugins by
* 21.03.2012 [http://wiki.eclipse.org/images/b/bf/Eclipse_Automotive_IWG_Telco_21032012_Mintues_of_Meeting_WP5.pdf]
+
gathering all relevant qualification information (from requirements to tests) in the tool qualification model.
* 04.04.2012 [http://wiki.eclipse.org/images/e/ed/Eclipse_Automotive_IWG_Telco_04042012_Minutes_of_Meeting.pdf]
+
See http://wiki.eclipse.org/images/2/2c/QualificationRoadmapOverview.pdf
* 18.04.2012 [http://wiki.eclipse.org/images/3/38/Eclipse_Automotive_IWG_Telco_18042012_Minutes_of_Meeting.pdf]
+
An overview of the concept has been published at the openCert 2012 conference, see
* 02.05.2012 [http://wiki.eclipse.org/images/7/7f/Eclipse_Automotive_IWG_Telco_02052012_Minutes_of_Meeting.pdf]
+
http://wiki.eclipse.org/images/7/75/ModelBasedToolQuali.pdf and http://wiki.eclipse.org/images/9/95/ModelBasedToolQualificationPresentation.pdf
  
== Next Steps ==
+
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.
  
* Complete the roadmap to cover all aspects of DO-330. The Roadmap can be found here [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00149.html]
+
Our current experience is that it suffices to fill the qualification model manually and to build a qualification kit
* Select a Plugin for classification and Qualification according to the roadmap to demonstrate the proposal
+
based on this manual information. This is compliant to all standards, but not for the highest TQLs (1,2,3) of the DO-330.
* Define an Eclipse Project to extend the plugin mechanism to contain qualification data
+
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
  
All interested parties are invited to participate. Commitment on WP5 telco or webex meeting.
+
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.
  
== Qualification Roadmap ==
+
== History ==
 +
The qualification support has been developer from the Eclipse automotive working group 5 in accordance with the
 +
Polarsys working group.
  
See http://wiki.eclipse.org/images/2/2c/QualificationRoadmapOverview.pdf for an overview (as presented on on 23rd of may 2012 on the IWG Meeting in Toulouse)
+
* WP Lead: Virtual Vehicle (M. Driussi)
On the Eclipse Day in Toulouse (24th of May 2012), http://www.eclipsedaytoulouse.com/en/ Oscar Slotosch presented an overview on
+
* Roadmap Lead: Validas AG (O. Slotosch)
the roadmap and the curent status.
+
  
*WP5.1 Definition of Goals & Requirements
+
Meetings and Activities:
*WP5.2 Elaborate Proposal
+
*WP5.3 Demonstrate Proposal
+
*WP5.4 Implement Proposal (extend Eclipse Pluging Framework within an Eclipse Project)
+
*WP5.5 Qualify any plugin that requires qualification
+
  
In WP5.1 we decided to use the DO-330 as basis for qualification of Eclipse-based tools, since
+
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]
it fits to the ISO 26262 but also to other standards like the DO-178C,..  
+
We are checking especially if the ISO 26262 requires less than DO-330.
+
  
We propose to extend the Eclipse plugin mechanism to additional data that contains
+
Webex session every two weeks on Wednesday 13 to 15 pm.  
all required information for qualification of the plugin.
+
Next Webex Meeting 22.08.2012 13p.m. (invitation is coming via email)
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",...
+
+
  
The concept has been elaborated within several steps and covers now all aspects of the DO-330.
+
A List of past Minutes of Meeting
Since the presentations are extended, it suffices to read the latest.
+
* 21.03.2012 [http://wiki.eclipse.org/images/b/bf/Eclipse_Automotive_IWG_Telco_21032012_Mintues_of_Meeting_WP5.pdf]
 
+
* 04.04.2012 [http://wiki.eclipse.org/images/e/ed/Eclipse_Automotive_IWG_Telco_04042012_Minutes_of_Meeting.pdf]
*First Steps (21th of march 2012) http://wiki.eclipse.org/images/8/8d/EclipseRoadmapFirst.pdf
+
* 18.04.2012 [http://wiki.eclipse.org/images/3/38/Eclipse_Automotive_IWG_Telco_18042012_Minutes_of_Meeting.pdf]
*Second steps (4th april 2012) http://wiki.eclipse.org/images/6/63/EclipseRoadmapSecond.pdf
+
* 02.05.2012 [http://wiki.eclipse.org/images/7/7f/Eclipse_Automotive_IWG_Telco_02052012_Minutes_of_Meeting.pdf]
*Third Steps (18th april 2012) http://wiki.eclipse.org/images/0/02/EclipseRoadmapThird.pdf  
+
* 16.05.2012 [http://wiki.eclipse.org/images/4/42/Eclipse_Automotive_IWG_Telco_16052012_Minutes_of_Meeting.pdf]
*Fourth Steps (2nd may 2012) http://wiki.eclipse.org/images/7/73/EclipseRoadmapFourth.pdf
+
* 30.05.2012 [http://wiki.eclipse.org/images/d/db/Eclipse_Automotive_IWG_Telco_30052012_Minutes_of_Meeting.pdf]
*Fifth Steps (16th may 2012) http://wiki.eclipse.org/images/0/00/EclipseRoadmapFifth.pdf
+
* 13.06.2012 [http://wiki.eclipse.org/images/6/68/Eclipse_Automotive_IWG_Telco_13062012_Minutes_of_Meeting.pdf]
*Sixth/Final Steps (30th may 2012) http://wiki.eclipse.org/images/1/1d/EclipseRoadmapSixth.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]
The conecpt is described with in the following three documents:
+
* Crystal-UseCase description [http://wiki.eclipse.org/images/0/0c/Crystal_UseCase_Proposal_AUTO_IWG_WP5_v03.pdf]
* HowTo Qualify Exclipse-based Tools
+
* 28.10.2013 (Ludwigsburg), see https://wiki.eclipse.org/images/6/65/EclipseRoadmap2103.pdf
* Tool Development Plan for Every Qualifiable Eclipse Plugin
+
* Tool Verification Plan for Every Qualifiable Eclipse Plugin
+
* The DO-330 model (EMF)
+
 
+
Is ready now with a complete coverage of DO-330. It can be used for demonstration and will be improved.
+
It is waiting for an offical DO-330 compliance review before it shall be used in official projects.
+
For ISO 26262 either a separate compliance tracing and review would be necessary, or an agreement
+
on the mapping of TCL and ASIL to TQLs.
+
 
+
<br>
+
 
+
----
+
 
+
We (Validas, BMW-CarIT) are currently working on the demonstration.  
+
Others can yoin if they are interested in contributing and willing to spend and document some effort.  
+
 
+
The demonstration shall develop a transition criteria checker tool for the DO-330 to determine
+
the qualification state of a tool based on the DO-330 qualification model of the concept.
+
The plan with functions, milestones etc. can be found at http://wiki.eclipse.org/images/0/08/Demonstrator.pdf  
+
 
+
We will synchronize within the WP5 telcos on next steps and report progress (effort & milestones).
+
  
 
<br>
 
<br>

Latest revision as of 17:13, 5 February 2014

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.

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.

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.

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