Channels ▼


Cross Discipline Collaboration For Hybrid Design Featuring Rhapsody and Simulink

Cross Discipline Collaboration For Hybrid Design Featuring Rhapsody and Simulink

Date: Thursday, March 15, 2012
Time: 11:00 AM PT / 2:00 PM ET
Duration: 60 minutes

[click here to register]

Presented By
A Dr. Dobb's Webcast


Embedded device development often requires diverse teams from different disciplines such as architectural design, closed loop control design, or signal processing to bring together their parallel development tasks to produce an integrated working design. Design information is often shared using manual paper based methods and tedious manual review processes which slows development and inhibits the ability to properly integrate designs and ensure the right product is built. Rational solutions for collaborative design, built on the Jazz platform, enable diverse teams to collaborate, share, review, analyze and trace designs built in IBM Rational Rhapsody and The Mathworks Simulink. Teams gain understanding of the designs from across the larger team and can contribute their points of view into these designs. More, Rhapsody and Simulink elements can be linked to other design elements or development lifecycle artifacts, such as requirements or test cases, leading to greater visibility of the relationships they have and how the designs will be impacted by any change. Learn how IBM is enabling teams to link designs from these powerful development environments and allowing designers and other project stakeholders to collaborate more fully on embedded systems design.

Register now.

Featured Speakers:

Justin Dyer:  — Systems Solutions Architect, 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.