Window “Stereotypes”

In objectiF RM, you use stereotypes to differentiate between the individual entities. Entities are, for example, requirements, test cases, documents, diagrams, queries, and so on. Each element in objectiF RM is always assigned to a stereotype, which allows you to specify the respective element more precisely via properties and to distinguish it from others. Stereotypes such as Requirement or Port contain so-called sub stereotypes, which thus allow the element to be specified. For example, a requirement can be a Feature of the stereotype or a Bug.

The project templates contain a number of stereotypes that you, as a user, can enhance with your own substereotypes. Each stereotype has properties that are standard in the template. These cannot be deleted. However, you can enhance them or define new properties that are then only available for elements of this stereotype. Properties that are defined at the highest level are inherited by the sub stereotypes so that they are also available to all sub stereotypes. Properties that are only valid for a substereotype are therefore only defined there. For example, an administrator can define an additional sub-stereotype for the Requirement stereotype that provides the additional property Effort of type Decimal Number. This property can then only be used by requirements of this type. Properties that the user subsequently defines are called user-defined properties.

If you need a project object that cannot be mapped with the existing stereotypes, you can also invent your own. These new elements are called artifacts in objectiF RM. To do this, you create a new artifact under the Artifact stereotype and then use the Form Designer to create a suitable form so that you can record the data later.

All stereotypes are managed centrally in the Stereotypes window. To open the window, click the eye and choose Show Stereotypes.

Use stereotypes as filters

In some situations, a selection dialog opens when you want to assign an element to another element. By assigning special stereotypes to your packages, you can restrict the display so that you can navigate more quickly to the target elements. When creating document templates, you use the stereotypes to determine which content (requirements, diagrams, queries) is to be generated later in a chapter. If you later create a document (chapter) based on this template, the stereotype means that when you assign the context element (which package is evaluated), only those packages are offered that correspond to the stereotype.

Stereotypes

Relationships

Diagrams