What MISRA, ISO 26262, and AUTOSAR mean for automotive software development and how static code analysis helps
Read More »
Details on the ISO 26262/IEC 61508 certification for the Klocwork 2016 release
Read More »
Discussing information you can use and what we learned from our audience during the "Three ways to ensure your automotive developers deliver secure, compliant, defect-free software" webinar
Read More »
Avoiding hacks, wrecks, and recalls is the job of every automotive software development team out there … yet few know how to do it. Organizations are under increasing pressure to deliver code that’s compliant to standards, protected from security threats, and free of defects that could result in expensive recalls or loss of consumer trust. To keep pace, traditional testing methods are falling by the wayside in favor of leaner, more effective techniques that get your software verified and validated faster. Join us on Tuesday, September 30th for our “How to reduce automotive software development
Read More »
Last week, we held a joint webinar with QNX Software Systems discussing how static analysis plays a key role in automotive functional safety and ISO 26262 (you can watch the recording here). We had developers, testers, architects, and students attend from all over the world and they all had one interest in common: better delivery of safe automotive software. We always try to understand our attendees and here’s an interesting result from one of the polls we ran (based on table 9 of ISO 26262-6, which lists methods of design verification for software units): Which
Read More »Previously I posted the value of using coding standards, specifically MISRA C and MISRA C++. This time I wanted to go through some general experiences we had with some of the checkers, specifically the ones that seem to throw a lot of violated rules, to the point that on some code bases MISRA flagged more than one error per LOC! There are still tons of great rules you can apply even if you don’t make an embedded product. But as I said before, it doesn’t make sense to turn on all the MISRA rules. After
Read More »What is MISRA? More Irrelevant Software Requirements Again…uh no but certainly the sentiment of many developers. MISRA (Motor Industry Software Reliability Association) is a coding standard, which first released MISRA C in 1998 and has since been revised. Obviously, this came out of the automotive sector with a clear focus on helping software systems to be more reliable and maintainable. MISRA has since grown. Now you see more and more industries adopting these standards. In 2008, MISRA released the C++ equivalent standard. So the obvious question is, should I apply this to my software source
Read More »Today, I had a chance to connect with Connie Beane, the Director of Certification and Safety Critical Software for ENEA Embedded Technology, Inc. Connie has a deep background in safety-critical avionics systems development as a Federal Aviation Administration Designated Engineering Representative (DER) with authority for design assurance level A systems, software and complex electronic hardware. Her additional experience includes 12 years with the FAA in the Transport Airplane Directorate as a Project Officer, Federal representative and Secretary of the RTCA committee SC-180, which produced DO-254, as well as 8 years at Boeing as a Lead
Read More »
CVE-2019-5736 was published on February 12. It covers the runc container for Kubernetes. There is a broken function in how the containers are run with how a corrupt user...
Getting buy-in from team members is a critical step in the OSS adoption process. So allowing them to see first hand the benefits is a great first step. ...
Application security is an important topic, but often not part of the formal training path for software professionals...
