Synonym: Kontrollfluss
The order in which a set of actions is executed.
Das CPRE Glossar
Ein gemeinsames Verständnis der verwendeten Begriffe ist die Grundlage für erfolgreiches RE. Das CPRE Glossar umfasst die Kernbegriffe des Requirements Engineering - es ist das zentrale Nachschlagewerk über alle CPRE Module und Ebenen hinweg! Das RE@Agile Glossar ergänzt das CPRE Glossar durch Begriffe für das Requirements Engineering im agilen Umfeld.
Die Glossare sind in verschiedenen Sprachen auch zum Download verfügbar.
Das CPRE Glossar: Die wichtigsten Begriffe des Requirements Engineering im Überblick
Bitte beachten Sie, dass die Begriffsdefinitionen in den Glossaren bewusst nur auf Englisch existieren, um Unschärfen oder Interpretationsspielraum, die aus Übersetzungen resultieren können, auszuschließen.
Zu dieser Filterung wurden keine Einträge gefunden.
Filter zurücksetzen
S
Filter zurücksetzen
-
SteuerflussControl flow
-
SpracheLanguage
A structured set of signs for expressing and communicating information.
Note:Signs are any elements that are used for communication: spoken or written words or expressions, symbols, gestures, sounds, etc.
-
SatzschablonePhrase template
A template for the syntactic structure of a phrase that expresses an individual ↑requirement or a ↑user story in ↑natural language. ( ↑requirements template )
-
Sicherheit (im Sinn von Nutzungssicherheit)Safety
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.
Note:Safety ↑requirements may be stated as ↑quality requirements or in terms of ↑functional requirements.
-
SzenarioScenario
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 ). -
ScrumScrum
-
Sicherheit (im Sinn von Informationssicherheit)Security
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.
Note:Security requirements may be stated as ↑quality requirements or in terms of ↑functional requirements.
-
SemantikSemantics
The meaning of a sign or a set of signs in a ↑language .
-
SequenzdiagrammSequence diagram
-
ServiceService
Synonym: Dienst
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.
-
Software-AnforderungsspezifikationSoftware requirements specification
Synonym: Pflichtenheft
A ↑requirements specification pertaining to a software ↑system .
Abbreviation: SRS -
SpezifikationSpecification
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 .Note:A specification may be about required properties ( ↑requirements specification ) or implemented properties (e.g., a technical product specification).
-
Spezifikation durch BeispieleSpecification by example
A ↑technique that specifies test cases and ↑requirements for a ↑system by providing examples of how the system should behave.
-
SpezifikationsspracheSpecification language
An artificial ↑language that has been created for expressing ↑specifications .
-
SpikeSpike
Synonym: Erkundung
In agile development: A task aimed at gaining insight or gathering information, rather than at producing a ↑product ↑increment .
-
SprintSprint
An ↑iteration in ↑agile development, particularly when using ↑Scrum.
-
Sprint-BacklogSprint backlog
Synonym: Sprint-Auftragsbestand
A set of ↑product backlog items that have been selected to be implemented in the current ↑sprint .
-
StakeholderStakeholder
Synonym: Interesseneigner
A person or organization who influences a ↑system’s ↑requirements or who is impacted by that system.
Note:Influence can also be indirect. For example, some stakeholders may have to follow instructions issued by their managers or organizations.
-
StakeholderanforderungStakeholder requirement
Synonym: Interesseneigneranforderung
A ↑requirement expressing a ↑stakeholder desire or need.
Note:Stakeholder requirements are typically written by stakeholders and express their desires and needs from their perspective.
-
StatechartStatechart
A ↑state machine having states that are hierarchically and/or orthogonally decomposed.
-
Story (in einem RE-Kontext)Story (in an RE context)
-
Story MapStory map
Synonym: Story-Landschaft
A two-dimensional arrangement of ↑user stories .
Note:A story map helps understand the ↑functionality of a ↑system , identify gaps and plan releases.
-
StoryboardStoryboard
A series of sketches or pictures that visualize the execution of a ↑scenario .
-
Strukturierte AnalyseStructured Analysis
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.
-
SynonymSynonym
A word having the same meaning as another word.
-
SyntaxSyntax
The rules for constructing structured signs in a ↑language .
-
SystemSystem
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.Note:1. A system may comprise other systems or ↑components as sub-systems.
2. The purposes achieved by a system may be delivered by
- deploying the system at the place(s) where it is used,
- selling/providing the system as a ↑product to its ↑users,
- having providers who offer the system’s capabilities as ↑services to users.
3. Systems containing both software and physical ↑components are called cyber-physical systems.
4. Systems spanning software, hardware, people and organizational aspects are called socio-technical systems.
Important: In all definitions referring to system in this glossary, system is an umbrella term which includes
- ↑products provided to customers,
- ↑services made available to customers,
- other work products such as devices, procedures or tools that help people or organizations achieve some goal,
- system ↑components or ↑compositions of systems. -
SystemgrenzeSystem boundaryNote:
1. The system boundary delimits the system as it shall be after its implementation and deployment.
2. At the system boundary, the external interfaces between a ↑system and its ↑context have to be defined.
3. The system boundary frequently coincides with the ↑scope of a ↑system (which denotes the range of things that can be shaped and designed). However, this is not always the case: there may be components within the system boundary that have to be re-used as they are (i.e., cannot be shaped nor designed), while in the system context there may be things that can be re-designed when the system is developed (which means that they are in scope). -
SystemkontextSystem 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.
-
SystemanforderungSystem requirement
A ↑requirement pertaining to a ↑system .
-
System-AnforderungsspezifikationSystem requirements specification
Synonym: Pflichtenheft
A ↑requirements specification pertaining to a ↑system .
Note:A system requirements specification is frequently considered to be a synonym for ↑requirements specification.
Abbreviation: SyRS -
SichtView
An excerpt from a ↑work product , containing only those parts one is currently interested in.
Note:A view can abstract or aggregate parts of the work product.