Channels ▼


Evolution of Automotive System Requirements - The Increased Need for Collaborative Design Management

Evolution of Automotive System Requirements — The Increased Need for Collaborative Design Management

Date: Tuesday, November 15, 2011
Time: 11:00 AM PT / 2:00 PM ET
Duration: One Hour

[click here to register]

Presented By
A Dr. Dobb's Webcast


In recent years, automotive systems have grown increasingly complex as electronic control units define a greater percentage of vehicle functionality and end-product differentiation. To maintain schedule adherence and satisfy complex development requirements, engineering organizations are increasingly turning toward software and system lifecycle management solutions as a means of promoting efficiencies and synergies in their development process.

The complexity and rising popularity of standards, such as AUTOSAR and GENIVI are driving more automotive system manufacturers to improve their current development processes. One way organizations are attempting this is through the use of commercial modeling tools that promote the modularity, traceability, and reusability of the assets under development. Engineering organizations will need to evaluate additional products and methodologies that enable collaboration between engineering groups, manage levels of abstraction, and support any development efficiencies. This webinar discusses how these tools deliver enhanced collaboration to automotive engineering teams.

Register now.

Featured Speaker:

Christopher Rommel:  — Vice President, Embedded Software & Hardware, VDC Research

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.