Aspect-Oriented Programming with the e Verification Language: A Pragmatic Guide for Testbench DevelopersMorgan Kaufmann, 28 iul. 2010 - 264 pagini 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 |
Cuprins
| 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 |
| 239 | |
Epilogue | 241 |
| 243 | |
Alte ediții - Afișează-le pe toate
Aspect-oriented Programming with the E Verification Language: A Pragmatic ... David Robinson Nu există previzualizare disponibilă - 2007 |
Termeni și expresii frecvente
added advice AHB AHB AHB ahb_monitor ahb_scoreboard alu_transaction_s aspect oriented aspect oriented programming aspect>><<aspect base class bfm_u bool bus interface BusBus InterfaceInterface byte called class Foo clock tree ClockClock TreeTree Code Listing configuration interface contain cover group CPUCPU create crosscutting concerns current_block deal debug declared dma_transfer_s doesn’t dominant concerns encapsulate enumerated type error etk.pl show example extendable case statement factory feature Figure file name following code functional coverage FunctionalityFunctionality functor grep high-level sequence hook method implement instantiate interact join points keep soft layer logger manifest file modify monitor monitor_u monitor-axi.e OOP solution pluggable code pointcuts pointer Problem Solution protocol register_names_t register_s return statement reuse scan chains ScanScan ChainChain scoreboard scoreboard-ahb.e SDIO signal SignalSignal Specman strategy pattern struct subtypes SystemC transaction transaction_s UART uint verification envi verification environment when-inheritance
Pasaje populare
Pagina 1 - A language that doesn't affect the way you think about programming is not worth knowing.
Pagina 239 - Y. Hollander, M. Morley, and A. Noy. The e language: A fresh separation of concerns.