Jump to: navigation, search

Difference between revisions of "Polarsys/Proposal"

(Core domains)
(Goals and Vision)
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Documents and Terms ==
 
The Eclipse Industry Working Group (IWG) Policy [http://www.eclipse.org/org/industry-workgroups/industry_wg_process.php Eclipse Industry Working Group Process]
 
 
The Guidelines for Eclipse Logos & Trademarks [http://www.eclipse.org/legal/logo_guidelines.php]
 
 
=== Other working group charter or proposals ===
 
[http://wiki.eclipse.org/Auto_IWG Auto IWG starting page]
 
 
[http://wiki.eclipse.org/index.php?title=Machine-to-Machine/M2MIWG_charter_draft M2M IWG charter draft]
 
 
[http://wiki.eclipse.org/EclipseLTS LTS program wiki page]
 
 
 
== Goals and Vision ==
 
== 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.
+
In demanding engineering domains, such as aerospace, defense and security, transportation, energy, healthcare or telecommunications, safety-critical and embedded system development has to deal with several strong requirements:
 +
;Innovation: ensuring the highest levels of safety, reliability, service and performance implies a Continuous effort of Research & Development, not only on the products themselves but also on the development methods & tools.
 +
;Computer Assistance and Automation: the numerous and complex operations required to develop and maintain industrial systems imply a high level of automation based on software tools.
 +
;Certification: from DO178 to ISO26262 and ECSS 40, the development of safety-critical and embedded system has to comply with strict regulations impacting not only the final product, but also its development process and the tools used to build it.
 +
;Very Long Term Support: typical products have life cycles that go from 30 years up to 70 years. During all this time, the tool chains have to remain operational.
  
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.
+
Polarsys aims at answering these needs by:
+
*Providing a set of industry-friendly open source tools & components.
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.
+
*Providing collaborative means to make open innovation easier.
 
+
*Fostering exchanges between academics and industrial partners.
To implement this vision, the IWG group and the Eclipse Foundation will collaborate to provide services and to:
+
*Operating dedicated software repositories, build chains, test facilities, etc.
* Maintain the infrastructure required for the hosting of IWG projects, including software repositories, software build and test facilities.
+
*Managing the quality and maturity of tools & components from early research prototypes up to the obsolescence.
* 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.
+
*Mutualizing the research, development and maintenance efforts as far as possible.
* Define the software tools to be contained in each release of the tool chains (with specific roadmaps and release trains).
+
*Organizing sustainable commercial services & ecosystem around those components.
* Create a labelling process to recognize projects maturity and companies know-how and commitment .
+
*Providing the documents required to cope with certification issues.
* Create a software quality assessment kit to define the maturity level of each component.
+
*Recognizing projects maturity and companies know-how and commitment through a Labeling process.
* Digitally sign certified software releases made available under the IWG banner.
+
* Make those binary software releases available only to the members of IWG.
+
  
 
== Core domains ==  
 
== Core domains ==  
Polarsys focuses on techniques and tools to fulfill the Polarsys goal and vision, and mainly on:
+
Polarsys focuses on techniques and tools to fulfill its goal and vision, and mainly on:
 
* System, Hardware and Software Modeling
 
* System, Hardware and Software Modeling
 
* Code analysis (static code analysis)
 
* Code analysis (static code analysis)
Line 36: Line 26:
 
* Embedded components (RTOS, Middleware, ...)
 
* Embedded components (RTOS, Middleware, ...)
 
* System on Chip simulation and Hardware logic (VHDL, SystemC, ...)
 
* 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.
 
Other domain specific techniques and tools can be proposed for acceptance by the IWG steering committee.
  
 
== Governance ==
 
== Governance ==
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.
+
Polarsys will be governed as an Eclipse Industry Working Group under a charter drafted by the [http://www.opees.org/ OPEES consortium] with the support of the EMO. [[Polarsys/Charter | This charter]] will describe rights & duties of Polarsys' members.
  
 
== Funding and Services ==
 
== Funding and Services ==
An entity must be at least [http://www.eclipse.org/membership/become_a_member/membershipTypes.php#solutions 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.
+
An entity must be at least [http://www.eclipse.org/membership/become_a_member/membershipTypes.php#solutions Solutions Members] of the Eclipse Foundation and adhere to the IWG under the conditions and acording to the fees defined in the [[Polarsys/Charter | Polarsys Charter]] to participate to the Polarsys IWG.
  
 
The IWG membership gives access to additional services and infrastructure including:
 
The IWG membership gives access to additional services and infrastructure including:
Line 62: Line 51:
 
* Combitech
 
* Combitech
 
* Ericsson
 
* Ericsson
 +
* European Space Agency
 
* Indra
 
* Indra
 
* Inria
 
* Inria
 +
* Intecs France
 
* Obeo
 
* Obeo
 
* Technalia
 
* Technalia
 
* Thales
 
* Thales
 
* UPV
 
* UPV
 +
* Soyatec
 +
 +
== Other working group charter or proposals ==
 +
The following IWG have some common objectives with Polarsys:
 +
*[http://wiki.eclipse.org/Auto_IWG Auto IWG starting page]
 +
*[http://wiki.eclipse.org/index.php?title=Machine-to-Machine/M2MIWG_charter_draft M2M IWG charter draft]
 +
*[http://wiki.eclipse.org/EclipseLTS LTS program wiki page]
 +
 +
We will foster coordination and sharing as far as possible.
  
 
== Tentative roadmap ==
 
== Tentative roadmap ==
Line 73: Line 73:
  
 
=== 2011 Milestones ===
 
=== 2011 Milestones ===
* September 2011: Submission of the IWG proposal
+
* September 2011: Submission of Polarsys proposal
* From September 2011: Gathering the IWG community
+
* September 2011-December 2012: Gathering Polarsys community
* November 2011: Announcement and kick-off of the IWG during the EclipseCon Europe
+
* November 2011: Announcement of Polarsys during EclipseCon Europe
 +
* January 2012: Kick-off of Polarsys
  
 
=== 2012 Milestones ===
 
=== 2012 Milestones ===
 
The purpose is to start aligning the Polarsys roadmap on the Eclipse release train.<br>
 
The purpose is to start aligning the Polarsys roadmap on the Eclipse release train.<br>
 
For each version, Polarsys will release two deliverables: the official Polarsys release and the experimental Polarsys release.<br>
 
For each version, Polarsys will release two deliverables: the official Polarsys release and the experimental Polarsys release.<br>
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.<br>
+
[http://www.topcased.org 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 [http://www.eclipse.org/projects/project.php?id=modeling.mdt.papyrus MDT-Papyrus], which is also an Eclipse component, will be aggregated to the first official release.<br>
 
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.<br>
 
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.<br>
 
Some components, for instance from academics, will be aggregated to the experimental release.
 
Some components, for instance from academics, will be aggregated to the experimental release.
 +
 +
== Organization and Contact ==
 +
For more information, please contact gael (dot) blondelle (at) obeo (dot) fr or ralph (dot) mueller (at) eclipse (dot) org.
 +
 +
You can also subscribe to the [https://dev.eclipse.org/mailman/listinfo/polarsys-iwg polarsys-iwg mailing list] in order to join the discussions. <br \>
 +
 +
== Documents and Terms ==
 +
The Eclipse Industry Working Group (IWG) Policy [http://www.eclipse.org/org/industry-workgroups/industry_wg_process.php Eclipse Industry Working Group Process]
 +
 +
The Guidelines for Eclipse Logos & Trademarks [http://www.eclipse.org/legal/logo_guidelines.php]

Latest revision as of 10:55, 10 January 2012

Goals and Vision

In demanding engineering domains, such as aerospace, defense and security, transportation, energy, healthcare or telecommunications, safety-critical and embedded system development has to deal with several strong requirements:

Innovation
ensuring the highest levels of safety, reliability, service and performance implies a Continuous effort of Research & Development, not only on the products themselves but also on the development methods & tools.
Computer Assistance and Automation
the numerous and complex operations required to develop and maintain industrial systems imply a high level of automation based on software tools.
Certification
from DO178 to ISO26262 and ECSS 40, the development of safety-critical and embedded system has to comply with strict regulations impacting not only the final product, but also its development process and the tools used to build it.
Very Long Term Support
typical products have life cycles that go from 30 years up to 70 years. During all this time, the tool chains have to remain operational.

Polarsys aims at answering these needs by:

  • Providing a set of industry-friendly open source tools & components.
  • Providing collaborative means to make open innovation easier.
  • Fostering exchanges between academics and industrial partners.
  • Operating dedicated software repositories, build chains, test facilities, etc.
  • Managing the quality and maturity of tools & components from early research prototypes up to the obsolescence.
  • Mutualizing the research, development and maintenance efforts as far as possible.
  • Organizing sustainable commercial services & ecosystem around those components.
  • Providing the documents required to cope with certification issues.
  • Recognizing projects maturity and companies know-how and commitment through a Labeling process.

Core domains

Polarsys focuses on techniques and tools to fulfill its 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, ...)

Other domain specific techniques and tools can be proposed for acceptance by the IWG steering committee.

Governance

Polarsys will be governed as an Eclipse Industry Working Group under a charter drafted by the OPEES consortium with the support of the EMO. This charter will describe rights & duties of Polarsys' 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 Polarsys Charter 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
  • Labelling
  • Legal reviews required for any projects which are part of the IWG initiative but not hosted at Eclipse.

Interested Parties

  • Airbus
  • Astrium
  • Atos
  • CEA
  • CNES
  • Combitech
  • Ericsson
  • European Space Agency
  • Indra
  • Inria
  • Intecs France
  • Obeo
  • Technalia
  • Thales
  • UPV
  • Soyatec

Other working group charter or proposals

The following IWG have some common objectives with Polarsys:

We will foster coordination and sharing as far as possible.

Tentative roadmap

This part presents the tentative roadmap of Polarsys for 2011 and 2012.

2011 Milestones

  • September 2011: Submission of Polarsys proposal
  • September 2011-December 2012: Gathering Polarsys community
  • November 2011: Announcement of Polarsys during EclipseCon Europe
  • January 2012: Kick-off of Polarsys

2012 Milestones

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.

Organization and Contact

For more information, please contact gael (dot) blondelle (at) obeo (dot) fr or ralph (dot) mueller (at) eclipse (dot) org.

You can also subscribe to the polarsys-iwg mailing list in order to join the discussions.

Documents and Terms

The Eclipse Industry Working Group (IWG) Policy Eclipse Industry Working Group Process

The Guidelines for Eclipse Logos & Trademarks [1]