Engineers and software developers sometimes fall into an either/or mindset, as we all do from time to time, in which there are only two possible outcomes: your solution or the other person’s – and the other person’s is the wrong one. But in the diverse domain of software code analysis and test, the answer to the
question of the right approach to ensuring code quality may be a multiple choice one, not just a choice between static analysis and dynamic testing.
My Editor’s Top Picks for this week’s Tech Focus newsletter illuminate this issue:
If after you have evaluated these various methods you still can’t determine the best approach for your particular application, be sure to register and attend the 2011 Spring ESC, May 2-5. Several class tracks offer possible answers: Best Practices, Debugging and optimizing, Design and test, Multicore debug, Languages and techniques and Software processes and tools.
Since the goal of Agile development is to have working software early, source code analysis enables developers to analyze the quality and security of code from day one of coding ” one of the earliest points in the software development process
Coding rules and static analysis tools are most effective when they work together, automating much of the work of checking compliance with rules, freeing up time to focus on higher-level concerns such as algorithm design.
Matthew Hayward gives you the lowdown behind one of the most frequency misunderstood aspects of static analysis: that it is distinctly different from other bug finding techniques.
Researchers at the FDA's Office of Science and Engineering Laboratories investigating new techniques for analyzing software in medical devices are using static analysis tools to uncover potential flaws in a device under review.
Source code analysis consultant Andrew Yang outlines some of the hard lessons learned by working with a number of companies instituting SCA tools, the problems encountered and how to avoid them.
This two part article covers the basics of testing and test case development and points out details unique to embedded systems work along the way. Part1: Basics of embedded software testing.
Extending the use of code coverage with mutation-based testing techniques to measure and drive improvement in all aspects of functional verification quality for simulation-based environments.
The programming specialists from PolySpace provide a brief tutorial on the basics of semantic analysis, and how it can be used to eliminate a variety of software errors.
Techniques for reducing the risk of bugs in software for safety-critical systems can work to reduce bugs in non-safety-critical systems. Advanced static-analysis tools can help by finding real errors automatically and reducing testing costs.
Green Hills Software, Inc., is now providing its user-based static code analyzer, DoubleCheck as a standard feature with its MULTI Professional tool suite for multicore development and debugger solutions. The integration is intended to increase developer productivity and code quality while enabling better management and control of code complexity and the overall coding process.
Coverity Inc. says the new release of its Prevent static code-analysis software embodies a new approach to “software mapping” that finds more bugs in embedded and enterprise software than previous technologies. The Prevent Software Quality System (SQS) also includes new defect- tracking capabilities and Java support.
EMA Design Automation announced TimingDesigner 9.25 with enhanced Automerge functionality, which the company claims, dramatically decreases the time required for performing interface timing analysis.
Embedded software engineers using a static analysis tool are working on projects with significantly larger average numbers of in-house developed lines of software code than developers not using a static analysis tools according to research by VDC Research.
Static source code analyzers attempt to find code sequences that, when executed, could result in buffer overflows, resource leaks or many other security and reliability problems. Source code analyzers are effective at locating a class of flaws that are not detected by compilers during standard builds and that often go undetected during run-time testing as well. Recently, Green Hills Software's source code analyzer was used to find flaws in several open-source applications that are widely used in Internet communications.
LDRA and Netrino have partnered to implement the Embedded C Coding Standard for the LDRA tool suite. Support of the Netrino Embedded C Coding standard extends LDRA's already comprehensive list of C/C++ language standards such as MISRA-C:1998 and MISRA-C:2004, CERT C, SEC C
You must verify your email address before signing in. Check your email for your verification email, or enter your email address in the form below to resend the email.
Please confirm the information below before signing in.
{* #socialRegistrationForm *}
{* firstName *}
{* lastName *}
{* displayName *}
{* emailAddress *}
By clicking "Sign In", you confirm that you accept our terms of service and have read and understand privacy policy.
{* /socialRegistrationForm *}
Almost Done
Please confirm the information below before signing in. Already have an account? Sign In.
