Channels ▼
RSS

Tools

Evolving Your Current Processes and Infrastructure to Fulfill the Requirements of ISO 26262


Evolving Your Current Processes and Infrastructure to Fulfill the Requirements of ISO 26262

Date: Tuesday, March 20, 2012
Time: 9:00 AM PT / 12:00 PM ET
Duration: 60 minutes

[click here to register]

Presented By
A Dr. Dobb's Webcast

Overview

As companies review their existing processes and tool infrastructure as to their suitability to help fulfill the requirements of ISO 26262 many questions arise. These include, "What changes are needed in our organization such as new roles and departments?","What changes to processes and artifacts need to be done?", and "How do I evolve my current tool environment to support these changes?". The planning, coordination and documentation of the activities for all phases of the safety lifecycle is a key management task. Being able to efficiently and effectively do safety critical development will be critical to compete in todays market.

The topics of this webcast will include describing a requirements driven process, lifecycle traceability, how to effectively manage product development in the context of ISO 26262. The webinar will also describe how the IBM Rational's solution for Automotive can help organizations comply with the requirements in ISO 26262 by managing the activities and artifacts throughout the safety lifecycle. The focus will be on integrating new practices into your existing processes in an evolutionary, not revolutionary, manner to help achieve compliance in a cost effective manner.

Register now.

Featured Speakers:

Dr. Graham Bleakley:  — Solution Architect, IBM
Karla Ducharme:  — Market Manager, Automotive and Aerospace & Defense, IBM Rational


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video