Contains two glossaries of commonly-used terms. Select each letter for that part of the glossary.
Contains a list of the terminology used in requirements management, systems engineering and V&V (validation and verification), including terms used in model-based systems engineering (MBSE). The definitions of some of these terms are often the subject of debate. These are our definitions. If you disagree with any of them, please contact us to discuss! This list is not exhaustive.
Contains a list of the principal terminology used in Cradle. This list is not exhaustive.
A B C D E F G H I K L M N O P Q R S T U V W Y
N: |
|---|
|
Named User |
|
A type of licence which provides the basic ability to browse, create, modify and delete information in the database, subject to the project's own access rules to specific Linux or Windows usernames specified in the named_users file. |
|
Namespace |
|
A model namespace is data entered by a user or recorded in the project's schema or database, it is a value that Cradle generates when needed for display and reporting purposes. Model namespaces will be unique, for although it will be possible to have two models with the same name (albeit with different MUIDs), such models cannot both be children of the same parent model in the model hierarchy. |
|
Navigate |
|
The act of following one or more cross references that may exist in a Cradle project database between an initial item and a set of other items, to see which items the given item is linked to, prior to possibly inspecting these other items, or using them as a starting point for another navigation. |
|
Navigation |
|
A specification of which cross references are to be used, and how they are to be used to define the navigation selection in a second set of items, starting with the current-selection in a first set of items. |
|
Notation |
|
Notation in the Cradle context refers to the type of diagram used to depict the system. |