Opees Presentation May 2011

2,134 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,134
On SlideShare
0
From Embeds
0
Number of Embeds
850
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Opees Presentation May 2011

  1. 1. OPEES @DASIA 2011 &
  2. 2. Leader OPEES @Gaël Blondelle
  3. 3. OPEES Open Platform for the Engineering of (Critical) Embedded SystemsMain Objective: Ensure the long term availability of Open Source tools for Critical systems
  4. 4. Long term availability…AIRBUS A300 Life CycleProgram began in 1972, production stopped in 20072007-1972 = 35 years...Support will last until 2050 2050-1972 = 78 years !! On board software development for very long lifecycle products
  5. 5. Long term availability…•  500 point selector switch first release in 1920•  Was still used in the 1980s Life Cycle is usually 30-40 years
  6. 6. Long Term Availability for What? Industry / Commercial worldresearch centres AUTAN ATTOL ATTOL RTRT RTRT AIRBUS MARBEN ATTOL- RATIONAL IBM TESTWARE SCADE SCADE SCADE SCADE SCADE AIRBUS/ VERILOG CS TELELOGIC ESTEREL-Schneider Electric/ Technologies VERILOG Object Object Object /GEODE /GEODE /GEODE VERILOG VERILOG TELELOGIC CAVEAT CEA
  7. 7. Tooling for critical systems The Topcased example
  8. 8. Long Term Availability for Topcased   After its acquisition in 2009, Anyware, the main contributor stopped its activities around Topcased   Thanks to the Open Source approach   The code base has not been lost due to IP (nearly 3M LoC, line A)   The ecosystem was strong enough to find other skilled contributors (no change in the development rate, line B) BA
  9. 9. Focus on Industrial User Strategy End User Requests OSS End User Contributor OSS Requests VAR End User Requests Tools Vendor End User End User End User End User End UsersEnd User ToolsRequests End User Vendor Support Requests Provider End UsersUsers adapt their process to the tools Nearly 80% Features Requests implemented as generic featuresLess than 20% Features Requests accepted 20% implemented as end user extensions Usual Tools Vendor ecosystem OPEES Target ecosystem
  10. 10. OSS as an enablerOSS advantages•  Manage IP issues OSS Freedoms*! Freedom 0!•  Open code and open to run the program, for any purpose! formats enable Freedom 1! to study how the program works, ! – Migration and change it to make it do what ! you wish! – Interoperability Freedom 2 ! to redistribute copies! – Extensibility Freedom 3!•  Lowers vendor lock-in to distribute copies of your ! modified versions to others !•  Share common platforms between tools vendors and industrial users (*) As defined by the Free Software Foundation
  11. 11. OSS is not enough! Additional needs•  Community management•  Ecosystem development – Industrial User centric – Access to skilled professionals – Training, Support, Maintenance – Processes to assess tool maturity•  Very Long Term Support
  12. 12. Maturity of OSS ecosystemsIndustrialUserBenefits OSS OSS + + Community Community + + User Centric Business Ecosystem OSS Ecosystem + Community (OPEES) Eclipse, OW2, OSS (Apache, FSF) Linux foundation Ecosystem Maturity
  13. 13. OPEES in a Nutshell•  Missions – Ensure long-term availability of critical / embedded systems engineering technologies – Secure industry competitiveness and development•  Towards a federation of Industrial Users and Service Providers – Build a sustainable ecosystem around OPEES technologies –  Avoid the creation of one ecosystem per industrial user•  OPEES openly federates some services that were provided by Tools Vendor with lock-in
  14. 14. Comparing Eclipse and OPEESImplemented in Eclipse To be implemented in OPEES•  OSS license Maturity assessment•  OSS governance Industry oriented governance•  Development process Labels•  Collaboration infrastructure regular assessment•  Integrated releases and formal evaluation•  Meritocracy Certification Process•  Project Management Enablement Committees TopCased Quality Kit•  IP Management Change Control Board•  Long Term Support Very Long Term Support
  15. 15. OPEES ITEA project 2009-201235 members from 5 European countries
  16. 16. Next steps•  Implement the OPEES legal entity – Sustainable after the end of the ITEA project•  Grow the community – Approach applies to other domains like •  Railway •  Automotive •  Nuclear
  17. 17. Join the initiative!•  To leverage OSS tools to build your critical embedded software•  To participate in the definition of the Very Long Term Support approach•  To contribute to the content of the catalog•  To exchange with people with similar issues
  18. 18. Thank you

×