Verification In All Its Aspects

This publication has been issued in implementation of the United Nations Disarmament Information Programme as a handy, convenient and attractive reference tool containing the report of the Secretary-General on verification in all its aspects, including the role of the UN in the field of verification. It also contains additional material related to the publication of the report. The publication continues the Disarmament Study Series and should serve as a valuable addition to the reference section of public and university libraries, permanent missions, research institutes and specialized non-governmental organizations.

Following 1990s defence cuts, Britain's armed forces are stretched quite severely. Successive governments have preferred buying US nuclear technology and intelligence to working with European partners. The US has disengaged from Europe, leaving the NATO countries with no common purpose. The contributors to this volume, economists and defence analysts outline how UK governments need to: establish priorities within budget constraints, exploring a division of labour with European partners; restructure the army towards forces suitable for low-intensity interventions and peace support; rationalize defence production and procurement; adapt the bipolar Cold War arms control regimes to the new multipolar world; and redefine the requirement for an independent British nuclear capability.

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