Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Auto IWG WP4"
(→WP4: Functional Safety Relevant Development Process and Environment) |
|||
Line 13: | Line 13: | ||
* Define approach | * Define approach | ||
* Connect to OPEES, OpenETCS | * Connect to OPEES, OpenETCS | ||
− | * SAFE project: [http://www.safe-project.eu/] | + | * SAFE project: [http://www.safe-project.eu/] [http://wiki.eclipse.org/Image:SAFE-Overview.pdf#filelinks] |
* SafeCer Overview: [http://wiki.eclipse.org/images/2/2f/SafeCer_Overview_VIF_v02.pdf] | * SafeCer Overview: [http://wiki.eclipse.org/images/2/2f/SafeCer_Overview_VIF_v02.pdf] | ||
[[Category:Auto IWG]] | [[Category:Auto IWG]] |
Revision as of 09:50, 17 July 2012
WP4: Functional Safety Relevant Development Process and Environment
This is work package 4 of the Automotive Industry Working Group.
- WP Lead: ITEMIS (A. Graf)
Functional Safety has an impact on Eclipse based tooling in two dimensions: First, which tools can be used to develop safety-relevant functions. Secondly, what are the implications of standards like ISO26262 on the development of Eclipse-based tooling?
This work package has one initial task: Every company rep to discuss internally who the right people within the organizations are to connect to