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.

Work email *

First Name *

Last Name *

Job Title *

Company Name *

Phone *

Address Line 1 *

City *

Zip/Postcode *

Country *

Industry *

Company Size *

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

By requesting this resource you agree to our terms of use. All data is protected by our Privacy Notice.

By submitting this form, you are confirming you are an adult of 18 years or older and you agree to BlackBerry contacting you with marketing-related emails or by telephone. You may unsubscribe at any time. BlackBerry websites and communications are subject to their Privacy Notice.

Please agree to the conditions