A template for the syntactic structure of a phrase that expresses an individual ↑requirement or a ↑user story in ↑natural language. ( ↑requirements template )

A popular ↑process framework for ↑agile development of a ↑system .

The meaning of a sign or a set of signs in a ↑language .

A diagram type in ↑UML which models the interactions between a selected set of ↑objects and/or ↑actors in the sequential order in which those interactions occur.

The provision of some ↑functionality to a human or a ↑system by a provider (a system, organization, group or individual) that delivers value to the receiver.

The capability of a ↑system to achieve an acceptable level of probability that the system, under defined conditions, will not reach a state in which human life, health, property, or the environment is endangered.

The degree to which a ↑system protects its data and resources against unauthorized access or use and secures unobstructed access and use for its legitimate ↑users.

An excerpt from a ↑work product , containing only those parts one is currently interested in.

A ↑requirements specification pertaining to a software ↑system .

Abbreviation: SRS

1. As a work product: A systematically represented description of the properties of an ↑item (a ↑system , a device, etc.) that satisfies given criteria.
   
2. As a process: the process of specifying ( ↑eliciting , documenting and ↑validating ) the properties of an ↑item .

A ↑technique that specifies test cases and ↑requirements for a ↑system by providing examples of how the system should behave.

An artificial ↑language that has been created for expressing ↑specifications .

In agile development: A task aimed at gaining insight or gathering information, rather than at producing a ↑product ↑increment .

A structured set of signs for expressing and communicating information.

An ↑iteration in ↑agile development, particularly when using ↑Scrum.

A set of ↑product backlog items that have been selected to be implemented in the current ↑sprint .

A person or organization who influences a ↑system’s ↑requirements or who is impacted by that system.

A ↑requirement expressing a ↑stakeholder desire or need.

A ↑state machine having states that are hierarchically and/or orthogonally decomposed.

The order in which a set of actions is executed.

A two-dimensional arrangement of ↑user stories .

A series of sketches or pictures that visualize the execution of a ↑scenario .

An approach for specifying the ↑functionality of a system based on a hierarchy of ↑data flow diagrams. Data flows as well as persistent data are defined in a data dictionary. A ↑context diagram models the sources of incoming and the destinations of outgoing ↑data flows.

A word having the same meaning as another word.

The rules for constructing structured signs in a ↑language .

1. In general: A principle for ordering and structuring.
2. In engineering: A coherent, delimitable set of elements that – by coordinated action – achieve some purpose.

A ↑requirements specification pertaining to a ↑system .

A ↑requirement pertaining to a ↑system .

The boundary between a ↑system and its surrounding ↑context .

The part of a ↑system’s environment that is relevant for the definition as well as the understanding of the ↑requirements of a ↑system to be developed.

1. In general: A description of a potential sequence of events that lead to a desired (or unwanted) result.
   
2. In RE: An ordered sequence of interactions between partners, in particular between a ↑system and external ↑actors . May be a concrete sequence (instance scenario) or a set of potential sequences (type scenario, ↑use case ).