What tool do you use when writing use cases?

Question

What tool do you use to write use cases and why?

Do you use a regular word processor (Word / OpenOffice), a Wiki, a specialized tool (fe Visual Use Case ), or something else?

Answer 1

I wrote usage examples with a common word processor using a simple template. This was enough for me, since I see no use in drawing oval shapes and sticks, so for me it’s enough to just plan the text. I also tend to keep the text short. Personally, I prefer to write user stories instead of using, although there is a connection between them.

Even Mike Cohn himself recommends using a word processor.

Answer 2

Visual tools are good for sharing ideas: I used Umbrello because it is very easy to use, fast, and does the job, although diagrams are all you get (you are unlikely to get diagram validation, reasonable code analysis or generation, etc.)

I believe problem tracking is a good way to track problems, including use cases. If you are trying to accomplish something and don’t want something to slip through the cracks, you need to maintain the TODO list somewhere, preferably sharing it among all the team members. The diagram is useless here, but a tracker with a touch on its use is gold.

Answer 3

Here at work we use Rally ( http://www.rallydev.com/ ). This is an online tool for writing and tracking articles. The commercial version has several functions, such as iteration planning, evaluation points, and high-speed combustion schemes. From what I understand, it is expensive, but it costs money in the long run.

Rally also offers a free, irrigated version if you want to flatten your tires a bit before committing them: http://www.rallydev.com/agile_products/editions/community/