Design Article
Tell us What You Think
We want to know what you thought about this Design. Let us know by adding a comment.
Demonstrate ISO 26262 conformance
Guido Sandmann, MathWorks
5/3/2012 3:00 AM EDT
Getting up to speed on ISO 26262
Do you have any tips for automotive engineers looking to get educated on this standard, so they can identify gaps in current design processes?
A very good starting point is the standard relevant landing page for ISO 26262 within the MathWorks web pages. Here engineers find papers which MathWorks experts (some together with customers from the automotive industry) have written in order to explain verification and validation workflows or support for tool qualification in accordance to the ISO 26262 standard. Here also engineers learn about MathWorks products and services fit into the solution portfolio regarding the standard.
As introduced in the beginning, MathWorks is a tool provider for technical computing and Model-Based Design. Because the underlying technology and use cases mainly cover Part 6 and to some extent Part 8 of the standard, MathWorks works closely together with third party vendors to close the existing gaps. For example, IKK++ technologies is a MathWorks partner that provides a tool (medini analyze) and services that help managing artifacts and process steps across the whole safety analysis for high-integrity applications.
Where does Model-Based Design fit in? Can you please outline the best way to develop a roadmap to an optimized process framework using Model-Based Design?
Model-Based Design is a popular automotive industry development paradigm that improves efficiency and quality of development processes for electronic embedded systems. It enables engineers to create executable specification models that can be simulated and tested to help find errors during early development phases.
Further down the V-cycle, Model-Based Design supports detailed design, implementation through production code generation, and related verification and validation activities including rapid prototyping and processor-in-the-loop code verification. The reference workflow (see below) reflects the left arm of a V-cycle and illustrates the verification and validation tasks necessary for an ISO 26262 compliant approach. MathWorks provides an integrated tool chain for each of these steps and activities.
For example, Part 6 in the ISO standard addresses “Product development at the software level”, which is the area that MathWorks tools are heavily used. The standard specifically calls out Model-Based Design as one way to develop high integrity application software. This means that Model-Based Design and ISO 26262 complement each other in a way that both approaches aim for high quality development processes for electronic embedded systems.
Thus such use of available software tools and techniques enables engineers to ensure ISO 26262 process and tool compliance.
Guido Sandmann is automotive marketing manager for Europe at MathWorks.
Do you have any tips for automotive engineers looking to get educated on this standard, so they can identify gaps in current design processes?
A very good starting point is the standard relevant landing page for ISO 26262 within the MathWorks web pages. Here engineers find papers which MathWorks experts (some together with customers from the automotive industry) have written in order to explain verification and validation workflows or support for tool qualification in accordance to the ISO 26262 standard. Here also engineers learn about MathWorks products and services fit into the solution portfolio regarding the standard.
As introduced in the beginning, MathWorks is a tool provider for technical computing and Model-Based Design. Because the underlying technology and use cases mainly cover Part 6 and to some extent Part 8 of the standard, MathWorks works closely together with third party vendors to close the existing gaps. For example, IKK++ technologies is a MathWorks partner that provides a tool (medini analyze) and services that help managing artifacts and process steps across the whole safety analysis for high-integrity applications.
Where does Model-Based Design fit in? Can you please outline the best way to develop a roadmap to an optimized process framework using Model-Based Design?
Model-Based Design is a popular automotive industry development paradigm that improves efficiency and quality of development processes for electronic embedded systems. It enables engineers to create executable specification models that can be simulated and tested to help find errors during early development phases.
Further down the V-cycle, Model-Based Design supports detailed design, implementation through production code generation, and related verification and validation activities including rapid prototyping and processor-in-the-loop code verification. The reference workflow (see below) reflects the left arm of a V-cycle and illustrates the verification and validation tasks necessary for an ISO 26262 compliant approach. MathWorks provides an integrated tool chain for each of these steps and activities.
For example, Part 6 in the ISO standard addresses “Product development at the software level”, which is the area that MathWorks tools are heavily used. The standard specifically calls out Model-Based Design as one way to develop high integrity application software. This means that Model-Based Design and ISO 26262 complement each other in a way that both approaches aim for high quality development processes for electronic embedded systems.
Thus such use of available software tools and techniques enables engineers to ensure ISO 26262 process and tool compliance.
Guido Sandmann is automotive marketing manager for Europe at MathWorks.____________________
If you liked this article, go to the Automotive Designline home page for the latest in automotive electronics design, technology, trends, products, and news. Also, get a weekly highlights update delivered directly to your inbox by signing up for our weekly automotive electronics newsletter here. |
|
|
|
|
Navigate to related information