Webinars

Developing safety critical software is difficult enough, but more and more often, developers are also now challenged with the task of developing the software so that it complies to industry standards such as DO-178B/C, IEC 61508, IEC 62304, ISO 26262 or even a company’s own internal standard. This is good news for the end users of the software, but what does it mean for the developers and how can they go about achieving this?

Many of these previously mentioned standards specify a number of ‘objectives’ or ‘requirements’ that need to be met. We will discuss these objectives and look at various ways in which they can be implemented and documented as well as also highlighting the processes, procedures and tools used to achieve critical software certification.

Using practical examples, we remove the mystery and confusion surrounding development, verification, configuration management and quality assurance. We pay special attention to requirements traceability, coding standards adherence, independence criteria, testing and structural coverage analysis. Finally, we discuss how these can assist in the next generation of certification.