Use cases

Next, UCs (Use Cases) are organized by using two relationships that are dependency relations stereotyped with:

• <<extends>> for generalizations or refinements, and
• <<uses>> for sub-operations/functionalities.

Use cases' diagram: relationships

For instance, consulting an account means to get its amount (with last preformed operations, etc.). This value can be <<used>> to validate other operations or it can be simply printed on screen or on a ticket (this corresponds to various kind of consultations or <<extensions>>).