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
S: |
|---|
|
Scenario |
|
A description of a specific interaction between a user and a system to accomplish some goal. An instance of usage of the system. Often presented in the form of a story. |
|
Scope |
|
The portion of the ultimate product vision that the current project will address. The scope draws the boundary between what’s in and what’s out for the project. |
|
Scope Creep |
|
A condition in which the scope of a project continues to increase, typically in an uncontrolled fashion, throughout the development process. |
|
Sequence Diagram |
|
An analysis model that shows the order in which messages pass in a system or the chronological sequence of steps that take place in an activity and the entities or classes involved in the activity. |
|
Software Development Life Cycle |
|
A sequence of activities by which a software product is defined, designed, built, and verified. |
|
Software Requirements Specification |
|
A collection of the functional and non-functional requirements for a software product. |
|
Specification, Requirements |
|
The process of documenting a system’s requirements in a structured, shareable, and manageable form. Also, the product from this process. (see also software requirements specification above). |
|
Stakeholder |
|
A person, group, or organisation that is actively involved in a project, is affected by its outcome, or can influence its outcome. |
|
Statechart Diagram |
|
An analysis model that shows the sequence of states that an object in a system goes through during its lifetime in response to specific events that take place. Similar to a State Transition Diagram. |
|
State-Transition Diagram |
|
An analysis model that shows the various states that a system can be in, or the statuses that an object in the system can have, and the permitted transitions that can take place between states. Similar to a Statechart Diagram. |
|
Subject Matter Expert |
|
An individual who has extensive experience and knowledge in a domain and who is recognised as an authoritative source of information about the domain. |
|
System Requirement |
|
A top-level requirement for a product that contains multiple sub-systems, which could be all-software or software and hardware. |
Contains a list of the principal terminology used in Cradle. This list is not exhaustive.