Used well, the Aspect Oriented (AO) features of the e verification language can save you scarce project time and give you a solution that can absorb change. The trick, of course, is using AO well.

“Verification is a very hot topic these days since it consumes the largest part of all design projects (60-70%). It is also one of the fast growing segments of the EDA industry. Many customers are interested to understand more about the benefits of AOP, but there are not a lot of resources available to learn about the advantages of using AOP with the e language…I really love the book. It provides very practical advice and is one of the best books written on the e verification language.”

–Mike Stellfox, Principle Field Verification Methodologist, Cadence Design Systems

The Aspect Oriented (AO) features of e represent an advanced software paradigm - so advanced that certain features are still not available in mainstream software languages. Expert users can exploit AO to craft verification environments that are simple to understand, yet flexible enough to handle almost any situation that test writers or unstable specifications can throw at them. And they can do it far more quickly and efficiently than non AO programmers would believe.

But how do you become an expert? How can you avoid the awkward learning phase when results can be anything but efficient? How do you unlock the power of AO in your next project?

We recommend that you cheat, and just learn from our hard work. Sure, you could do what we did - work on some seriously tough projects with a whole bunch of really good engineers, and fight to beat improbable deadlines. Alternatively, you could just buy yourself a copy of David Robinson’s book, and save yourself the pain.

Aspect-Oriented Programming with the e Verification Language takes a pragmatic, example based, and fun approach to unravelling the mysteries of AOP. In this book, you’ll learn:

• how to use AOP to organize your code in a way that makes it easy to deal with the things you really care about in your verification environments. Forget about organizing by classes, and start organizing by functionality, layers, components, protocols, functional coverage, checking, or anything that you decide is important to you
• how to easily create flexible code that eases your development burden, and gives your users the power to quickly do what they need to do with your code
• how to truly create a plug-and-play environment that allows you to add and remove functionality without modifying your code. Examples include how to use AOP to create pluggable debug modules, and a pluggable module that lets you check that your testbench is still working before you begin a regression
• how to use AOP to sidestep those productivity roadblocks that seem to plague all projects at the most inconvenient of times
• why “return” is evil, and some other “gotchas” with the AOP features of e

All of the methodologies, tips and techniques described in his book have been developed and tested on real projects, with real people, real schedules and all of the associated problems that come with these. Only the ones that worked, and worked well, have made it in, so by following the advice given in the book, you’ll gain access to the true power of AOP while neatly avoiding the effort of working it all out yourself.

It’s the pragmatic way.

Available in the US now from Amazon and Elsevier.

Available in the UK and Europe from the 26^th of September.

This entry was posted by admin on Wednesday, August 29, 2007 at 2:00 pm and is filed under Methodology, News. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.