Aviation Certification Information, Technical Training, Videos and Free Technical Whitepapers available for download at the website of AFuzion. Free "how-to" technical training videos in DO-178C, DO-254, ARP4754A, ARP4761A, DO-278A, and DO-200B by the world's largest provider of professional training and consulting. AFuzion: the world's first DO-178 training in 1988 and the world's first gap analysis in 1989. Over 15,500 engineers training in 30+ countries by AFuzion's actual trainers - more than all other trainers in the world, COMBINED.
As someone wanting to transition from a rapid-prototype environment to a formal DO-178C environment.. perhaps not for FAA approval, but to develop high quality/safe products for aerospace companies (Lockhead's SEAL Level X, Boeing , etc) , Medical, or Nuclear industries, would love to see a trivial example that goes shows all the steps and outputs. Having a documented process on how code is generated is one thing, but how do you prove safety? Who defines the unit tests? I imagine there are differences between the FAA/ FDA / DOE (DO178X , 13485 / ISO14971 , 414.1x), but what are the typical documents/tools/software , and the typical document/artifacts that are needed in the various stages of the software life cycle. Requirement Management - (IBM Ration) DOORS, JAMA, Xebrio, rmtoo florath , doorstop-dev / doorstop , reqview Static Source Code Analysis - Parasoft, PolySpace, CodeSonar, horusec , sonar cloud, veracode PREFast Dynamic Analysis / Modified Condition/Decision Coverage (MC/DC) - VectorCAST, RapiTest Configuration Management / Storage and Version Control System - Git, SourceSafe, Mercurial, MS TFS QA - Helix ALM V&V - VectorCAST, LDRA Testbed Continuous Integration / CD - Continuous Delivery/Deployment What is the general attitude towards open source software (ex. FreeRTOS) and code-generation tools (ex. ST's Cube MX)? How do CPLD and FPGAs fit in to the picture.. since not exactly software, but they are programmable devices written in an programming language like VHDL , (system)verilog?
As someone wanting to transition from a rapid-prototype environment to a formal DO-178C environment.. perhaps not for FAA approval, but to develop high quality/safe products for aerospace companies (Lockhead's SEAL Level X, Boeing , etc) , Medical, or Nuclear industries, would be interested in an overview of the basic requirements. For example, what are the typical outputs/documents required.. what are the typical software tools that are a must-have in the various stages of the software life cycle.. noting the difference between checking style (N-version programming) and finding bugs: Requirement Management - DOORS, JAMA Static Source Code Analysis - Parasoft, PolySpace, CodeSonar, horusec , sonar cloud, veracode PREFast Dynamic Analysis / Modified Condition/Decision Coverage (MC/DC) - VectorCAST, RapiTest Configuration Management - Git, SourceSafe, Mercurial, MS TFS QA - Helix ALM V&V - VectorCAST, LDRA Testbed ( Continuous Integration / CD - Continuous Delivery/Deployment : Travis CI , Bugzilla, Jira, jenkinsio, GitLab) What is the general attitude towards open source software (ex. FreeRTOS) and code-generation tools (ex. ST's Cube MX)? How do CPLD and FPGAs fit in to the picture.. since not exactly software, but they are programmable devices written in an HDL? What parts of the above are covered in in Vance's 'Aviation Development Ecosystem' book?
Hi Vance - I appreciate the training. My background is aerospace and was the "SME" of software assurance and overall compliance for one of the centers. "Process Assurance" is not "quality on steroids." Quality encompasses so much more. In terms of "process assessments," they are performed to assure (1) processes are documented and baselined, (2) processes are followed, AND (3) processes accomplish intended purposes. More often than not, goal (3) is ignored. However, if the process does not achieve its intended purpose, then why follow it? The process needs to be revised. Thanks again for all the webinars. I met an AFusion representative on one of the missions I supported and worked with him for several years.
Vance, your knowledge and communication style/clarity are outstanding, thank you so much for this and your other really informative and genuinely useful videos.
Thank you John for your kind words! FYI, we do free monthly aviation development/certification webinars on DO-178C, ARP4754A, DO-254, etc; you can follow AFuzion on LinkedIn and get notifications (they're free to AFuzion LinkedIn Followers). Enjoy!
An excellent and highly relevant webinar from AFuzion and Solid Sands. Vance and Marcel make a clear case for focusing on otherwise easy to overlook implications the C standard library has in safety-critical applications. In aviation, in particular, "libraries fly" unlike tools and so should be subject to the same Requirements Based Testing as all other source code under guidance of the relevant standards and according to the software's DAL. And just because it may have come with the compiler doesn't exempt it from suspicion and scrutiny. In addition to highlighting its importance, Marcel explains how requirements and test specifications are developed from libraries and introduces offerings from Solid Sands that support the qualification and certification of the C standard library. Sorry to have missed the live webinar, but glad I could catch the recording. Thanks Vance and Marcel!
Hi Mark - we had four folks replay the entire video and all confirmed audio was fine. If you could provide specifics, we'll check further. Perhaps your connection though?
Hi Kumaran - sorry, our Publisher (AFuzion Press www.afuzion.com) owns the copyright so we cannot share the PPT directly. But the full book is available on Amazon here: www.amazon.com/gp/product/B08ZYNFLTJ/ref=dbs_a_def_rwt_bibl_vppi_i0
I thoroughly appreciate the efforts put by the presenters to deliver a meaningful, high level and yet concise webinar to one of the important guidelines(i would say standard) where most of the companys do not dedicate to time to train the employees. absolutely commendable. Thanks to Vance and Nazan.
