This page is being built to provide you with links to resources that provide more insight into government regulations, software safety issues and legal perspectives. This site is under construction and more information will be provided as the site is built out.
Legal & (Other) Perspectives of Software Glitches
Tracking and Hacking Report – by U.S. Senator Ed Markey. This report highlights the urgent need to regulate how car companies gather and share private information about drivers as well as the need to build more secure car software to prevent hackers from taking control of other people’s vehicles.
A Survey of Remote Automotive Attack Services (2014) – This report is provided by two hackers who believe it’s very important for the public to understand what’s going on. They point out that they offer Consumer Protection information to help you decide which vehicles appear to be the safest based on their software design and functioning. This report also provides excellent insight into the overall problem.
Lists of Recalls
CNN has provided a list of all GM recalls. While some of the recalls are not software-related, it is impressive to know that in 2 years (2013 and 2014), GM has recalled more cars than it has made in the last 5 years.
Government of Canada provides a database for people to search and see which vehicles, models and years have had recalls issued, and for what. It is a very helpful tool.
IEEE lists “9 Notorious Automotive Electronics Recalls”. Allison Dorantes-Garcia, writing in The IEEE Times, provides a quick summary of some significant recalls due to faulty electronics that can start fires in the exhaust, cause airbags to malfunction, make the steering wheel unresponsive to driver input, trigger sudden unintended acceleration.
Legal & Other Perspectives
Legal Firm that Brought GM’s Ignition Switch Issues to Light – Lance Cooper represented the parents of Brooke Melton who died as a result of the GM ignition switch issue.
The Emerging Risks Associated with Keyless Push Button Ignitions on Automobiles – Kreindler & Kreindler (USA). Note that Kreidler & Kreidler do not claim that keyless fobs are not riddled with software glitches, but that the introduction of this “convenience” technology has led to deaths.
Toyota’s Software Problems – Why NASA couldn’t find the “bug” and why Michael Barr did — This presentation was put together by Prof. Philip Koopman of Carnegie Mellon University.
External and internal electromagnetic signals trigger unintended acceleration — This information is listed on a law firm’s website.
Software Coding Guidelines
There are a number of coding guidelines and associations throughout the world. None of them are regulatory agencies. Following sound (and safe) software development practices is optional.
SEI – Software Engineering Institute.
ISO 26262 – As ISO indicates on its website, “ISO (International Organization for Standardization) is an independent, non-governmental membership organization and the world’s largest developer of voluntary International Standards.”
MISRA – The Motor Industry Software Reliability Association is an organization based in the UK that works on behalf of the automobile industry. It’s members are automobile companies. Membership is not mandatory.
Government Warnings & Notifications
FCC 7 State “Sunny Day” 911 Outage – This report by the U.S. regulatory agency, the FCC, examined what led to the “simple software error” that prevented 11 million people from being able to access 911 for six hours in April 2014. The FCC has indicated that 911 outages are becoming more frequent.
U.S. FDA Medical Device Recall Report – This report points out that one of the most frequent causes for recalls is software and that if “industry and CDRH can address these problems jointly, we may be able to prevent as many as 400 recalls each year.” Preventing recalls saves lives.
Health Canada Medical Device Software – In 2010, Health Canada – a governmental body – issued a report stating that software that is “intended or represented for use in the diagnosis or treatment of an abnormal physical state of a patient meets the definition of a medical device . . .”. This is an excellent start to the process of regulating software. But the problem with Health Canada’s approach is that it regulates any software issues “after the fact.” once the damage has been done (person injured and/or dies).