Naming conventions are set using regulations for pictures (name pattern), writing, length and uniqueness of names.
Elements need to be able to be differentiated between by their names within their namespaces they are directly linked with. A package is used as an example when grouping elements and provides a joint namespace for these elements directly contained in the package.
Namespaces can be nested and contain elements which can be given names; these elements, in turn, represent a namespace for elements they contain. e.g. classes need to have unique names within a package, operations need to have unique names within a class and parameters need to have unique names within an operation.
A package's contents consists of so-called "packageable elements". Classes, events etc. belong to these, as well as packages themselves; this enables the packages to be hierarchically arranged. A package is the owner of these elements. This means that all elements contained are deleted from a model as soon as this package is deleted.
The elements' stereotypes can be used when setting namespaces in the configuration. This means you can set whether case sensitivity is relevant, whether they should have a certain minimum or maximum length and in what respect the name has to be unique.
The range of name verification means that uniqueness can be controlled step-by-step.
Unique in the entire Innovator model
This means the Innovator model within a repository, i.e. the unit that you open and which you log into as a user.
Certain element types occur in various methods. Uniqueness in the entire Innovator model and corresponding naming conventions can be used to assign elements more easily using simply the name. On the other hand, ambiguity may be unavoidable as certain names cannot be freely chosen.
Unique in the current model
The (sub)model is the third level in the Innovator model: <Innovator model>::<System model>:<Model>.
Unique naming in the current model simplifies communication within the level being viewed of the respective model. However, the same name can be allocated to other elements of the same type in other submodels.
Consider only elements defined in the namespace
Verifying the name for uniqueness is restricted to the immediate container, i.e. for operations it is carried out within the class and for parameters within the operation. However, it does take account of the names of imported elements.
There are a few exceptions for which the immediate container is not the namespace but a level of a more remote container; for example, the namespace of a state is formed by the state machine and not by the region which is represented by the immediate container. As a result, states can be moved to another region without having to be renamed.
No extended verification
Verifying the name for uniqueness is restricted to the immediate container without considering imports.
Name patterns can be defined for elements in the configuration via their stereotype. Regular expressions are used for this. Stereotypes inherit these name patterns and can then add requirements to these inherited naming constraints.
© 1986-2014 MID GmbH Nuremberg Germany. DIN EN 9001 certified. All rights reserved.