As a software engineer, I found Dr. Young's book to be practical and very useful. My project has been implementing six of his ten "Recommended Requirements Practices," and they have indeed proved to be effective, as advertised. The book is organized around the 10 requirements practices, but covers a very wide range of other issues that influence project success - including such diverse topics as project management, team partnering, process definition, and project communication. The book and accompanying CD are loaded with templates and examples; we've reused a couple of them to produce deliverables for our customers.
The book doesn't have lots of "textbook" things like review problems and quizzes; it's much more focused on real-world implementation than some other requirements books (like the ones that are obviously the collected notes from some professor's undergraduate class). There is a glossary, and two good indexes (by author and by subject) that are accurate and at the right level of detail to make the book effective as a reference. The other thing that has kept this book on my ready-reference shelf is the annotated bibliographies - each chapter ends with a list of key references (mostly books and articles), with explanations of why they are significant, what they contain, and URLs for the ones that are available on the web.
