Difference between revisions of "Auto IWG WP5"

Revision as of 11:37, 18 April 2012

WP5: Eclipse Qualification Kit (ISO26262)

This is work package 5 of the Automotive Industry Working Group.

• WP Lead: Virtual Vehicle (M. Driussi)

Intent

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. WP5 has set itself the goal to work on this topic for Eclipse Plugins, which are used in this context. 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.

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 18.04.2012 13p.m. (Outlook appointment)

Next Steps

• Discuss the Roadmap internally / expand it / change it. The Roadmap can be found here [2]
• Build the working team to contribute to the roadmap.
• 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.

Qualification Roadmap (contact: Oscar Slotosch, Validas)

See http://wiki.eclipse.org/images/1/1e/EclipseQualificationProcess.pdf for an overview (as presented on 4th april by Validas)

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

The following results have been achieved to elaborate the proposal

• Checklist for DO-330 compliance (cannot be published due to RTCA restrictions)
• Example requirements document (will be checked for DO-330 compliance), see http://wiki.eclipse.org/images/f/fc/TCAToolRequirements.zip
• 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. The following steps have been achieved:

• First Steps (21th of march 2012) see http://wiki.eclipse.org/images/8/8d/EclipseRoadmapFirst.pdf
• Second steps (4th april 2012) http://wiki.eclipse.org/images/6/63/EclipseRoadmapSecond.pdf
• Third Steps (18th april 2012) http://wiki.eclipse.org/images/0/02/EclipseRoadmapThird.pdf

Since the presentations are extended, it suffices to read the latest.