DO-178B includes tool qualification as "additional consideration". Clearly there is a problem.
Once it is deteremined that a development tool or the verification tool requires qualification, the tool qualification should be done prior to its use. And since this determination is done at the planning stage, this activity should be moved from section 12 of the DO-178B (dealing with Additional Consideration) to Chapter 11 (Software Life Cycle Data).
Tool Qualification data should be made an integral part of Software Life Cycle data.

Development tools are really helpful its true and are getting upgrade day by day
Posted by: Best Dissertation Writing Services | January 24, 2012 at 05:49 PM
I wanted to write a quick note to express my thanks. I'm really impressed by a blog unique and perfectly chosen and organized!
Posted by: Smart Home | November 10, 2011 at 12:37 PM
Yes, I agree with you regarding the tool qualification activities. This issue will be resolved once the DO-178C is released. DO-178C has an additional supplement for the Tool qualification activities, where in it elaborates more on the tool qualification processes.
Posted by: Koteswara | October 01, 2010 at 11:02 PM
There have been numerous instances of development tool qualification - and it is as suggested very expensive. For example, automatic code generators have been qualified as development tools as the applicant is depending upon the output of the code generator - and wishes to do so for the tool being used in the same manner on a number of projects (thereby spreading the cost).
Posted by: RMH | September 17, 2010 at 03:12 PM
@Pradeep, I have never come across a single instance of a need to qualify development tool till date.
There could be 3 reasons:
a) I have not done enough projects
b) It must be prohibitively expensive to qualify a development tool
c) Carrying out verification as detailed by DO-178B chapter 6 must be cheaper than qualifying a development tool.
Posted by: Amitabh | September 17, 2010 at 09:29 AM
@Amitabh. How difficult is the qualification of development tool when compared to the qualification of verification tool?
Posted by: Pradeep | September 17, 2010 at 08:53 AM
Section 11 simply deals with Life Cycle Data - so perhaps there is a case to move the contents of Section 12.2.3.1 and Section 12.2.3.2 to Section 11. However, this was not done so as to keep everything related to tool qualification together. For the future, Tool Qualification as related to DO-178C will pe provided as a separate document entirely.
Posted by: RMH | September 17, 2010 at 12:11 AM
@ bharathi : Tool Qualification Data of S/w development tools to be controlled as CC1 whereas for s/w verification tools it is CC2
Posted by: Pradeep | September 16, 2010 at 06:42 PM
As per DO-178B para 12.2.3.b, "The tool qualification data should be controlled as Control Categorisation 1 (CC1) for software development tools and CC2 for software verification tools."
Posted by: Amitabh | September 16, 2010 at 01:50 PM
very simply explained. It is indeed an art to read & stop new visitors with your attractive writing style. I am really impress from your posted information. Thanks for sharing.
Posted by: How to be an alpha male | September 16, 2010 at 11:40 AM
Is Tool Qualification data comes under CC1 or CC2??
Posted by: Bharathi Raja | September 16, 2010 at 10:43 AM