Instruct: Classify a given Amazon review into positive or negative sentiment.
Query: Use cases written by analysts for analysts

This is a good book if you plan to have business analysts writing use cases for other business analysts. It is a lousy book if the audience for your use cases are subject matter experts and technical people/engineers/developers. The "good" examples have all technical details stripped from them supposedly to make them easier to read; in actuality this makes them easier to read for BAs, but useless for anyone else. Details this book recommends ignoring as "design" or "implementation" are actually implied requirements that are derived from non-functional or legacy constraints.Use cases can be a useful supplement for the "200 page traditional IEEE ... functional requirements", provided they have sufficient technical detail and traceability. Non-technical use cases used to replace traditional requirements is a recipe for project disaster.