Open-DO: Towards a Lean Approach for Certification (Cyrille Comar)

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite & 1 Group

    Open-DO: Towards a Lean Approach for Certification (Cyrille Comar) - Presentation Transcript

    1. Toward a lean approach to certification Cyrille Comar [email_address] www.open-do.org
    2. Summary
        • Introduction to Open-DO
        • FLOSS & Open Source Communities
        • Lean/Agile vs DO-178
        • Why Open-DO?
        • Possible Open-DO material
        • Keys to Success
      • The Big Freeze Problem
        • Can I change my code after certification ?
          • The ESA anecdote
        • Can I upgrade to a new version of community-developed component ?
          • The AdaCore/Gcc anecdote
      Introduction to Open–DO (1)
    3. Which Arinc 653 OS will be around in 15 years?
        • Commercial Solutions
            • - WRS, Sysgo, LynuxWorks, GHS, DDCI
        • Private Solutions maintained internally by Avionics companies
            • - At least 3 in Europe & 1 in the US
        • Experimental
            • - RTEMS + 653 interface
      Any lessons from what happened in the Unix world? Introduction to Open–DO (2)
    4. The meeting of 3 worlds Introduction to Open–DO (3) Libre Open Source High Assurance Certification Agile Lean
    5. Libre Open Source High Assurance Certification Agile Lean The meeting of 3 worlds Introduction to Open–DO (3)
      • More efficient
      • More reusable
      • More attractive
      • Less costly
      • More visible
      • Easier to learn
    6. The meeting of 3 worlds Introduction to Open–DO (3)
      • More efficient
      • More reusable
      • More attractive
      • Less costly
      • More visible
      • Easier to learn
      Libre Open Source High Assurance Certification Agile Lean
        • FLOSS & Open Source Communities
    7. Open Source Free to use… for ever Free to look at sources Free to change Free to redistribute FLOSS License
    8. Open Source Communities (1)
        • Significant technologies are successfully managed by such communities:
        • - The Linux Kernel
        • - Eclipse
        • - GCC
        • - RTEMS
        • - Mozilla
        • - Open Office
        • - Python
        • For more than 20 years now
    9. The GCC example … and many more
        • Contributors: from individuals to corporations
        • Sharing technology not products
      Open Source Communities (2)
    10. Open Source Communities (3)
      • Active participants
        • Short term cost increase
            • Learning curve
            • Working in an open environment
            • - Contributing back
        • Long term cost decrease by
            • - Sharing Resources
            • Solving a common problem
            • Avoiding solving already solved problems
      Initiators & regulators
      • Passive Users
          • Benefit from the work of others
          • Can’t customize to their own needs
          • Help spread the technology
    11. Open Source Communities (4) Sharing instead of Off-shoring COTS or not COTS?
      • What about the HA/certification community?
      • Is there a need for openness & cooperation?
      • Potential for community growth?
      • AVSI (Aerospace Vehicle Systems Institute)
      • Certify Together
      • The DO-178C committee
      • military
      • space
      • railways, automotive, …
        • Lean/Agile vs DO-178
        • DO-178 vs Lean/Agile
      • Continuous Integration
      • Iterative requirements
      • Test Driven Development
      • (Executable Specifications)
      • Life Cycle Data & Traceability
      • Specific Workflows
      • Requirement Based Testing
      • Emphasis on verification activities
      • Good Software Engineering Practices
      • Guarantee/Improve Quality
    12. Some DO-178B workflows (1) 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
    13. 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
    14. Some DO-178B workflows (3) Software Life Cycle Process Integral Processes Qualification of Verification Tools Workflow Requirement Coverage Traceability 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
    15. Example : Agile Tool Qualification Requirement Coverage Traceability
      • Minimize requalification effort when adding a new TOR
      • Automate requalification for different environment
      • « Natural » traceability model
      • Integrate QA & CM
      • 2 running experiments
      OSEE FitNesse +SVN Tool Operational Requirements Reviews Testing Completeness Analysis
        • Possible Open-DO material
    16. Some Relevant Open Projects & Technologies OSEE Couverture SPARK
    17. Some Relevant Open Projects & Technologies OSEE Couverture SPARK
    18. Open DO Components Open-Do Life Cycle Management Document Templates Qualifiable Tools Education Materials Certifiable Components
    19. Open-Do Document Templates Qualifiable Tools Education Materials Certifiable Components
      • Specialized Workflows
      • Tools supporting them
      Open DO Components Life Cycle Management
    20. Open-Do Document Templates Qualifiable Tools Education Materials Certifiable Components
      • Open verification tools
      • Open Development tools
      • Open (orphan) qualification material
      Open DO Components Life Cycle Management
    21. Open-Do Document Templates Qualifiable Tools Education Materials Certifiable Components Open DO Components Life Cycle Management
      • Toy certifiable projects
      • Training material
      • Specialized DO-178C examples
        • Model Based
        • Formal Methods
        • OOP …
    22. Open-Do Document Templates Qualifiable Tools Education Materials Certifiable Components Open DO Components Life Cycle Management
      • Examples:
        • 653 OS
        • Light DataBase
        • IP stack
        • middleware
        • Standard Classes
    23. Open-Do Document Templates Qualifiable Tools Education Materials Certifiable Components Open DO Components Life Cycle Management
      • Coding Standards
        • C, Ada, …
      • DO-178:
      • PSAC, SDP, SVP, SCMP…
      • Other standards
    24. Why Open-DO ?
        • Provides a shared infrastructure
        • - For long term investment
        • - For long term cost reduction
          • Allows some level of cooperation with competitors
          • Lower training costs (especially for subcontractors)
          • Support for the transition to DO-178C
      Avionics industrial community Why Open-DO?
    25. Why Open-DO?
        • Better understand the needs of this industry
          • Offer adequate training to students
          • Opportunity for applied research activities
      Academics
        • Offers an ideal showcase for their open technologies
          • Tool sharing makes it easier to provide a complete supported solution
          • Creates and ecosystem where everyone can meet potential
          • customers and partners
      Tool providers Why Open-DO?
        • Balance
        • - Europe vs US
        • - Boeing vs Airbus
        • - Authorities vs Industry
        • Find key participants for critical mass
        • - Certification authorities
        • - Major Aeronautics players
        • - Established tool providers
        • - Academics
        • Attract public funds for bootstrap
          • Find appropriate governance rules
      Keys to success
    26. Open-DO Bootstrap
        • One project in Europe (FP7)
        • - call for projects in 1 month (T0)
        • - submission of the proposal : T0 + 4 months
        • One project in the US
        • Others?
        • Share from the start
        • - infrastructures
        • - ideas
        • - activities
        • open-do.org
    SlideShare Zeitgeist 2009

    + AdaCoreAdaCore Nominate

    custom

    435 views, 1 favs, 0 embeds more stats

    In this series of talks, our panel of experts prese more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 435
      • 435 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 16
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Groups / Events