Ten Principles for Building Safe Embedded Software Systems

Obtaining safety certifications and pre-market approvals for safety-related systems is arduous, costly, and prone to failure. And yet such certifications and approvals are integral to the sale and market acceptance of software for a wide range of products. For example, software for a medical device must obtain FDA Class III pre-market approval (IEC 62304), a train control system must meet requirements set out in EN 50126 and EN 50657, automotive system components must meet differing ISO 26262 safety integrity levels depending on functionality, and an industrial automation system is required to be IEC 61508 SIL-rated.

Download this whitepaper to learn how a safety culture is not only a culture in which engineers are permitted to raise safety questions, but a culture in which they are encouraged by company leaders to do so.

Ready to view and download this whitepaper?

    What are your top concerns/ criteria when implementing a commercial embedded operating system? *

    What operating system or hypervisor have you been using for your current or past projects? (select all that apply) *

    By downloading this content, you give your express consent to be contacted (by phone or email) by a representative from BlackBerry in regards to the content.
    Privacy Policy.*