SoftwareSafetyStandardsandGuidelines.docxVIP

Software Safety Standards and Guidelines (Herrmann, §3.2) 1 CS 3090: Safety Critical Programming in C MISRA Development Guidelines CS 3090: Safety Critical Programming in C 2 MISRA: Motor Industry Software Reliability Association Guidelines for activities across the entire software process: Project planning Integrity Requirements specification Design Programming Testing Product support Built on top of ISO 9001 (international standard for quality management), with extra rules for ensuring safety – beyond ordinary “quality” Software vs. other automotive components CS 3090: Safety Critical Programming in C 3 Software is primarily a design, with no manufacturing variation, wear, corrosion or ageing aspects. It has a much greater capacity to contain complexity. It is perceived to be easy to change. Software errors are systematic, not random. It is intangible. Automotive applications vs. applications in other industrial sectors CS 3090: Safety Critical Programming in C 4 High production volumes – Components subject to wear – Difficult to ensure regular maintenance Therefore automotive software has an emphasis on data driven algorithms The code processes data in continuous streams Code should be flexible, able to handle a variety of data Avoid specialized code for each data type parameter optimization Find the “right” combination of inputs to maximize/minimize output adaptive control Control laws are not fixed; rather, they adapt to changes over time (e.g. fuel levels) and sudden events (e.g. change in road surface) on-board diagnostics Automotive applications vs. applications in other industrial sectors CS 3090: Safety Critical Programming in C 5 Passenger car drivers receive little or no training compared with other users of computer-based products and services. Therefore, automotive software requires an emphasis on failure management techniques based on the controllability of the vehicle. Automotive applications vs. applications in other industrial sectors CS 3090: Safe