The functional safety standard, ISO 26262 adds more requirements to the product lifecycle for automotive hardware-software systems. This functional safety standard acts as a framework impacting integrated requirements traceability, risk management, validation, verification, documentation, and collaboration throughout the systems engineering “V” model lifecycle process.
This paper examines the impact of the standard on both the development process and support tool chains for automotive electronics, and what it means for modern automotive developers. Among other things, we’ll cover:
Recent updates to ISO 26262
Leveraging LHP Engineering Software to streamline compliance
Ensuring that software tools and tool chains are suitable for safety-intense systems
Aligning to best practices
Testing the Requirements
You can’t always visualize how a system will run just by reading requirements. That’s why early testing of ...
A Path to Model-Based Systems Engineering (MBSE) with Jama Connect
In this paper, we discuss how to leverage Jama Connect for MBSE to enable cross-discipline collaboration an...