Difference between revisions of "DO-178B and DO-178C"

From T-VEC Wiki
Jump to: navigation, search
(Common Questions)
(DO-178C)
Line 50: Line 50:
 
===DO-178C===
 
===DO-178C===
  
SC-205 is the official designation in the US of the RTCA subcommittee dedicated to updating DO-178B - SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION. This is the primary document on which the FAA certification of all commercial software-based aerospace systems is based. DO-178B was released in 1992 and is mirrored in Europe by ED-12B, the same document but with a European designation. SC-205 is responsible for revising DO-178B/ED-12B to bring it up do date with respect to current software development and verification technologies. The new document will be called DO-178C/ED-12C and is due to be finalized during 2008.
+
SC-205 is the official designation in the US of the RTCA subcommittee dedicated to updating DO-178B - SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION. This is the primary document on which the FAA certification of all commercial software-based aerospace systems is based. DO-178B was released in 1992 and is mirrored in Europe by ED-12B, the same document but with a European designation. SC-205 is responsible for revising DO-178B/ED-12B to bring it up do date with respect to current software development and verification technologies. The new document will be called DO-178C/ED-12C and is due to be finalized during 2010.
  
 
The committee work is divided into 7 Subgroups:
 
The committee work is divided into 7 Subgroups:
Line 77: Line 77:
 
* What is source code in the context of automatic code generators?
 
* What is source code in the context of automatic code generators?
 
* Can coverage of a model’s logical paths during simulation of a model in the modeling environment be granted credit for MCDC structural coverage in the presence of a qualified (read “perfect”) auto-code generator?
 
* Can coverage of a model’s logical paths during simulation of a model in the modeling environment be granted credit for MCDC structural coverage in the presence of a qualified (read “perfect”) auto-code generator?
* What are high level vs. low level vs. derived requirements and should design models such as Simulink/MatrixX/SCADE be considered low level requirements  
+
* What are high level vs. low level vs. derived requirements and should design models such as Simulink/MatrixX/SCADE be considered low level requirements
  
 
===RTOS in Certification===
 
===RTOS in Certification===

Revision as of 12:52, 9 July 2009