Introduction
This book is focused on the task of writing "clear and compelling" software requirements, as a prerequisite to the software development process. In the author's view, it's a task that's being done very badly, and both process and product suffer greatly as a result of bad requirements.
The core problem is that requirements are written by analysts, developers, project managers, and others who are to close to the work to communicate in sufficient detail, and who tend to have poor communications skills in general.
The author does not intend to cast aside the known-and-proven techniques, but to provide a different perspective that can be integrated with them.