WP_Term Object
    [term_id] => 70
    [name] => Dassault Systemes
    [slug] => dassault-systemes
    [term_group] => 0
    [term_taxonomy_id] => 70
    [taxonomy] => category
    [description] => 
    [parent] => 157
    [count] => 44
    [filter] => raw
    [cat_ID] => 70
    [category_count] => 44
    [category_description] => 
    [cat_name] => Dassault Systemes
    [category_nicename] => dassault-systemes
    [category_parent] => 157

Talking Directly to EDA R&D

Talking Directly to EDA R&D
by Daniel Payne on 08-02-2015 at 12:00 pm

Many EDA companies keep their R&D engineers focused on product development and bug fixing, shielding them from any and all direct contact with end-users, mostly for fear of what might be revealed if such direct dialog were allowed. Customer support people are allowed to talk directly with customers, then pass along enhancement requests or file bug reports to R&D. Another way is for product marketing and technical marketing folks to talk with EDA users and uncover new product requirements, then report to R&D what they’ve heard about possible roadmap features. Direct conversations between EDA tool users and EDA R&D engineers is kind of rare, however it can be quite beneficial to both parties as there is no intermediate filtering of ideas, design challenges, likes and dislikes.

I was actually kind of surprised to learn that Dassault Systemes is having a two day user meeting in September and October where the second day is fully dedicated to EDA users talking directly with EDA R&D engineers to actually share their user experience, have roundtable discussions, discuss product roadmaps, describe how they actually use the tools, and explain what they really want to see in the next release of software. This kind of direct interaction between users and developers is a wonderful approach that keeps a company like Dassault in tune with what’s really happening, and able to plan and respond accordingly.

Related – A Systems Company Update from #52DAC


As a quick recap, Dassault has introduced the Silicon Thinking Experience which offers four solution areas for SoC design teams that provide a business platform allowing Design, Product and Manufacturing engineering to work together:

  • Design Collaboration using DesignSync and Pinpoint
  • Requirements driven verification
  • Enterprise-level IP management
  • Manufacturing Collaboration

DesignSync has been used since 1998 to help SoC teams manage both the hardware and software content in their electronic products. Designers can share their hierarchical design to all team members, even across the globe during their collaboration of design and verification.

The Pinpoint tool came from Tuscany Design Automation, and was acquired by Dassault in late 2012, it provides a dashboard with info for both the front-end and back-end IC design flows, helping you to reach design closure quicker.

Knowing if your system design implementation actually meets the original requirements is important for success, so having a methodology that supports requirements driven verification is essential. Ad-hoc verification just isn’t sufficient for a complex electronic product today.

How you manage the hundreds of IP blocks on a single SoC can be a critical success factor, so using a proven system will help reduce risks, enable IP reuse, eliminate duplication of IP and track issues and defects through multiple projects.

Related – Design Collaboration, Requirements and IP Management at #52DAC

Also Read

A Systems Company Update from #52DAC

Design Collaboration, Requirements and IP Management at #52DAC

Managing Semiconductor IP

Share this post via:


0 Replies to “Talking Directly to EDA R&D”

You must register or log in to view/post comments.