Documents and Terms
The Eclipse Industry Working Group (IWG) Policy Eclipse Industry Working Group Process
The Guidelines for Eclipse Logos & Trademarks 
Other working group charter or proposals
Goals and Vision
The goal of the Polarsys group is to collaboratively define, build and maintain open source tools for safety-critical and embedded system development in demanding engineering domains, such as aerospace, defense and security, transportation, energy, healthcare, telecommunications.
These domains typically require maintenance of tool chains for the very long term – from 30 to up to 50 to 70 years in some cases – which create some very unique issues. Another characteristic of the working group is to address material for qualification processes – like in the DO 178 for Aircraft or ISO 26262 for Automotive.
Additionally, Polarsys intends to foster exchanges between academics and industrial partners in these domains and manage the maturity of tools from early research prototypes to the obsolescence of tools.
To implement this vision, the IWG group and the Eclipse Foundation will collaborate to provide services and to:
- Maintain the infrastructure required for the hosting of IWG projects, including software repositories, software build and test facilities.
- Proceed to IP due diligence in order to provide clean open source software released under EPL or other licenses validated by the IWG like BSD-like and LGPL.
- Define the software tools to be contained in each release of the tool chains (with specific roadmaps and release trains).
- Create a labelling process to recognize projects maturity and companies know-how and commitment .
- Create a software quality assessment kit to define the maturity level of each component.
- Digitally sign certified software releases made available under the IWG banner.
- Make those binary software releases available only to the members of IWG.
Polarsys focuses on techniques and tools to fulfill the Polarsys goal and vision, and mainly on:
- System, Hardware and Software Modeling
- Code analysis (static code analysis)
- Debugging, tracing and other integration tools
- Transversal process support tools : Configuration Management, Change tracking, Technical facts management, Project reporting
- Test and verification tools targeting embedded software methods, simulation and early validation
- Embedded components (RTOS, Middleware, ...)
- System on Chip simulation and Hardware logic (VHDL, SystemC, ...)
- UI Modeling, UI DSL language and extensible code generation
Other domain specific techniques and tools can be proposed for acceptance by the IWG steering committee.
Polarsys will be governed as an Eclipse Industry Working Group under a IWGCharter drafted by the existing OPEES consortium with the support of the EMO. This charter will stipulate the requirement of those members who are on the Steering Committee and those who are Participating Members.
Funding and Services
An entity must be at least Solutions Members of the Eclipse Foundation and adhere to the IWG under the conditions and acording to the fees defined in the IWGCharter to participate to the Polarsys IWG.
The IWG membership gives access to additional services and infrastructure including:
- Long term support, including build infrastructure, release downloads, digital signing for release signing, etc.
- Access to all the IWG private resources hosted in the Polarsys IWG firewalled web area, for instance Components Qualification Kits, Long Term Support (LTS) and Very Long Term Support (VLTS) Binary Releases
- IWG-specific test and certification programs.
- Participation to the Polarsys components Change Control Boards
- Legal reviews required for any projects which are part of the IWG initiative but not hosted at Eclipse.
This part presents the tentative roadmap of Polarsys for 2011 and 2012.
- September 2011: Submission of the IWG proposal
- From September 2011: Gathering the IWG community
- November 2011: Announcement and kick-off of the IWG during the EclipseCon Europe
The purpose is to start aligning the Polarsys roadmap on the Eclipse release train.
For each version, Polarsys will release two deliverables: the official Polarsys release and the experimental Polarsys release.
TopCased components will start populating the experimental release in 2012. After graduation, and at their pace, they will progressively join the offical release. A TopCased component such as MDT-Papyrus, which is also an Eclipse component, will be aggregated to the first official release.
Components with the Polarsys label (i.e., which necessary conform to the Polarsys goals), and mature enough, will also be integrated to the first official release.
Some components, for instance from academics, will be aggregated to the experimental release.