Ron, "S. Ron Oliver" wrote: > Do any of you have any experience with these certification processes? > > I have not, but I may have a need to come up to speed on them. I would > appreciate any information you can pass along. > We at Aonix have certifiable RTSs (e.g. certify them) for both Ada83 and Ada95. A brief overview of the FAA safety critical standard follows: The FAA's DO-178B is heavily process oriented in specifying that the development group clearly define all their development processes. It can not be exact since the standard does not know what type of system is being developed for each case. It is explicit in some testing areas and required development artifacts though. This is typically delivering all: requirements specs., high level design, detailed design, source code, text cases, and test results. Traceability across all artifacts is required. For testing the development organization must show 100% coverage. This is at the source code level for Level B and lower and typically at the machine level for Level A. Note that because of the traceability requirements, the test cases must be traceable back to the requirements. Thus quite often holes in coverage point back to missing or vague requirements. Thus to get full coverage it is common to have to repeat testing and refine the requirements, design, etc. to get to 100%. In both source and machine level coverage no dead code is allowed (this is implicit in the 100% coverage). Some special cases can exist where there is a very small amount of code without coverage and these can be designated as deactivated code, but now we are getting into low level particulars of the standard. I hope this helps. Copies of the standard can be purchased through RTCA.