Comments on: How to Write Good Use Case Names – 7 Tips http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/ Software product success. Thu, 18 Mar 2010 00:01:42 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: What is the key to writing a good Use Case?: Ask A Good Product Manager: Your product management questions answered http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/comment-page-1/#comment-363597 What is the key to writing a good Use Case?: Ask A Good Product Manager: Your product management questions answered Sun, 04 May 2008 06:16:19 +0000 http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/#comment-363597 [...] Define the use case names. Each name is in the form of subject-verb-object, with a clear goal implicit in the name. [...] [...] Define the use case names. Each name is in the form of subject-verb-object, with a clear goal implicit in the name. [...]

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/comment-page-1/#comment-67236 Scott Sehlhorst Fri, 26 Jan 2007 15:49:16 +0000 http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/#comment-67236 Great additions Harry, thanks! Great additions Harry, thanks!

]]> By: Harry Nieboer http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/comment-page-1/#comment-67131 Harry Nieboer Thu, 25 Jan 2007 22:43:14 +0000 http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/#comment-67131 I would add one tip and extend another of your seven: Good Use Case Names Use Terms From The User Domain. As the name of the use case must make the meaning of the Use Case clear to the users it is a good idea to use terms from the users. These terms should preferably be included in your glossary. Good Use-Case Names Reflect User Goals, and not the way that goal is accomplished. Too often names like "add appointment in Outlook" are used, whereas a solution-neutral "plan appointment" definitely reflects the User Goal better. Try to avoid Use-Case names that begin with "Do", "Process" or "Carry out" Good Use-Case Names Reflect one Goal for one User Use Cases are too big if the flow or alternate flows are only of value to distinct Actors. Use Cases are too big if they reflect multiple goals that would not necessarily be achieved at the same moment in time, e.g. "Finish book and send it to editor" Use Cases are too big if they reflect a goal that can not be achieved at a single moment in time, e.g. "Write book" I would add one tip and extend another of your seven:

Good Use Case Names Use Terms From The User Domain.

As the name of the use case must make the meaning of the Use Case
clear to the users it is a good idea to use terms from the users.
These terms should preferably be included in your glossary.

Good Use-Case Names Reflect User Goals, and not the way that goal is accomplished.

Too often names like “add appointment in Outlook” are used, whereas
a solution-neutral “plan appointment” definitely reflects the User Goal
better.
Try to avoid Use-Case names that begin with “Do”, “Process” or
“Carry out”

Good Use-Case Names Reflect one Goal for one User

Use Cases are too big if the flow or alternate flows are only of value
to distinct Actors.
Use Cases are too big if they reflect multiple goals that would not
necessarily be achieved at the same moment in time, e.g. “Finish book
and send it to editor”
Use Cases are too big if they reflect a goal that can not
be achieved at a single moment in time, e.g. “Write book”

]]>