Skip to end of metadata
Go to start of metadata

The basic entity in arKItect is an object. An object is defined by its name and its type. Types are important because they define the different kinds of objects that can exist in the project, appearance of the objects and relations between objects. For example, if an object S of type System can contain an object Sb of type Subsystem, this is because the types System and Subsystem allow this relation. We call the complete representation of the relations between the types the Rules.

The types in a project are important because they determine what can be done, see Working with Project Data. If the types are Planet, Star and Satellite, you can model star systems. If the types are Organ, Tissue and Cell, you can model living organisms and so on.

The possible relations between two types A and B can be resumed as follows:

  • An object of type A cannot contain an object of type B.
  • An object of type A can contain an object of type B as a flow.
  • An object of type A can contain an object of type B when it is not defined as a flow.

When an object of type A can contain an object of type B, we say that A is the parent of B.

In Rules, you can:

To access the rules, click on the Rules panel in Rules and Filters. If the Rules and Filters panel is not visible, you can display it using Rules and Filters in the Show / Hide Panel of the Tools Category. If you are currently viewing the filters, the Rules shortcut should be visible above the Filters panel.

Rules lists the existing types of the meta-model in alphabetical order. This order cannot be modified.

In the next pages, you will find more details on the following topics:


  • No labels