Jump to: navigation, search

Difference between revisions of "Auto IWG WP5"

(Qualification Roadmap)
 
(2 intermediate revisions by the same user 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)
+
 
 +
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 [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.
  
== Intent ==
+
== Qualification Process and Roadmap ==
  
Main Saftey standards (ISO 26262, EN 50128, DO 178C, DO 278A, DO-330, IEC 61508) require tool qualification.
+
The goal is not to qualify Eclipse completly but to enable tool developers using Eclispe as a plattform to develop qualifyable plugins.
WP5 of Automotive Industrial working group has set itself the goal to work on this topic for Eclipse.
+
The goal is not to qualify Eclipse 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  
 
We have identified the DO-330 as first, domain independant tool qualification standard that satisfies the requirements of  
Line 16: Line 27:
 
We have specified a roadmap to provide an infrastructure that support the develment of qualifyable Eclipse plugins by  
 
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.
 
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.
  
Currently we are working step by step to implement the roadmap, starting with the support of the lowest (TQL-5) level and using
+
Our current experience is that it suffices to fill the qualification model manually and to build a qualification kit
qualification support tools from Validas for case studies until the integrated Eclipse tool support is in place.  
+
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 infrastructure, but it enables us to qualify  
+
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.
 
Eclipse tools now. See the presentation in Ludwigsburg https://wiki.eclipse.org/images/6/65/EclipseRoadmap2103.pdf for more details.
  
== Meetings and Activities ==
+
== 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 [http://wiki.eclipse.org/images/e/ef/Eclipse_Automotive_IWG_WP5_Telco_07_03_2012_Minutes_of_Meeting.pdf]
 
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]
Line 42: Line 72:
 
* Crystal-UseCase description [http://wiki.eclipse.org/images/0/0c/Crystal_UseCase_Proposal_AUTO_IWG_WP5_v03.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
 
* 28.10.2013 (Ludwigsburg), see https://wiki.eclipse.org/images/6/65/EclipseRoadmap2103.pdf
 
== Next Steps ==
 
 
We are on the road towards tool qualification towards Eclipse. The following steps are the nexts.
 
You are invited to join us.
 
* Finalization of the concept (Review against DO-330, Tracing and Réview against ISO-26262)
 
* Qualification of important Eclipse-based tools
 
* Demonstration of the concept (prototype) for non-Eclipse-based developments
 
* Collection of ressources for the QPP project to integarte the model into Eclipse
 
 
All interested parties are invited to participate. Commitment on WP5 telco or webex meeting.
 
 
== Qualification Roadmap ==
 
 
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)
 
On the Eclipse Day in Toulouse (24th of May 2012), http://www.eclipsedaytoulouse.com/en/ Oscar Slotosch presented an overview on
 
the roadmap and the curent status.
 
 
*WP5.1 Definition of Goals & Requirements
 
*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
 
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
 
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",...
 
 
The conecpt is described with in the following three documents (and the model):
 
* HowTo Qualify Exclipse-based Tools
 
* Tool Development Plan for Every Qualifiable Eclipse Plugin
 
* Tool Verification Plan for Every Qualifiable Eclipse Plugin
 
* The DO-330 model (EMF)
 
 
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
 
 
<br>
 
 
----
 
 
We (Validas, BMW-CarIT, Virtual Vehicle) have started a small demonstration of the process.
 
 
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>
 
 
----
 
 
 
Business Model:
 
 
<br>
 
Tool qualification needs a business model and we think that it should be open for every user of eclipse to use and to provide
 
tool qualification kits for Eclipse. Currently we are discussing this the idea of pay per qualification as http://wiki.eclipse.org/images/e/ed/PayPerQualification.pdf
 
  
 
<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