
Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
-34% $37.76$37.76
Ships from: Amazon Sold by: Everleaf Books
Save with Used - Good
$9.15$9.15
Ships from: Amazon Sold by: Zoom Books Company

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the author
OK
Writing Effective Use Cases 1st Edition
Purchase options and add-ons
Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use Cases, Alistair Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations. Cockburn begins by answering the most basic questions facing anyone interested in use cases: "What does a use case look like? When do I write one?" Next, he introduces each key element of use cases: actors, stakeholders, design scope, goal levels, scenarios, and more. Writing Effective Use Cases contains detailed guidelines, formats, and project standards for creating use cases -- as well as a detailed chapter on style, containing specific do's and don'ts. Cockburn shows how use cases fit together with requirements gathering, business processing reengineering, and other key issues facing software professionals. The book includes practice exercises with solutions, as well as a detailed appendix on how to use these techniques with UML. For all application developers, object technology practitioners, software system designers, architects, and analysts.
- ISBN-109780201702255
- ISBN-13978-0201702255
- Edition1st
- Publication dateOctober 5, 2000
- LanguageEnglish
- Dimensions7.3 x 0.7 x 9 inches
- Print length304 pages
There is a newer edition of this item:
Frequently bought together

Customers who viewed this item also viewed
Editorial Reviews
Amazon.com Review
The focus of this text is on use cases that are written, as opposed to modeled in UML. This book may change your mind about the advantages of writing step-by-step descriptions of the way users (or actors) interact with systems. Besides being an exceptionally clear writer, the author has plenty to say about what works and what doesn't when it comes to creating use cases. There are several standout bits of expertise on display here, including excellent techniques for finding the right "scope" for use cases. (The book uses a color scheme in which blue indicates a sea-level use case that's just right, while higher-level use cases are white, and overly detailed ones are indigo. Cockburn also provides notational symbols to document these levels of detail within a design.)
This book contains numerous tips on the writing style for use cases and plenty of practical advice for managing projects that require a large number of use cases. One particular strength lies in the numerous actual use cases (many with impressive detail) that are borrowed from real-world projects, and demonstrate both good and bad practices. Even though the author expresses a preference for the format of use cases, he presents a variety of styles, including UML graphical versions. The explanation of how use cases fit into the rest of the software engineering process is especially good. The book concludes with several dozen concrete tips for writing better use cases.
Software engineering books often get bogged down in theory. Not so in Writing Effective Use Cases, a slender volume with a practical focus, a concise presentation style, and something truly valuable to say. This book will benefit most anyone who designs software for a living. --Richard Dragan
Topics covered:
- Introduction to use cases
- Requirements
- Usage narratives
- Actors and goals
- Stakeholders
- Graphical models for use cases
- Scope for use cases (enterprise-level through nuts-and-bolts use cases)
- Primary and supporting actors
- Goal levels: user goals, summary level, and subfunctions
- Preconditions, triggers, and guarantees
- Main success scenarios
- Extensions for describing failures
- Formats for use cases (including fully dressed one- and two-column formats)
- Use case templates for five common project types
- Managing use cases for large projects
- CRUD use cases
- Business-process modeling
- Missing requirements
- Moving from use cases to user-interface design
- Test cases
- eXtreme Programming (XP) and use cases
- Sample problem use cases
- Tips for writing use cases
- Use cases and UML diagrams
From the Back Cover
Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask: "How exactly am I supposed to write use cases?" Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable.
In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a "nuts-and-bolts" tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises--with answers--to illuminate the most important points.
Highlights of the book include:
- A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more
- A use case style guide with action steps and suggested formats
- An extensive list of time-saving use case writing tips
- A helpful presentation of use case templates, with commentary on when and where they should be employed
- A proven methodology for taking advantage of use cases
With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.
0201702258B04062001
About the Author
Alistair Cockburn is a recognized expert on use cases. He is consulting fellow at Humans and Technology, where he is responsible for helping clients succeed with object-oriented projects. He has more than twenty years of experience leading projects in hardware and software development in insurance, retail, and e-commerce companies and in large organizations such as the Central Bank of Norway and IBM.
0201702258AB07302002
Product details
- ASIN : 0201702258
- Publisher : Addison-Wesley Professional; 1st edition (October 5, 2000)
- Language : English
- Paperback : 304 pages
- ISBN-10 : 9780201702255
- ISBN-13 : 978-0201702255
- Item Weight : 1 pounds
- Dimensions : 7.3 x 0.7 x 9 inches
- Best Sellers Rank: #136,603 in Books (See Top 100 in Books)
- #36 in Object-Oriented Design
- #111 in Software Development (Books)
- #291 in Computer Software (Books)
- Customer Reviews:
About the author

Dr. Alistair Cockburn (pronounced CO-BURN) was named as one of the “42 Greatest Software Professionals of All Times" in 2020 as a world expert on methodologies, project management, software architecture, use cases and agile development. He co-authored the Agile Manifesto in 2001. Since 2015 he has been working on expanding agile to cover every kind of initiative, including social impact project, governments, and families. For his latest work, see alistaircockburn com.
Dr. Cockburn's books cover the range from "Surviving Object Oriented Projects", on project management, to "Design in Object Technology" and "Hexagonal Architecture Explained", both for programmers, to the world-best-seller, "Writing Effective Use Cases", for business analysts, to "Agile Software Development", for everyone moving to agile development. His future works will include "Tactics and Strategies of Successful Project Managers", "Simplifying Software Design", and a four-part series "The Heart of Agile."
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonCustomers say
Customers find this book to be a comprehensive guide to writing use cases, with one customer noting its easy-to-navigate Table of Contents. They consider it an outstanding product, with one customer describing it as an excellent no-nonsense book.
AI-generated from the text of customer reviews
Select to learn more
Customers find this book to be a comprehensive guide to writing use cases, describing it as the best book on the subject. One customer notes that the Table of Contents makes it easy to find an overall view of Use Case topics, while another mentions it is helpful for more experienced requirements writers.
"...book to the other ones, this is superior because it does not provide a specific framework with esoteric descriptions about how Use Cases evolve..." Read more
"...This was the greatest book on use cases in the waterfall era, written by the greatest expert on the subject, so I’m better primed to jump into agile..." Read more
"...The Table of Contents makes it easy to find an overall view of Use Case topics and the Index breaks it down in great detail...." Read more
"Very helpful. Cockburn is a good teacher. Concepts are presented in multiple ways to give you multiple chances to get it...." Read more
Customers find the book to be a great value, with one customer describing it as an excellent no-nonsense guide.
"I love this book. I needed to get a good book to be able to review the best use cases." Read more
"...Why is this book worth someone’s time? In other words, why did I choose to read it? For two reasons...." Read more
"...Well let me tell you something. It's good and it has a lot of value, that's why...." Read more
"A. Cockburn doesn't need any presentation. An excellent writer and theoretician...." Read more
Reviews with images

Unprofessional print and cut on popular profession reference book
Top reviews from the United States
There was a problem filtering reviews. Please reload the page.
- Reviewed in the United States on October 7, 2024I love this book. I needed to get a good book to be able to review the best use cases.
- Reviewed in the United States on May 19, 2009Having tried 'Use Cases: Requirements in Context' and 'Managing Software Requirements: A Use Case Approach' I can tell you this is the book to really understand what's the whole point of Use Cases.
Whenever I am introduced to a modeling tool (UML would be another example for me) I always end up wondering what to put and what to leave out of the model I am building for the problem at hand. This book does not give you a specific answer (who would want a solution that would only apply to only a limited set of problems? I did not, at least for the project I used this book for), it gives you the very essence of the criteria you should apply to include something or not.
By comparing this book to the other ones, this is superior because it does not provide a specific framework with esoteric descriptions about how Use Cases evolve throughout the project life cycle. It describes the purpose of writing use cases: describing a goal of some importance to an actor.
So many times I have read these 'Use Cases' that describe a system in terms of people pushing buttons, changing values in some UI and end up describing the system in terms of CRUD operations not descriptive by any means. If, after all, most 'Enterprise Systems' built are just fancy and costly web-versions of SELECT, INSERT, DELETE and UPDATE statements executed against a database, how informative can be use cases that only say a system INSERTS/UPDATES/DELETES/QUERIES data in a database? By describing a user goal, all database operations (and many other interactions with any back-end systems) start making sense. I have found that we human beings are so good at 'filling out the blanks' that some of these operations might even sound obvious at times.
This book will guide you during the writing of your use cases, keep them at consistent levels of abstraction and, more important, at all times highlight the ultimate goal your user wants to achieve by executing a use case.
If you really want to complement the topics in this book, consider the perfect companion 'Patterns for Effective Use Cases'.
Cheers!
Ytsejammer
- Reviewed in the United States on March 4, 2025The first thing I noticed is that this book is almost 25 years old. That’s an eternity in computer science, especially in a non-mathematical subject. It was written under the “waterfall” paradigm of software development, before agile took over most of the software engineering world. Instead of a page or two, waterfall specifications could require a binder of dozens, if not hundreds, of pages. This book describes “use cases” instead of the “user stories” that agile commends. Why is this book worth someone’s time? In other words, why did I choose to read it?
For two reasons. First, I’m a big fan of studying history. I’ll admit that I didn’t read every page closely in 2025, but I picked up on why agile design documents are organized a certain way. Knowing the history of the field allows me to understand the present better – and theoretically, be prepared for the future better.
Second, most of the literature I’ve read on user stories is overly simplistic. They don’t go into enough detail about what to choose and how. When communicating with my developers, I want to understand what possibilities can and cannot be communicated. To see the global set of options, I had to go back in time to when large design documents were the norm. Just like when someone reads Beowulf or The Canterbury Tales to understand how modern literature took its form, I can see all the glorious option that writing a user story encompasses.
Realistically, I don’t expect this book to be explored by a ton of people now. After all, it’s almost 25 years old! But thumbing through its pages enlightened me a bit as I start to communicate my ideas to the developers I work with. This was the greatest book on use cases in the waterfall era, written by the greatest expert on the subject, so I’m better primed to jump into agile practices and whatever era comes next.
- Reviewed in the United States on June 20, 2004I had never heard of Use Cases until taking a class in Systems Analysis and Development. So I went to Amazon and did a search for books on Use Cases and saw that this one was rated quite high. I believe I read all the customer reviews. I don't understand how most everyone can give a 5 star rating and one person gives it a 1 star rating.
I must say that this book could make even someone new like me, being new to Use Cases, look good. The Table of Contents makes it easy to find an overall view of Use Case topics and the Index breaks it down in great detail. The book is described by the author as a book that is, "predominately aimed at industry professionals who read and study alone, and is therefore organized as a self-study guide." I like that.
If you are looking for a book for a class, such as the one I took, or just want to look good at work to describe a process, behavioral requirements, or software development, surely this book could help you too.
- Reviewed in the United States on May 4, 2017Very helpful. Cockburn is a good teacher. Concepts are presented in multiple ways to give you multiple chances to get it. As tech books go, this one is pretty "squishy." Which is exactly right. The fact that it's 20 years old isn't a problem. Cockburn is teaching a method for creating coherence and completeness in designing a system. Sure, he's focused on computer systems, but I'm starting to think about how this methodology applies to a business plan.
The most important idea in the book, for me, is about "levels." How to know when you're getting too airy-fairy and when you're getting bogged down in the details and when you're getting it just right. I had a project where the problem was I was all over the place on levels, and this straightened me right out.
Top reviews from other countries
- Prasun DubeyReviewed in Canada on April 16, 2018
5.0 out of 5 stars Five Stars
excellent book
- Gareth GreenwoodReviewed in the United Kingdom on July 12, 2013
5.0 out of 5 stars Best book on UCs I've ever seen
This is a top-notch book on Use Cases. I got it because I had to write Use Cases for a programming and configuration tool for a safety controller used with electric motor drives in industrial automation systems. This is a SIL3 safety-critical application.
I disagree entirely with the two-star-awarding reviewer who calls Cockburn "naive". Indeed the great virtue of Cockburn's approach to Use Cases is that he keeps them simple. This is a major advantage in high-integrity systems where simplicity is the friend of reliability and safety. I also applaud Cockburn's evident disdain for using UML graphical notations for UCs. OO-methods are generally shunned in safety-critical systems as they are regarded as too imprecise (Indeed hardened practitioners in critical systems engineering often regard the use of UML/OO as a sign of limited competence.)
Cockburn is IMO absolutely right in saying that UCs are an essentially textual form. Sooner or later the developers of MIS-type systems will realise that those of us who have been doing hard software engineering (in this reviewer's case for over 40 years) actually have a far clearer idea of the kinds of specification formalisms that work when things absolutely have to be right. And when the OO fad has finally died, I reckon Cockburn's book will still be in print because it does not shackle itself to the UML/OO bandwagon.
IMO, this book is exceptionally well-written and down-to-earth. It is, I think, a solid and welcome contribution to the literature on specification.
- Paolo ScuroReviewed in Italy on November 8, 2013
5.0 out of 5 stars Effective methodology
The book provides a very effective methodology to collect and describe functional requirements.
The presentation is very clear and reach of examples from real projects. It is possible to learn use cases since reading the first sections. The rest of the book is dedicated to in-depth analysis of some topics.
-
JosephReviewed in France on August 29, 2015
5.0 out of 5 stars Très bon livre qui structure les idées
Livre très riche en enseignements et plein de bon conseils.
Je conseille chaque architecte informatique à l'avoir et mettre en pratique les "recettes" de ce livre.
- D. V. GATENBYReviewed in Germany on March 13, 2014
5.0 out of 5 stars A must-have!
If you can't claim for this book on expenses, pay for it out of your own pocket. This book is a must-have for any business analyst writing use cases.
The book starts off with the key points of use cases, giving clear, useful and useable pointers. I like the exercises too, which give you practice at writing use cases. The worked examples are also ideal for anyone who likes the "monkey see, monkey do" learning style.