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
O: |
|---|
|
Object |
|
A thing in the real-world which is within the domain of a system to be built. Objects are things with certain properties such as the ability to distinguish between things of the same type and the possession of unique characteristics that differentiate one thing from another thing of the same type. Objects are represented in current object oriented methodologies as containing internal data not necessarily externally visible, together with operations that create and manipulate that data. Some object oriented methodologies focus predominately on the internal data whilst others focus predominately on the life history of the data and the external events that cause the data to pass through its life history. |
|
Object Oriented |
|
An adjective applied to any technique, or software product supporting a technique, or approach taken towards doing something based upon a technique, which focuses on the objects being manipulated rather than on the manipulations to be performed and the functionality to achieve it. By concentrating on the objects being manipulated, self contained packages (software classes) can be created for the objects that can be assembled to create larger objects and can be reused between systems. This approach is portrayed as being the opposite to a structured approach. |
|
Originator |
|
An attribute of a requirement that can be used to record the originator of the requirement as a person, organisation, or document. |
|
Owner |
|
When a user creates an item, he gains ownership of it. However, ownership can change throughout the lifecycle to be owned by another user, a team or the project. |