Aspect-Oriented Programming with the e Verification Language: A Pragmatic Guide for Testbench Developers

Front Cover
Morgan Kaufmann, Jul 28, 2010 - Computers - 264 pages
0 Reviews
What’s this AOP thing anyway, really—when you get right down to it—and can someone please explain what an aspect actually is?

Aspect-Oriented Programming with the e Verification Language takes a pragmatic, example based, and fun approach to unraveling 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
• 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
• 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
• Utilize AOP to sidestep those productivity roadblocks that seem to plague all projects at the most inconvenient of times
• Discover why “return” is evil, and some other “gotchas” with the AOP features of e
All of the methodologies, tips, and techniques described in this 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 this book, you’ll gain access to the true power of AOP while neatly avoiding the effort of working it all out yourself.

• 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
• 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
• 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
• Utilize AOP to sidestep those productivity roadblocks that seem to plague all projects at the most inconvenient of times
• Discover why “return” is evil, and some other “gotchas” with the AOP features of e
 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Contents

Chapter 1 Introduction to Aspect Oriented Programming AOP
1
Chapter 2 AOP in e
31
Chapter 3 Using AOP to Organize Your Code
67
Chapter 4 Creating Flexible Code
93
Chapter 5 Creating Pluggable Code
113
Chapter 6 Improving Your Productivity
145
Chapter 7 AOP in Action
163
Chapter 8 Analysing e Code
215
Bibliography
239
Epilogue
241
Index
243
Copyright

Other editions - View all

Common terms and phrases

Popular passages

Page 1 - A language that doesn't affect the way you think about programming is not worth knowing.
Page 239 - Y. Hollander, M. Morley, and A. Noy. The e language: A fresh separation of concerns.

About the author (2010)

David Robinson is a senior program manager on the SQL Data Services (SDS) team. David is responsible for a multitude of things, including driving product features, developing code samples and, most important, demonstrating to customers the value that SDS and cloud computing provides. David enjoys getting out in the community, presenting on SDS, gathering feedback, and helping to ensure SDS meets whatever demands you throw at it. David has also written for MSDN Magazine on developing solutions against SDS. Before joining the SDS team, David was a solutions architect on Microsoft's Health and Life Sciences team.

Bibliographic information