Aerospace International: Squashing the Bugs

Aerospace International: Squashing the Bugs

on Oct 12, 09 • by Lynn Gayowski • with No Comments

The traditional way to check software code has been for the code to be checked-in, then bugs found through testing, then debugged, before the cycle begins again. Not only is this extremely time-consuming and expensive but it also throws up the problem of other mistakes being inserted at the checking stage. However,...

Home » Industry Articles » Aerospace International: Squashing the Bugs

The traditional way to check software code has been for the code to be checked-in, then bugs found through testing, then debugged, before the cycle begins again. Not only is this extremely time-consuming and expensive but it also throws up the problem of other mistakes being inserted at the checking stage.

However, source code analysis experts such as Klocwork have developed automated software development integrity tools that can automate the identification and assessment of software architecture flaws before the code is checked in, allowing programmers to submit bug-free code.

As well as increased safety, another benefit in using this method of source code analysis is in expense and time. It is far cheaper and takes less time to fix problems before the software is compiled, than to compile, than test, then hunt for the bugs and errors at a later stage. Klocwork’s chief technology officer, Gwyn Fisher, for example, notes that automated source code analyis can be “two orders of magnitude faster” than traditional methods.

Read More

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Scroll to top