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
L: |
|---|
|
Latency |
|
Measure of the time that elapses between the occurrence of a stimulus in a system’s environment and the arrival at a specified point in the system of data that relates to the stimulus. |
|
Latest |
|
Highest version and draft instance of items. |
|
Level |
|
A selection criterion for items, based on the position of an item within a hierarchy of items of the same type. |
|
Licence File |
|
A file containing the details of the numbers of each type of connection and tool licence that a customer has purchased. It is the permanent embodiment of a security code, that is read by the CDS and Cradle tools when they start to determine licence information. |
|
Lifecycle Reuse |
|
Refers to the goal of achieving reuse of intellectual effort not simply in the context of software source code but rather in the entire lifecycle of formal requirements through analysis and design to the detailed implementation expressed as circuit diagrams or actual software. Current object oriented techniques are focused on software reuse, but the software typically represents under 10% of the reusable intellectual effort if all earlier parts of the lifecycle culminating in the software are also reusable. |
|
Lightweight Directory Access Protocol |
|
An Internet protocol (LDAP) that e-mail and other programs use to look up information from a server. |
|
Link |
|
There are two types of links in Cradle. These are physical links which are defined cross references between items or pseudo links which are identified by the numbering of the items. |
|
Link Attribute |
|
Each cross reference that is created between items in the database contains 16 attributes, each with a value of up to 200 characters. You can use these attributes to store data inside the cross reference, for example to explain or justify the link that is created by the cross reference between the items that it connects. When searching the database, you can choose to follow cross references that contain specific link values inside some or all of their attributes. To ensure that searches are consistent, you may want to restrict the values in cross reference attributes to a specific set. |
|
Link Group |
|
A link group is a named set of link types. If you ask Cradle to search based on a link group, Cradle searches using all of the link types in the link group. When searching the database, following cross references, Cradle only follows those cross references which are tagged with one of the link types in the link group. |
|
Link Rule |
|
Link rules allow you to control the creation of physical cross references between items. |
|
Link Settings |
|
Allows you to define the re-entrancy of cross references when created. |
|
Link Type |
|
Each cross reference has a link type. Link types can be used to distinguish between different types of cross reference. Link types have 16 character names. By default, cross references are created with link types of all spaces. You can create any number of link types. Each link type has a name, and an associated colour. The colours are used when cross references are drawn in Hierarchy Diagrams (HIDs). You can create more than one cross reference between a pair of items, provided that each has a different link type. |
|
List Reference |
|
An ambiguous reference to the identities of one or more items of information within Cradle that contains a wildcard expression. For items identified by names, a list reference contains a complete or partial name followed by a wildcard. For items identified by numbers (where numbers are normally textual strings containing digits, dots, and (for system notes and requirements) arbitrary other characters) a list reference contains a complete or partial number followed by a wildcard. The wildcards are . meaning followed by one or more characters, * meaning followed by zero or more characters, + meaning items from here onwards, and - meaning up to this item. |
|
Load Scenario |
|
A load scenario is a sequence of environment loads that is used to perform a sequence of Performance Analyses of a given state model. A load scenario consists of a name and an arbitrarily large sequenced set of environment load names. One performance analysis is performed for each environment load in the load scenario. The results for all such analyses are held within the PERF DATA frames of the data definitions, and specifications of the symbols on the diagrams within the state model. Each set of the analyses’ results are identified with an identity that distinguishes them from all others, such that the results from alternative environment loads in the load scenario can be readily compared. |
|
Lower |
|
If two or more objects of the same type are selected, the Lower operation will merge the symbols and produce a new diagram that contains the originally selected symbols, and the symbols' inputs and outputs. |