DO C tutorial is designed by TONEX to help you improve your overall DO- C is the modified and updated version of DOB/EDB (), which. The difference between creating aviation software and other software can be summarized in one simple phrase: “RTCA DOB”. If you are. In this Product How-To, Paul Anderson of GrammaTech takes you step by step through the DOB and how use his company’s static analysis.
|Published (Last):||5 July 2017|
|PDF File Size:||4.23 Mb|
|ePub File Size:||12.62 Mb|
|Price:||Free* [*Free Regsitration Required]|
Certification Liaison Process Note: Even the use of the requirement after the implemented features have been deployed and used should be traceable. So getting an FAA project number is usually the first thing to be done in a project. The system safety assessments combined with methods such as SAE ARP A determine the after mitigation DAL and may allow reduction of the DOB software level objectives to be satisfied if redundancy, design safety features and other architectural forms of hazard mitigation are in requirements driven by the safety analyses.
Of course, that is not possible if your product is highly innovative, because then it will be the first of its kind and there won’t be any applicable TSO. Requirements traceability is concerned with documenting the life of a requirement. Software whose failure would cause or contribute to a major failure condition.
To install the same equipment on another type of aircraft or rather, supplementing a different TCyou need to obtain a second STC. The FAA applies DOB as the document it uses for guidance to determine if the software will perform reliably in an airborne environment,  when specified by the Technical Standard Order TSO for which certification is sought.
That depends on what level of compliance you want to achieve. Software whose failure would cause or contribute to a minor failure condition.
Companies providing these kind of tools as COTS are subject to audits from the certification authorities, to which they give complete access to source code, specifications and all certification artifacts.
A Simple Phrase
This is the case for document “DOB”, which defines the guidelines for development of aviation software. The configuration management process typically provides archive and revision identification of:.
All items are not required at all certification levels. Inexpensive certification depends on the documents not only saying the right things, but saying them in the right way, in the right order. It is the software safety analyses that drive the system safety assessments that determine the DAL that drives the appropriate level of rigor in DOB.
Software Configuration Management Process 3. On a real project, the actual activities that will be done in the context of a process must be shown to support the objectives. A third party tool can be qualified as a verification tool, but development tools must have been developed following the DO process.
DOB – Wikipedia
For levels higher than that you may or may not need library source code depending on how your test procedures are designed. I do not understandand cannot give you advice onthe many other aspects of your project that this encompasses. You need to know how to read it.
If you want to develop aviation software, you’ll have to have a copy of DOB. Your tutoriaal test procedure must insure that all possible arguments supplied to any library function used are tested. This objective-based nature of DOB allows a great deal of flexibility in regard to following different styles of software life cycle.
Don’t start testing until your product is completely debugged, tested and ready to release. There are many possible and acceptable ways for a real project to define these aspects. The safety assess ment is done at the beginning of the development cycle and based on the assess ment the objectives for the level are complied with. The signoff is via FAA form High degree of product focus leading to quality product. DOB specifies that each line of code is required and tested, and that no unused code exists in the application program build.
Views Read Do–178b View history. If you happen to uncover a bug during certification testing, and have to change your code at all, the entire certification tests must be re-run to be compliant.
Seemingly, the simplest method of certifying the product is to do it under an existing TSO.