Search Results

With the inception of model-based design and automatic code generation, many organizations are developing controls and diagnostics algorithms in model-based development tools to meet customer and regulatory requirements. Advances in model-based design have made it easier to generate C code from models and help software engineers streamline their workflow. Typically, after the software has been developed, the models are handed over to a calibration team responsible for calibrating the features to meet specified customer and regulatory requirements. However, once the models are handed over to the calibration team, the calibration engineers are unaware of how to calibrate the features because documentation is not available. Typically, model documentation trails behind the software process because it is created manually, most of this time is spent on formatting. As a result, lack of model documentation or up-to date documentation causes a lot of pain for OEM’s and Tier 1 suppliers.

In this paper, we review existing software safety standards, guidelines, and other software safety documents. Common software safety elements from these documents are identified. We then describe an adaptable software safety process for automotive safety-critical systems based on these common elements. The process specifies high-level requirements and recommended methods for satisfying the requirements. In addition, we describe how the proposed process may be integrated into a proposed system safety process, and how it may be integrated with an existing software development process.