Introduction to use cases

[alex_papworth]

In my defence!

I'd agree wth gonzo an almost all points

Like most tools, use cases have a value but only whe used in the right circumstances and in the right way.

As gonzo says, they are good for systems where there is a lot of user interaction. Otherwise, don't use them.
They strike a balance between the highly structured approach that a designer/developer needs and the informal approach to which the business user tends to respond best.

They're also good for planning purposes - you can break a use case into scenarios and plan to deliver agreed scenarios in a particular release or iteration.

What's the alternative? Unwieldy functional specs - unsatisfactory for developers and business users.
I'd be curious to hear what others have used.

I'm not sure what is considered spam - I am promoting my website but you should only click on the link if you're interested in the content and it doesn't cost!!

As a parting shot, use cases should never be used in isolation - users respond better to prototypes and other more visual, less abstract approaches.
This is discussed more in Requirements gathering alongside use cases!!!

[Rookie]

I'd agree wth gonzo an almost all points

Like most tools, use cases have a value but only whe used in the right circumstances and in the right way.

As gonzo says, they are good for systems where there is a lot of user interaction. Otherwise, don't use them.
They strike a balance between the highly structured approach that a designer/developer needs and the informal approach to which the business user tends to respond best.

They're also good for planning purposes - you can break a use case into scenarios and plan to deliver agreed scenarios in a particular release or iteration.

What's the alternative? Unwieldy functional specs - unsatisfactory for developers and business users.
I'd be curious to hear what others have used.

I'm not sure what is considered spam - I am promoting my website but you should only click on the link if you're interested in the content and it doesn't cost!!

As a parting shot, use cases should never be used in isolation - users respond better to prototypes and other more visual, less abstract approaches.
This is discussed more in Requirements gathering alongside use cases!!!

More blatent spamming! Why not click on my 'more spam' linky: http://www.spam.com/

[jmo21]

didn't Alex post a while back asking what people thought of this idea about a business analysis blog of some sort?

Edit: here it is: http://forums.contractoruk.com/gener...lyst-site.html

[cojak]

Well, godd luck to him provided he doesn't expect me to put my hand in my pocket...

[cojak]

Here's another good website to giving examples

[lightng]

Getting the hang of this now.

I've drawn a boundary box labelled CUK. Outside I've got a stickman with the role description "Spammer". I've put an oval use-case bubble in the boundary box and labelled it "Spam CUK". A straight line between the stickman and the use-case bubble completes my diagram.

Wow, I now understand the bigger picture. This use-case stuff is truly amazing!