+49 (30) 467086-20 service@microtool.de
Products » objectiF RM » Requirements Engineering » Requirements


A requirement is a property or condition that a system or system component must fulfill.


Create requirements

You can enter requirements manually using a dialog, import them, model them in a diagram, or create them in backlog views.


If you want to know at a glance which requirements are in a backlog, which requirements are realized by which elements or which requirements do not yet have test cases, then use queries. The objectiF RM project templates contain queries on goals and their relationships by default. You can find them in the Products window in the Analyses/ Queries package:

  • Requirements list
  • Derived requirements (compact)
  • Requirements with realized elements
  • Requirements with personas (compact)
  • Requirements with test cases
  • Backlogs with requirements

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


The stereotype of requirements is <<Requirement>>. You need the stereotype when you create document templates, queries, forms, or search for a requirement in the tool.

In the Stereotypes window, you will find the requirement stereotype under DomainElement. Below this there are more sub-stereotypes that you can extend or customize with user-defined properties. Properties such as priority, identifier pattern, etc. do not have to be defined separately for each sub-stereotype, since the properties are inherited from the main stereotype.

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 requirements:

View | View Requirement

Opens the editing dialog in view mode.

Edit |Edit Requirement

Opens the editing dialog in write mode.

Edit with Form

If additional forms have been created for requirements, you can select a form to be used.

Change State

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


Schedule Assigns the requirement to an activity and a backlog.

Dervie test case Creates a test case for the requirement.

Contains additional commands that you can use to create refinements, derivations, references, and dependencies to the requirement.

Create review | Create review for requirement

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

Apply Pattern

Shows all patterns that can be applied to the requirement. Green icons indicate that the pattern is particularly suitable.

Pattern Catalog | Pattern catalog for requirement

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


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

Show Diagrams | Show diagrams with requirement

Opens a selection dialog where all diagrams containing the requirement are displayed. If you select a diagram and click OK, the diagram opens.

Create with Form

If additional forms have been created for requirements, you can select a form to be used.

Create Variants

Allows you to create an appropriation requirement variant. Additional commands are also available that you can use to copy changes to the variant or requirement to the requirement or variant.

Edit Revision

Allows you to create a revision. It also allows you to view, compare, and trace the history of a requirement.

Go to

If there are relationships between a requirement and other requirements, goals, stakeholders, test cases, use cases, blocks or references, you can jump to the respective element. The item opens in a separate window on the right side of the screen.


Exports the requirement to a sxmi file.


Deletes the requirement from the project. The action cannot be undone.