Tables in Relatics represent specific parts of the project’s systems engineering (SE) model. The model selector is used to view a snapshot of the model by selecting which parts of the model are visualized in the table. Furthermore, the model selector can provide insight into the SE model of a project because it reflects the model objects.

Understand the model selector

• The model selector shows all model objects hierarchically. The model objects are arranged in a tree, where type properties can be recognized by checkboxes and type relations can be recognized by arrows.
• The root of the model selector is dependent on the type element it is opened in.
• At the top of the model selector, the name of one or multiple type elements is stated in a header. The headers can be folded and unfolded by pressing .
  • Standard type elements have one header with the type element name in the model selector. Below this header, the model objects are defined.
  • Derived type elements have an additional header with the name of the origin element. The header is used to edit the grouping of the origin type element.
  • Middle type elements have two additional headers with the origin and target element names. The headers are used to edit the grouping of the origin and target type elements.
• In the My view tab all user can make use of the model selector to add and remove model objects. However, for use cases and the all elements view the model selector is only editable by power users.

Note:

• Model objects can be visualized in the table by selecting them in a thread. The model objects must be deselected from the last object in the thread to the first. So, it is impossible to deselect the first model object in a thread when more are selected.