+49 (30) 467086-20 service@microtool.de

Use cases

A use case describes a visible system behavior of a system from a user’s perspective, with the intention of achieving a goal or obtaining a result.



The standard stereotype of use cases is <<UseCase>>. However, you can also use the stereotype MisUseCase or BusinessUseCase when you create a use case.
You need the stereotype when you create document templates, queries, forms, or search for an use case in the tool.

In the Stereotypes window, you can find the UseCase stereotype at the top level under U. Below this, further sub-stereotypes are created that you can extend or adjust using user-defined properties. Properties do not have to be defined separately for each sub-stereotype, since the properties are inherited from the main stereotype.

Create use case

You can enter, import, model in a diagram, or create backlog views for use cases manually using a dialog.


If you want to know at a glance which use cases are in a backlog, which use cases are covered by test cases, or want to have a list of all use cases, use queries. The objectiF RPM project templates contain queries on goals and their relationships by default. You can find them in the Products window in the Analyses/ Queries package:

  • Use case list
  • Use cases with derived requirements
  • Use cases with actors
  • Use cases with activity diagrams
  • Use cases with included use cases
  • Use cases with extending use cases
  • Use cases with test cases
  • Use cases with use case stories
  • Backlogs with use cases
  • Backlogs with use case references
  • Use case slices with use case

You can customize existing queries by hiding or displaying columns, or by changing the order of columns and column headers.

Context menu commands

Context menu commands allow you to edit, refine, schedule, share, create revisions, and more. The following context menu commands are available for use cases:

Edit | Edit Use Case

Opens the editing dialog in write mode.

Edit with Form

If additional forms have been created for use cases, you can select a form that is to be used.

Description document

Opens, creates or deletes a Word document.


Opens the slicing pane, which you can use to connect use case slices to test cases.

Create Reference| Create Use Case Reference

Creates a reference of the selected use case.

Change State

Allows you to change the state of a use case without opening the editing dialog.

Create review | Create review for use case

Creates a review for the use case, which is displayed directly below the use case.

Apply Pattern

Shows all patterns that can be applied to the use case. Green icons show that the pattern is particularly suitable.

Pattern Catalog | Pattern Catalog for Use Case

Opens the pattern catalog, which you can use to find out about all existing patterns.

Derive Requirement

Creates a request for the use case. You can find the request in the editing dialog of the use case on the tab Requirements/Derived Requirements.

Derive Block

Creates a block for the use case.


Allows the use case to be sent by link, e-mail or hyperlink.

Show Diagrams | Show Diagrams with Use Case

Opens a selection dialog in which all diagrams containing the use case are displayed. If you select a diagram and click OK, the diagram opens.

Go to

If relationships exist between a use case and requirements, goals, actors, test cases, or activity diagrams, you can jump to the relevant element here. The element is opened in a separate window on the right side of the screen.

Assign Activity Diagrams

Opens a selection dialog where you can assign an activity diagram to the use case.

Activity Diagram

Creates a new activity diagram for the use case.

Create with Form

If additional forms have been created for use cases, you can select a form that is to be used.

Execute Extension

If extensions have been created, you can select and execute them.

Create Variant

Enables you to create a use case variant. Additional commands are also offered that you can use to copy changes to the variant or use case to the use case or variant.

Edit Revision

Allows you to create a revision. You can also use it to call up, compare, and trace the history of a use case.

Export | Export Use Case

Exports the use case to a sxmi file.


Deletes the use case from the project. The action cannot be undone.