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.
A B C D E F G H I N O P Q R S T U V W
R: |
|---|
|
Requirement |
|
A statement of a customer need or objective, or of a condition or capability that a product must possess to satisfy such a need or objective. A property that a product must have to provide value to a stakeholder. |
|
Requirement Attribute |
|
Descriptive information about a requirement that enriches its definition beyond the statement of intended functionality. Examples include origin, rationale, priority, owner, release number, and version number. |
|
Requirements Allocation |
|
The process of apportioning system requirements among various architectural subsystems and components. |
|
Requirements Analyst |
|
The role on a project team who has lead responsibility for working with stakeholder representatives to elicit, analyse, specify, validate, and manage the project’s requirements. Also called a business analyst, system analyst, requirements engineer, and simply analyst. |
|
Requirements Development |
|
The process of defining a project’s scope, identifying user classes and user representatives, and eliciting, analyzing, specifying, and validating requirements. The product of requirements development is a requirements baseline that defines the product to be built. |
|
Requirements Engineering |
|
The domain that encompasses all project lifecycle activities associated with understanding a product’s necessary capabilities and attributes. Includes requirements development and requirements management. A sub-discipline of system engineering and software engineering. |
|
Requirements Management |
|
The process of working with a defined set of product requirements throughout the product’s development process and its operational life. Includes tracking requirements status, managing changes to requirements and versions of requirements specifications, and tracing individual requirements to other project phases and work products. |
|
Requirements Traceability Matrix |
|
A table that illustrates logical links between individual functional requirements and other types of system artifacts, including other functional requirements, use cases, architecture and design elements, code modules, test cases, and business rules. |
|
Retrospective |
|
A review in which project participants reflect on the project’s activities and outcomes with the intent of identifying ways to make the next project be even more successful. |
|
Risk |
|
A condition that could cause some loss or otherwise threaten the success of a project. |
|
Root Cause Analysis |
|
An activity that seeks to understand the underlying factors that contribute to an observed problem. |
Contains a list of the principal terminology used in Cradle. This list is not exhaustive.