I used Microsoft Visio to create all of those diagrams. I ended up creating templates for the types of drawings I do the most, since creating them from scratch can take some time, and having a template assures a consistent delivery when producing multiple documents. Thanks again!

This blog is one of the most interesting I have seen explaining use cases and scenarios. The structure of the graphics is also fantastic to help with planning of test cases.
What tool do you use to produce the diagrams?

Julia.

Thanks again!

There are at least the following similarly named things: use scenario, user scenario, use case, use case scenario.

Cockburn, at least, defines “use(r) scenario” to mean the same thing as what I called a “use case scenario”. I intentionally included the word “case” to make sure that people didn’t confuse it with the abstract market situation that Pragmatic describes.

As you point out – I didn’t explain that very well. Now, hopefully, others will find this discussion. Thanks for pointing it out.

Fantastic content on the site. I just found this after hearing about it at Pragmatic’s PPM course.

One comment on this page: Pragmatic uses the term “use scenario” (not “use case scenario,” as you use here) as a means to describe a market problem that needs solving. That is, what is the user trying to accomplish, and is not able to, that creates the problem at hand?

That’s quite different from the “use case scenario” described here, which is essentially a path through a use case — which is also a useful concept, just different. It might be worth differentiating between these two concepts on the site.

Thanks again for the great content.

Brian