Home > Community > Blogs > System Design and Verification > it s not too early to think about dac 2009
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

Register | Membership benefits
Get email delivery of the System Design and Verification blog (individual posts).


* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

It's Not Too Early to Think About DAC 2009

Comments(1)Filed under: System Design and Verification, DAC 2009, hardware-dependent software

Even though it's still a couple of months off, it's not too early to think about DAC 2009. This year's conference will be held July 26-31 at the Moscone Center in San Francisco.

The technical program was announced this week, and after a couple of years away from DAC, I will return this year to participate in three activities.

The first is a Tuesday presentation in session 3U of the User Track titled Design Flow for Embedded System Device Driver Development and Verification

The second is a Wednesday lunch panel, part of a day long Virtual Platform Workshop

The third is a Thursday panel titled The Wild West: Conquest of Complex Hardware-Dependent Software Design

It should be an interesting mix of opinions about how to address the current challenges in embedded software.

It's great to see all of the activity at DAC related to Virtual Platform and Embedded Software.

As I was looking up the information on the events I will participate in one thing caught my eye, the use of the term "Front-End". Last year when Cadence announced new R&D leadership I found out I was suddenly a member of the Front End Group of Cadence. Now the DAC User Track lists four sessions with "Front-End" in the title. It looks like the Front End is a great place to be this year as we work on tools and techniques to raise the abstraction and productivity of System Design and Verification.

Mark your calendars now and I'll see you at the conference.


Jason Andrews



By Ric Merrifield on May 13, 2009
Jason - one thing I have found in the design process is that people get too close to their requirements and suffer from what I call the "how" trap and don't realize how critical it is to separate "what" outcome is needed before diving into "how" to get there.  I blogged about it at the rethinkbook.com site and I would be interested to get your take.

Leave a Comment

E-mail (will not be published)
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.