Your SlideShare is downloading. ×
0
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Open-Do - Initial concepts and idea
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Open-Do - Initial concepts and idea

1,892

Published on

Concepts and ideas behind the Open-DO initiative. Presented by Cyrille Comar (AdaCore) at the DO-178C committee meeting in Cologne, Germany.

Concepts and ideas behind the Open-DO initiative. Presented by Cyrille Comar (AdaCore) at the DO-178C committee meeting in Cologne, Germany.

Published in: Technology
1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total Views
1,892
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
73
Comments
1
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. A call for action Cyrille Comar [email_address] Matteo Bordin [email_address] www.open-do.org
    • 2. Summary <ul><ul><li>Introduction </li></ul></ul><ul><ul><li>FLOSS &amp; Open Source Communities </li></ul></ul><ul><ul><li>Introducing Open-DO </li></ul></ul><ul><ul><li>Why an Open Initiative for DO-178? </li></ul></ul><ul><ul><li>Keys to Success </li></ul></ul><ul><ul><li>Annex: Description of the mentioned projects </li></ul></ul>
    • 3. Which Arinc 653 OS will be around in 15 years? <ul><ul><li>Commercial Solutions </li></ul></ul><ul><ul><ul><ul><li>- WRS, Sysgo, LynuxWorks, GHS, DDCI </li></ul></ul></ul></ul><ul><ul><li>Private Solutions maintained internally by Avionics companies </li></ul></ul><ul><ul><ul><ul><li>- At least 3 in Europe &amp; 1 in the US </li></ul></ul></ul></ul><ul><ul><li>Experimental </li></ul></ul><ul><ul><ul><ul><li>- RTEMS + 653 interface </li></ul></ul></ul></ul>Introduction Any lessons from what happened in the Unix world?
    • 4. FLOSS License Free to use… for ever Free to look at sources Free to change Free to redistribute
    • 5. Open Source Communities <ul><ul><li>Significant technologies are successfully managed by such communities: </li></ul></ul><ul><ul><li>- The Linux Kernel </li></ul></ul><ul><ul><li>- Eclipse </li></ul></ul><ul><ul><li>- GCC </li></ul></ul><ul><ul><li>- RTEMS </li></ul></ul><ul><ul><li>- Mono </li></ul></ul><ul><ul><li>- Python </li></ul></ul><ul><ul><li>… </li></ul></ul><ul><ul><li>For more than 20 years now </li></ul></ul>
    • 6. Open Source Communities The GCC example … and many more <ul><ul><li>Contributors: from individuals to corporations </li></ul></ul><ul><ul><li>Sharing technology not products </li></ul></ul>
    • 7. Roles in Open Source Communities <ul><li>Active participants </li></ul><ul><ul><li>Short term cost increase </li></ul></ul><ul><ul><ul><ul><li>Learning curve </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Working in an open environment </li></ul></ul></ul></ul><ul><ul><ul><ul><li>- Contributing back </li></ul></ul></ul></ul><ul><ul><li>Long term cost decrease by </li></ul></ul><ul><ul><ul><ul><li>- Sharing Resources </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Solving a common problem </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Avoiding solving already solved problems </li></ul></ul></ul></ul>Initiators &amp; regulators <ul><li>Passive Users </li></ul><ul><ul><ul><li>Benefit from the work of others </li></ul></ul></ul><ul><ul><ul><li>Can’t customize to their own needs </li></ul></ul></ul><ul><ul><ul><li>Help spread the technology </li></ul></ul></ul>
    • 8. <ul><li>What about the DO-178 community? </li></ul><ul><li>Is there a need for openness &amp; cooperation? </li></ul><ul><li>Potential for community growth? </li></ul><ul><li>AVSI (Aerospace Vehicle Systems Institute) </li></ul><ul><li>Certify Together </li></ul><ul><li>This comittee </li></ul><ul><li>military </li></ul><ul><li>space, automotive, … </li></ul>
    • 9. Some Relevant Open Projects &amp; Technologies OSEE Couverture SPARK
    • 10. Some Relevant Open Projects &amp; Technologies OSEE Couverture SPARK
    • 11. Libre Open Source High Assurance Certification Agile Lean The meeting of 3 worlds Open - DO Concepts
    • 12. Libre Open Source High Assurance Certification Agile Lean Visibility Resiliance Sharing Reuse Iterative requirements Continuous Integration Test Driven Development … Qualified tools Life cycle traceability Req based testing Open - DO Concepts
    • 13. Relevant Agile/Lean Concepts Test Driven Development Requirement Based testing Executable Specifications Continuous Integration IP 217 Iterative requirements
    • 14. Open - DO Challenges Opening &amp; sharing more than “source code” - requirements, designs, testcases … Life-Cycle Traceability Agile Workflows for the DO-178
    • 15. Some DO-178B workflows Software Life Cycle Process Integral Processes Top level workflow Transition criteria between activities Workflow support Workflow verification System aspects related to Software Development Section 2 Overview of aircraft and engine certification Section 10 Software Life Cycle - section 3 Software Planning Process – Section 4 Software Development Processes – Section 5 Software Verification - section 3 Software Config Management – section 7 Software Quality Assurance - Section 8 Certification Liaison - section 9 Software Life Cycle Data – Section 11 Additional Considerations – Section 12
    • 16. Some DO-178B workflows (2) Software Life Cycle Process Integral Processes Requirement coverage Code coverage Traceability Component certification workflow System aspects related to Software Development Section 2 Overview of aircraft and engine certification Section 10 Software Life Cycle - section 3 Software Planning Process – Section 4 Software Development Processes – Section 5 Software Verification - section 3 Software Config Management – section 7 Software Quality Assurance - Section 8 Certification Liaison - section 9 Software Life Cycle Data – Section 11 Additional Considerations – Section 12 Requirements Design Coding Reviews Testing Completeness Analysis
    • 17. Some DO-178B workflows (3) Software Life Cycle Process Integral Processes Qualification of Verification Tools Workflow Requirement Coverage Traceability OSEE System aspects related to Software Development Section 2 Overview of aircraft and engine certification Section 10 Software Life Cycle - section 3 Software Planning Process – Section 4 Software Development Processes – Section 5 Software Verification - section 3 Software Config Management – section 7 Software Quality Assurance - Section 8 Certification Liaison - section 9 Software Life Cycle Data – Section 11 Additional Considerations – Section 12 Tool Operational Requirements Reviews Testing Completeness Analysis
    • 18. Open DO Components Open-Do Workflows Document Templates Qualifiable Tools Education Materials Certifiable Components
    • 19. Open-Do Workflows Document Templates Qualifiable Tools Education Materials Certifiable Components Specialized for given certification standards Open DO Components
    • 20. Open-Do Workflows Document Templates Qualifiable Tools Education Materials Certifiable Components OSEE Couverture … Gene-auto Topcased Open DO Components
    • 21. Open-Do Workflows Document Templates Qualifiable Tools Education Materials Certifiable Components Toy certifiable projects Specialized Examples (e.g. for do-178c annexes) Open DO Components
    • 22. Open-Do Workflows Document Templates Qualifiable Tools Education Materials Certifiable Components OS runtimes IP stack middleware … Open DO Components
    • 23. Open-Do Workflows Document Templates Qualifiable Tools Education Materials Certifiable Components PSAC SDP, SVP, SCMP… Standards SAS … Open DO Components
    • 24. Why an open initiative for the DO-178 world?
    • 25. Why Open-DO? <ul><ul><li>Educational materials for clarifying intent </li></ul></ul><ul><ul><ul><li>Experimental test-bed for annexes </li></ul></ul></ul>A support to the DO-178C effort
    • 26. <ul><ul><li>Provides a shared infrastructure </li></ul></ul><ul><ul><li>- For long term investment </li></ul></ul><ul><ul><li>- For long term cost reduction </li></ul></ul><ul><ul><ul><li>Allows some level of cooperation with competitors </li></ul></ul></ul><ul><ul><ul><li>Lower training costs (especially for subcontractors) </li></ul></ul></ul>Avionics industrial community Why Open-DO?
    • 27. <ul><ul><li>Lower training costs for DERs </li></ul></ul><ul><ul><ul><li>Vehicle for clarifying specific issues </li></ul></ul></ul><ul><ul><ul><li>Help sharing or practices between authorities </li></ul></ul></ul>Certification authorities Why Open-DO?
    • 28. <ul><ul><li>Offers an ideal showcase for their open technologies </li></ul></ul><ul><ul><ul><li>Tool sharing makes it easier to provide a complete supported solution </li></ul></ul></ul><ul><ul><ul><li>Creates and ecosystem where everyone can meet potential </li></ul></ul></ul><ul><ul><ul><li>customers and partners </li></ul></ul></ul>Tool providers Why Open-DO?
    • 29. <ul><ul><li>Balance </li></ul></ul><ul><ul><li>- Europe vs US </li></ul></ul><ul><ul><li>- Boeing vs Airbus </li></ul></ul><ul><ul><li>- Authorities vs Industry </li></ul></ul><ul><ul><li>Find key participants for critical mass </li></ul></ul><ul><ul><li>- Certification authorities </li></ul></ul><ul><ul><li>- Major Aeronautics players </li></ul></ul><ul><ul><li>- Established tool providers </li></ul></ul><ul><ul><li>- Academics </li></ul></ul><ul><ul><li>Attract public funds for bootstrap </li></ul></ul><ul><ul><ul><li>Find appropriate governance rules </li></ul></ul></ul>Keys to success <ul><li>define « Open Source 2010 » </li></ul><ul><li>certification workflows </li></ul>
    • 30. Annex – Information on Mentioned Projects OSEE Couverture SPARK
    • 31. System Engineering Environment Focus on system engineering Open to external tool integration Open development philosophy Integrated management environment OSEE <ul><ul><li>Application life cycle management system </li></ul></ul><ul><ul><li>First-class Eclipse project contributed by </li></ul></ul><ul><ul><li>- www.eclipse.org/osee </li></ul></ul><ul><ul><ul><li>- Apache Team (Phoenix, AZ) </li></ul></ul></ul><ul><ul><ul><li>- 5 years in development, 5 people full-time </li></ul></ul></ul><ul><ul><ul><li>- Not specific to DO-178 </li></ul></ul></ul>
    • 32. Development Artifacts Tracking Requirements Test cases Test procedures Models Code Tests Tests Actual Output Tests Expected Output OSEE Development Artifacts (import artifacts from external tools) Traceability Model OSEE
    • 33. Slide: Requirements Test cases Test procedures Design Code Tests Test Actual Output Test Expected Output OSEE &amp; Traceability End-to-End Traceability Model
    • 34. Slide: Define Development Teams Assign Members to Teams Joe John Ryan Don Qualification Verification Analysis Joe Don Workflow Instantiation (example: verification of a REQ_1_2b) assign assign OSEE &amp; Workflow Modeling/Tracking
    • 35. Slide: TOPCASED <ul><ul><li>T oolkit in OP en source for C ritical A pplication &amp; S yst E m D evelopment </li></ul></ul><ul><ul><li>www.topcased.org </li></ul></ul>(formal) analysis Design / Analysis Model Metamodel Code
    • 36. TOPCASED (II) <ul><ul><li>An Integrated Eclipse Distribution </li></ul></ul><ul><ul><li>The Future Official Eclipse Solution for UML modeling </li></ul></ul><ul><ul><ul><li>http://wiki.eclipse.org/MDT-Papyrus-Proposal </li></ul></ul></ul>UML SysML AADL … Graphical Modeling Model Transformation Framework ECore
    • 37. Slide: GeneAuto <ul><ul><li>- A Qualifiable Generic Framework for Code Generation </li></ul></ul><ul><ul><li>Dynamic Systems Modeling: Simulink/StateFlow, Scicos </li></ul></ul><ul><ul><li>Targeting C (and Ada soon) </li></ul></ul><ul><ul><li>Available as a FLOSS </li></ul></ul><ul><ul><li>along with qualification material (planned) </li></ul></ul><ul><ul><li>Partners: Airbus, Continental, Thales-Alenia, Barco, IAI, … </li></ul></ul>… … Qualified Input Model Intermediate representation Code
    • 38. Slide: SPARK <ul><ul><li>Annotation of Ada programs for Formal Analysis </li></ul></ul><ul><ul><ul><li>Partial correctness </li></ul></ul></ul><ul><ul><ul><li>Information/Data Flow </li></ul></ul></ul><ul><ul><li>The whole technology is NOW available as a FLOSS </li></ul></ul><ul><ul><li>http://www.praxis-his.com/sparkada/ </li></ul></ul>Ada SPARK
    • 39. Couverture <ul><ul><li>Language-Independent Structural Coverage Framework </li></ul></ul><ul><ul><ul><li>Source coverage WITHOUT instrumentation (st, dc, mc/dc) </li></ul></ul></ul><ul><ul><ul><li>Object Coverage (instructions, branches) </li></ul></ul></ul><ul><ul><li>Instrumented Simulation Framework </li></ul></ul><ul><ul><li>The whole technology will be available as a FLOSS… </li></ul></ul><ul><ul><li>including the qualification material </li></ul></ul><ul><ul><li>https://libre.adacore.com/coverage/ </li></ul></ul>
    • 40. Slide: Couverture (II) if Pression (M) &gt;= P_Limit then Alarme (M, « PRE ») elsif Temperature (M) &gt;= T_Limit then Alarme (M, « TEMP ») end if ; 0x12460 0X12464+ ... Source Code Cross Compiler Instrumented, Virtualized Execution Environment Execution Traces Object Coverage Report (instruction, branch) Source Coverage Report (statement, DC, MC/DC)
    • 41. Upcoming Events The Lean, Agile Approach to High-Integrity Software Paris - March 26 th , 2009 Jim Sutton, Lockheed Martin Alexandre Boutin, Yahoo Emmanuel Chenu, Thales David Jackson, Praxis High-Integrity Systems Cyrille Comar, AdaCore Open-Do Masterclass @ Avionics EU Amsterdam - March 11 th -12 th , 2009 Franco Gasperoni, AdaCore Open-Do Masterclass @ Avionics US San Diego – June, 1 st – 2 nd , 2009 Ryan Brooks , Boeing Robert B.K. Dewar, AdaCore [email_address] Next Informal Open-DO Meeting @ EclipseCon 2009 Santa Clara, March 21 st -25 th , 2009 Airbus, Boeing, AdaCore

    ×