This is probably the best book that I have read on the broad subject of Requirements Process. Thankfully it is not another book pushing a limited view of Requirements .. not all project types respond well to pure Agile and not all project types need Waterfall. Instead it presents the core principles of Requirements Process and shows how to weave a thread through whatever process, (Agile, Waterfall, Agifall, Watergile) that you choose. This is a professional approach and allows you to select the most appropriate tools and techniques.
Very specifically, the requirements process is presented from the very start, with the Business Process, which is then analysed down into automated parts, the Use Cases, and the manual processes. The Use Cases then become the source of the testable requirements.
The process described fits quite easily with PRINCE and answers many questions left open in other tomes on this subject. Given that we know that inadequate requirements are a source of much error and rework it is a good idea that all IT professionals have a rather complete picture of how requirements should be captured, managed and implemented. This book is strongly recommended as a thorough view of the subject. It does present requirements process from the point of view of the author's process, "Volere", but that should not distract as it is an evolved and thorough process. It allows the authors to be specific in their provision of templates for requirements, and to provide detaield implementation details. Their associated website also has many useful whitepapers and templates.
The book addresses Requirements Process along three parallel paths, the "Rabbits", fast agile types of project, the "Horse", more formal enterprise projects, and naturally, the Elephant ... the heavyweight project. Each has its requirements needs addressed throughout the book. There is just one story about requirements.. the principles, and they can be mapped onto whatever type of project. This book shows how to do that and is strongly recommend.