
Amazon Prime Free Trial
FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with FREE Delivery" below the Add to Cart button and confirm your Prime free trial.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited FREE Prime 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
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:
-46% $30.99$30.99
Ships from: Amazon Sold by: Story Haven Press
Save with Used - Good
$14.23$14.23
Ships from: Amazon Sold by: KAFKASLLC
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
There is a newer edition of this item:
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
Frequently bought together

Similar items that may deliver to you quickly
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: #737,892 in Books (See Top 100 in Books)
- #246 in Object-Oriented Design
- #798 in Software Development (Books)
- #1,846 in Computer Software (Books)
- Customer Reviews:
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 20 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.
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 the book very useful and a great resource for anyone creating or reading software specifications. They say the information is laid out clearly, and the table of contents makes it easy to find an overall view of use case topics. Readers also appreciate the reminder chapters, which act both as a reminder and refresher. They mention the concepts are presented in multiple ways and the book doesn't provide a specific framework with esoteric descriptions.
AI-generated from the text of customer reviews
Customers find the book very useful, great, and excellent. They say it has good examples and advice. Readers also mention it's a comprehensive guide to writing use cases and an excellent desktop reference for business analysts.
"...guide you during the writing of your use cases, keep them at consistent levels of abstraction and, more important, at all times highlight the..." Read more
"...All of this is was demonstrated with great examples...." 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
"Hands down - this is the best book on use cases. If you want to write good and effective use cases, THIS is the book to get...." Read more
Customers find the book easy to comprehend. They say the information is laid out clearly and the table of contents makes it easy to find an overall view of use case topics. Readers also mention that the index breaks down the topics in great detail. Overall, they say the book is well-written and covers all aspects of use case writing.
"...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
"...you decide that use cases are easy to understand, the methodology quite easily learned and particularly applicable to the workflow application..." Read more
"A great place to start with use cases. Easy to comprehend. There is no mention of the graphical model of use cases...." Read more
"This book is well written. All the information are laid out clearly and the book covers all aspects of use case writing. Also very readable...." Read more
Customers find the reminder chapters particularly useful for keeping on track. They say the book acts both as a reminder and refresher. Readers also appreciate the multiple ways concepts are presented.
"...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
"Very helpful. Cockburn is a good teacher. Concepts are presented in multiple ways to give you multiple chances to get it...." Read more
"...has been some years since I last created use cases, this was a great refresher for me, and I bought a second copy for my employees who were doing..." Read more
"A great book, acts both as a reminder and teached me some New stuff. Should be a book every one who Works With specs. should read." Read more
Reviews with images
Unprofessional print and cut on popular profession reference book
-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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
I've had a chance to work with use cases and specification of variable quality in my career. Some were much better than the other, but it really varied company-to-company. One common denominator (and sadly an annoying one) was inconsistency regarding naming, conventions, level of detail ... I can't stress enough how much development time I've wasted due to unclear definitions, missing specifications, and general confusion. The author of this book does a great job explaining how use cases fill in this missing piece by suggesting use case format and listing many, many real world examples.
You will read about important aspects of good use cases such as scope definition, which things are to be used in the use case, which things are to be designed as a result of the use case, and the importance of listing preconditions and postconditions. All of this is was demonstrated with great examples. There were things I didn't really like about the book and they seemed like an amusingly big hammer - especially all the little icons and colours trying to introduce some sort of visual framework to it. I'd rather not see any of that noise, but that's a personal preference.
By now use cases have a bit of bad reputation due to heavy-weight methodologies that were encouraged in the past. RUP. Waterfall. BPM. You name it. The author suggests that use cases don't need to be "fully dressed" - we can use different kinds of formal language for use cases. A banking analyst is most likely going to be required to "dress them up", while a startup product owner may come up with something much less formal and relaxed.
With hindsight we can ask ourselves a question. Is this still worth it? Do we still want use cases in young dynamic and fast changing environments like new tech startups? I do think that user stories or BDD are a better fit here. On the other hand we can't forget that there still are huge software companies running important aspects of our daily lives (banks, telco, transport etc.). These companies try to change as well, but it often results in some form of poorly implemented and conceptually broken agilefall process. While I don't really want to advocate for full-blown use cases, it made me stop and think plenty of times, and I am absolutely convinced that some businesses would massively profit from quality use cases.
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.
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
Je conseille chaque architecte informatique à l'avoir et mettre en pratique les "recettes" de ce livre.
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.
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.








