Ten Principles for Building Safe Embedded Software Systems
Get the Whitepaper
Download Now
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.
Safety must be embedded in the practices, processes, and culture of every organization building safety-critical systems. If safety-critical products are to succeed, manufacturers must look beyond strictly technical challenges to embrace the following principles for building and certifying safety-critical software systems.
A product development culture focused on safety can’t guarantee that the software will meet its dependability requirements, nor is it certain the system will receive the necessary safety certifications or pre-market approvals.
Download the Whitepaper Now
→
close X
Cookies are required to access some content on our site. Please check your browser's cookie settings and reload the page to try again.
Thank you for your interest.
What are your top concerns/ criteria when implementing a commercial embedded operating system?
Please Select
Security capabilities/functionality
Real-time capabilities/performance
Safety / security certification
Overall cost
None of the above
What operating system or hypervisor have you been using for your current or past projects?
BlackBerry QNX
Linux (open source)
Wind River
Green Hills
Other (please specify)
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.