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
U: |
|---|
|
Unique Identifier |
|
The item's Unique ID (UID). |
|
Unsubmit |
|
This allows a user with the necessary privileges to take an item that has been submitted for review and cancel that submission. |
|
Use Case |
|
A generic description of an entire transaction involving several objects. A single use case can contain many scenarios. |
|
Use Case Diagram - Non SysML |
|
A Use Case Diagram (UCD) is a diagram that is used to show the use cases of a system and the external actors that use them. |
|
Use Case Diagram - SysML |
|
Used to define operations in terms of how a system or other entity might be used by external entities (i.e. actors) to accomplish a set of goals/missions. Each use case is associated with a set of operational scenarious describing the desired activities to be performed. A scenario can be defined using an activity diagram. |
|
User Access List |
|
Contains the User Access List for a CDS. |
|
User Configuration File |
|
A system configuration file provided for System Administrators to use to force specified usernames in specified Cradle projects to be read-only or read-write users when they login to Cradle. |
|
User Control File |
|
Contains records that define the access modes for specific usernames in specific projects. |
|
User Definition File |
|
A directory structure that contains numerous sub-directories for various types of personal setups and definitions, each sub-directory storing an arbitrarily large number of files holding the user’s personal definitions for the corresponding type of setup or definition data. |
|
User List |
|
User lists are a set/group of users which are used in workflows. They allow projects to control who will review information. |
|
User Preference |
|
User Preferences allow you to control settings that are used to customise your WorkBench environment and set default options |
|
User Profile |
|
The set of information that describes the characteristics of a particular Cradle user. Each project maintains a User Register containing details of all User Profiles. A User Profile records details for each username (must be unique within the project) of the associated password, team name, security clearance, set of privileges, set of skills, and a set of tool access rights. |
|
User Register |
|
The set of User Profiles for a Cradle project, held in that project’s project database. |
|
User Setup |
|
The User Setup tool is used to create, view, amend and delete users in a project. |
|
User Type |
|
User types are used to provide customised definitions for particular groups of users. A list of user types is defined for the project. |
|
Username |
|
The identity of a user in a Cradle project, and the ownership value of all information created and owned by that user. Usernames are up to eight characters (alphanumerics, spaces, and underscores) and are case-insensitive. |
|
Utilities |
|
Cradle provides a number of utilities that allow you to check the integrity of the Cradle database. It is strongly advised that no additional users are logged into the database when running these utilities |