---
product_id: 5779548
title: "Writing Effective Use Cases"
brand: "alistair cockburn"
price: "Bs.505"
currency: BOB
in_stock: true
reviews_count: 10
url: https://www.desertcart.bo/products/5779548-writing-effective-use-cases
store_origin: BO
region: Bolivia
---

# Writing Effective Use Cases

**Brand:** alistair cockburn
**Price:** Bs.505
**Availability:** ✅ In Stock

## Quick Answers

- **What is this?** Writing Effective Use Cases by alistair cockburn
- **How much does it cost?** Bs.505 with free shipping
- **Is it available?** Yes, in stock and ready to ship
- **Where can I buy it?** [www.desertcart.bo](https://www.desertcart.bo/products/5779548-writing-effective-use-cases)

## Best For

- alistair cockburn enthusiasts

## Why This Product

- Trusted alistair cockburn brand quality
- Free international shipping included
- Worldwide delivery with tracking
- 15-day hassle-free returns

## Description

Writing Effective Use Cases

## Images

![Writing Effective Use Cases - Image 1](https://m.media-amazon.com/images/I/619aqfdFY9L.jpg)

## Customer Reviews

### ⭐⭐⭐⭐⭐ 5.0 out of 5 stars







  
  
    Distills the core idea behind use cases
  

*by C***H on Reviewed in the United States on May 19, 2009*

Having 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

### ⭐⭐⭐⭐⭐ 5.0 out of 5 stars







  
  
    LOVE THIS!
  

*by A***N on Reviewed in the United States on October 7, 2024*

I love this book. I needed to get a good book to be able to review the best use cases.

### ⭐⭐⭐⭐ 4.0 out of 5 stars







  
  
    There is still a lot of value in this classic use cases book even in 2017
  

*by V***O on Reviewed in the United States on March 14, 2017*

It's year 2017, software development went through major transformations, waterfall is (mostly) dead, RUP is dead, heavy UML is dead. Most of the companies now use some sort of agile-inspired technique to manage their software deliveries. Why on earth would anyone want to read a 17 year old book on use cases today? Well let me tell you something. It's good and it has a lot of value, that's why.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.

---

## Why Shop on Desertcart?

- 🛒 **Trusted by 1.3+ Million Shoppers** — Serving international shoppers since 2016
- 🌍 **Shop Globally** — Access 737+ million products across 21 categories
- 💰 **No Hidden Fees** — All customs, duties, and taxes included in the price
- 🔄 **15-Day Free Returns** — Hassle-free returns (30 days for PRO members)
- 🔒 **Secure Payments** — Trusted payment options with buyer protection
- ⭐ **TrustPilot Rated 4.5/5** — Based on 8,000+ happy customer reviews

**Shop now:** [https://www.desertcart.bo/products/5779548-writing-effective-use-cases](https://www.desertcart.bo/products/5779548-writing-effective-use-cases)

---

*Product available on Desertcart Bolivia*
*Store origin: BO*
*Last updated: 2026-02-20*