Functional safety, as defined basically in IEC 61508 and in ISO 26262 for automotive systems, clearly describes actions to take and methods to use to develop a safe system. "Safe" actually can include the presence of faults and bugs. This implies the detection of malfunctions and taking proper actions before any harm is done. So it's all about timing: Before a hazard occurs, the system has to put itself, in time, into a safe state involving automated mechanisms and the driver.
Precisely defining the safety requirements, including time intervals the system has to respond to faults, is mandatory. And it is crucial for project success to evaluate early in the development process if these requirements are met.
This article introduces the reader to the timing aspects of functional safety. A model-based methodology based on a matured tool suite will be described to help design embedded systems having the correct dynamic behavior and robustness to changes and unexpected system states.
For the complete article, including five steps to functional safety (with design of a seat position memory system as an example), click here, courtesy of Automotive Designline Europe.
A good step by step breakdown of the process while not getting bogged down in technical details. The approach seems workable but the hard parts are the actual implementation. Thanks for a well written article!
This is interesting, and the example of hazardous failure of the power seat points out the large number of hazards provided by the convenience functions added to the vehicle. Even more important is the linking of the concerns to the fact that the primary parameter is profit, with all others, including safety, a distant second in importance.
This is an eye-opening article, indeed.
Join our online Radio Show on Friday 11th July starting at 2:00pm Eastern, when EETimes editor of all things fun and interesting, Max Maxfield, and embedded systems expert, Jack Ganssle, will debate as to just what is, and is not, and embedded system.