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
A: |
|---|
|
Acceptance Criteria |
|
Conditions that a software product must satisfy to be accepted by a user, customer, or other stakeholder. |
|
Activity Diagram |
|
An analysis model that shows a dynamic view of a system by depicting the flow from one activity to another. Similar to a flowchart. |
|
Actor |
|
A person, software system, or hardware device that interacts with a system to achieve a useful goal. Also called a user role. |
|
Alternative Flow |
|
A scenario in a use case that leads to success (accomplishing the actor’s goal) but involves a variation from the normal course in the specifics of the task or of the actor’s interaction with the system. Also known as an alternative course. |
|
Analysis, Requirements |
|
The process of classifying requirements information into various categories, evaluating requirements for desirable qualities, representing requirements in different forms, deriving detailed requirements from high-level requirements, negotiating priorities, and so on. |
|
Architecture |
|
The structure of a software-containing system, including the software and hardware components that make up the system, the interfaces and relationships between those components, and the component behaviours that are visible to other components. |
|
Assumption |
|
A statement that is believed to be true in the absence of proof or definitive knowledge. |
Contains a list of the principal terminology used in Cradle. This list is not exhaustive.