DO-178B documents?
DO-178B documents?
What is DO-178B/ED-12B? The purpose of this document is to provide guidelines for the production of software for airborne systems and equipment that performs its intended function with a level of confidence in safety that complies with airworthiness requirements.
Do data items parameters 178C?
PARAMETER DATA ITEM (PDI) DO-178C has addressed some general topics that resulted in changes to several section of the document. One such general topic is Parameter Data Item (PDI). A Parameter Data Item File is an instantiation of the parameter data item containing defined values for each data element.
DO-178B Level A coverage?
The different DO-178B-levels are defined according to the possible consequences of a software error: Catastrophic (level A), hazardous-severe (level B), major (level C), minor (level D) or no-effect (level E).
What is the DO-178B document?
The document outlines the guidelines used by organizations developing airborne equipment and certification authorities, such as FAA, EASA, and Transport Canada. The development of DO-178B was a joint effort of RTCA and EUROCAE who publis hed the document as ED-12B.
Are consunova’s process templates and checklists DO-254 and DO-178C compliant?
ConsuNova’s comprehensive set of Process Templates and Checklists are fully compliant with DO-178C and DO-254. ConsuNova DO-178 and DO-254 Templates and Checklists that have been reviewed and deployed successfully on projects under FAA, EASA and Military compliance authorities.
What is the difference between do254 and DO178B?
DO-254 provides certification information from project conception, planning, design, implementation, testing, and validation, including DO-254 Tool Qualification considerations. DO-254 and DO-178B are actually quite similar, with both having major contributions via personnel with formal software process expertise.
What are the software verification requirements for DO-178C?
One of the key requirements in the software verification process of DO -178C is achieving structural code coverage in conjunction with the testing of the high- level and low -level software requirements. Based on a system safety assessment, failure condition categories are established.
