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"
(New page: === WP4: Functional Safety Relevant Development Process and Environment === * WP Lead: ITEMIS (A. Graf) Functional Safety has an impact on Eclipse based tooling in two dimensions: First,...) |
m (categorize, link back) |
||
| Line 1: | Line 1: | ||
=== WP4: Functional Safety Relevant Development Process and Environment === | === WP4: Functional Safety Relevant Development Process and Environment === | ||
| + | This is work package 4 of the [[Automotive Industry Working Group]]. | ||
* WP Lead: ITEMIS (A. Graf) | * WP Lead: ITEMIS (A. Graf) | ||
| Line 13: | Line 14: | ||
* Connect to OPEES, OpenETCS | * Connect to OPEES, OpenETCS | ||
* SAFE project: [http://www.safe-project.eu/] | * SAFE project: [http://www.safe-project.eu/] | ||
| + | |||
| + | [[Category:Auto IWG]] | ||
Revision as of 08:37, 26 October 2011
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
- Identify the stakeholders in the IWG member companies, then (unless otherwise decided)
- Definition of scope
- Clarification of requirements
- Define approach
- Connect to OPEES, OpenETCS
- SAFE project: [1]