Adam Trujillo, Parasoft
It’s well understood that electronic systems in automobiles are not only becoming more complex, but they’re also becoming broader in terms of scope. Integrating over-the-air connectivity, such as cellular, Bluetooth, and Wi-Fi, enhance the user experience, and can extend control-by-wire systems. This is in addition to the several USB ports already found in the auto [...]
ISO 26262, MISRA, and other standards seek to normalize software development for automotive applications by providing a foundation for implementing engineering concepts in software development processes. Some organizations view compliance with ISO 26262 and other standards as an overhead-boosting burden, but the truth is that the cost of failure associated with software defects is much, [...]
Static analysis is a development testing activity with the potential to go far beyond simply checking code. When used as part of a policy-driven defect prevention strategy, static analysis can drive a software engineering team's productivity and minimize fiscal, legal, and ethical risks associated with potentially faulty code. The reason more organizations do not realize the benefits of static analysis, however, is that it's often homogeneously deployed as a tool for "finding bugs." But the truth is that there are different implementations of static analysis that serve different purposes in the development process. And while it's a foregone conclusion that software engineers should run static code analysis, the proper implementation of the right technologies is the difference between wasting time and money and reaching new software development heights.