The goal of DVClub events is to help build the verification community through quarterly educational and networking functions. We currently have active branches in Austin, Boston, RTP and Silicon Valley as well as international branches in Europe and India.

Events generally involve a free lunch followed by a technical program
and time allocated for networking. Topics vary, but the core focus is
end user verification stories, verification technology, and speculation
on our chosen career paths.

For more information on becoming a presenter, please contact us at: admin@dvclub.org

The application deadline for the MTV Scholarship Program is now less than 30 days away. This scholarship will provide round-trip airfare, conference registration fees, and hotel accommodations for several students across the nation to attend the 11th annual workshop on Microprocessor Test and Verification in Austin, TX.

“It’s always difficult to have to choose applicants”, said Eric Hennenhoefer, President of Obsidian Software. “There are so many talented young engineers out there, and we like to help really determined and motivated individuals whenever we come across them.”

2010 marks the first year of this scholarship, which is open to applicants until October 1st. More information can be found by visiting the scholarship program page:

2010 Microprocessor Test and Verification Scholarship

The notoriety of DVClub is spreading organically by word of mouth – something that’s not easy to achieve among a community of engineers. “We continually see new people at each event” said DVClub founder and organizer Eric Hennenhoefer. “Once they’ve experienced a DVClub event, they tend to come back to future events and bring more co-workers with them”. The average quarterly growth rate for DVClub in 2010 has been around 7% per quarter and climbing.

About DVClub:

The principal goal of DVClub is to have fun while helping build the verification community through quarterly educational and networking events. Currently over 50 advisors actively keep the club organized by brainstorming on topics, tracking down speakers, promoting events, and helping out on event day.

This article is reposted from the Cadence blog.

Can verification engineers gain control over the verification process, and stop being full-time firefighters? With proper planning, communication, and organization, the answer is “yes,” according to Allison Goodman, validation program manager at Intel for client and enterprise solid state hard drives.

Goodman spoke at a Silicon Valley DVClub lunch meeting January 26 at Dave and Buster’s restaurant in Milpitas, California. DVClub is an interesting organization. With chapters in Austin, Bangalore, Boston, Dallas, Research Triangle Park, San Diego, and Silicon Valley, the club’s stated purpose is “to have fun while helping build the verification community through quarterly educational and networking events.” IC engineers can join for free, and events are free. Costs are picked up by sponsors, including Cadence.

The January 26 event brought together around 120 attendees. There were a few EDA folks, but as far as I could tell, most attendees were verification engineers. Goodman’s speech was entitled “Tales from the trenches – validation missteps making us full time firefighters.” Goodman started her speech by noting that “it’s not technical problems that cause bad things to happen. It’s usually on the people side.” She identified four “missteps” that force engineers to put out fires rather than proactively validate a product’s quality.

Misstep #1: Insufficient planning

Insufficient planning occurs when you don’t have what you need to do testing, and your test coverage falls short. It’s caused by undocumented assumptions, the increasing scope of projects, and “missed dependencies” (you need 10 prototypes but only get 5). “If you don’t plan for it, it will surprise you, and every surprise will end up as a fire.”

The solution? Put your plan in writing – including who does what, how features work, what it means to be “done,” what checkpoints will monitor progress, and criteria for success. Keeping track of assumptions may be the biggest part of the solution. Write them down!

Misstep #2: Not designing for test

Designers often think their designs won’t have any mistakes, so there’s no plan for testing and no communication with validators. This makes it difficult to find and replicate bugs, to figure out what you need to monitor, and to know when you’re done. Interpreting test results as “pass” or “failure” may be very difficult. The antidote is for validators to get involved in the earliest stages of the design process. “Ask how you’re going to test it and how you’re going to tell if it’s working.”

DVClub provides an opportunity for networking as well as speakers and lunches.

Misstep #3: Not creating and integrating feedback loops

All too often, the marketing team or the design engineers make changes to a product, and don’t communicate those changes to the verification team. Further, many companies place engineers in “silos” with little or no communication – for example, there are software engineers, hardware engineers, and firmware engineers who don’t talk to each other.

What’s needed is continuous feedback about any changes in the product, as well as problems found with the product. Tests should be monitored for effectiveness and continually improved.

Misstep #4: Lack of transparency

Lack of transparency happens when you tell your boss (or team) that everything is well when it really isn’t. Or, you skimp on tests and coverage as schedule pressure rises, and don’t let managers know. As a result, risks and coverage gaps increase. “Tell the real story, and encourage others to do the same. Don’t declare that it’s done until it’s really done.”

My takeaway

While there are tools that can help with verification planning and monitoring – such as Cadence Incisive Enterprise Manager – quality verification depends on “people” factors such as whether and how verification teams plan, how early they’re involved with the design process, how well and how honestly people communicate, and how adaptable teams are to feedback and change. Pay attention to these issues and perhaps you can put the fire extinguishers away.

Richard Goering

If you receive our newsletters, then you’re already pre-approved.