DOB, Software Considerations in Airborne Systems and Equipment Certification is a guideline dealing with the safety of safety-critical software used in certain airborne systems. Although technically a guideline, it was a de facto standard for developing avionics software systems until it was replaced in by DOC. 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. The failure conditions are categorized by their effects on the aircraft, crew, and passengers. DOB alone is not intended to guarantee software safety aspects. Safety attributes in the design and implemented as functionality, must receive additional mandatory system safety tasks to drive and show objective evidence of meeting explicit safety requirements.
|Published (Last):||26 July 2004|
|PDF File Size:||14.46 Mb|
|ePub File Size:||16.7 Mb|
|Price:||Free* [*Free Regsitration Required]|
Everyone who boards a plane assumes that it will stay in the air throughout their journey. The reason? It's an update to DOB. DOC classifies safety in five levels. Each level corresponds to the consequence if the software fails. These software safety levels are designated based on risk. And the higher the risk, the more safety objectives need to be met.
And the more difficult it will be to prove compliance. Levels A through C are the most severe. Level A software failures may result in fatalities through a plane crash. Level B software failures may result in passenger injuries. Level C software failures may cause passenger discomfort.
Levels D and E are much more minor. Level D software failures cause passenger inconvenience, such as flight delays. And Level E software failures have no impact on safety. Achieving compliance with DOC is important. Planning is critical. This means you need to gather requirements. And you need to make sure those requirements account for the standard. You can manage these requirements in a number of ways.
Your requirement document might be in Microsoft Word. Or it might be in a sophisticated requirements management tool. Your plan should also include quality assurance. How will you make sure your code is compliant? That makes it easier to ensure quality. This can be achieved by creating a traceability matrix. You also need to make sure the code conforms to a coding standard. This can be achieved through code reviews or by using a static analysis tool.
And, you need to verify your tests and test coverage. One way to do this is by creating tests from a test case. Tool qualification is a part of many compliance standards. DO is a tool qualification requirements standard. It was created for DOC, but it can be used outside of airborne industries. So, DO is an important component of compliance. And using already qualified tools makes this process much easier. And DOC makes it more complex.
If you want to be in compliance with DOC, you need thorough test coverage. With Helix ALM, you can create test cases from requirements. And you can run tests from test cases. This helps you ensure percent test coverage. Traceability is always important for compliance.
And it will significantly boost your ability to comply. With Helix ALM , you can establish links between everything. Quality matters. With Helix QAC , you can improve code quality. Perforce offers a range of tools that can help you get in compliance throughout your development lifecycle.
Helix ALM brings your requirements, tests, and bugs together in one spot. He specializes in technical guidance and product development efficiency for global organizations.
An expert in software development, he is dedicated to helping customers drive quality product strategy.
But achieving compliance can be a challenge. What Is DOC? Planning Planning is critical. Development DOC should be top-of-mind during development processes. This means: Requirements should be clearly defined. Test cases should be developed from requirements.
Code should be written to satisfy those requirements. Tests should satisfy test cases and show that requirements are met. Traceability should link every item.
Traceability Across Development Traceability is always important for compliance. Quality, Guaranteed Quality matters. Recommended Posts. May 20, What Is EN ? Static Analysis.
DO-178C: The Next Avionics Safety Standard tutorial at the SIGAda conference
DO 178C Tutorial