Nothing going on here, move along…

Use cases

Use cases is a container for information which communicates with other use cases.

An <<include>> use case starts up with its parent use case

An <<extend>> use case only starts up with an extra process

A general use case may or may not start up with another use case

An <<extend>> is used with a condition which decides whether activate or not eg. Verify credit card IF it is a credit card transaction

Generalizations explain inheritances

With extends a child can’t replace a parent, there can’t be orphans.

Focus degree of detail

Can be brief, casual or full dressed

Typical use case documentation sections include:

Use case name






Basic course of events

Alternative paths



Author and date

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Tag Cloud

%d bloggers like this: