The CPRE Glossary

The basis for successful RE is a common understanding of the terms used. The CPRE Glossary covers the core terms of Requirements Engineering—it is the central reference work across all CPRE modules and levels!

The glossaries are also available in various languages for download.

The CPRE Glossary: An overview of the most important Requirements Engineering terms
Please note that the definitions of terms in the glossaries are deliberately in English only in order to exclude any ambiguities or scope for interpretation that may result from translations.

in
No matching results found.
Reset filter
S
  • 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.

  • Scope (of a system development)

    The range of things that can be shaped and designed when developing a ↑system .

  • 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.

  • Semantics

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

  • Sequence diagram

    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.

  • Service

    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.

    Note:

    In systems engineering, software engineering and Requirements Engineering, services are typically provided by a ↑system for a ↑user or another system.

  • Software requirements specification

    A ↑requirements specification pertaining to a software ↑system .

    Abbreviation: SRS

  • Sprint

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

  • Stakeholder

    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.

  • Stakeholder requirement

    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.

  • Standard

    A formal, possibly mandatory set of regulations for how to interpret, develop, manufacture or execute something.

    Note:

    In RE, there are RE-relevant standards issued by ISO/IEC and IEEE.

  • State machine

    A ↑model describing the behavior of a ↑system by a finite set of states and state transitions. State transitions are triggered by events and can in turn trigger actions and new events.

  • State machine diagram

    A diagrammatic representation of a ↑state machine .

  • Statechart

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

  • Synonym

    A word having the same meaning as another word.

  • Syntax

    The rules for constructing structured signs in a ↑language .

  • System 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.

  • System requirement

    A ↑requirement pertaining to a ↑system .

  • System requirements specification
    Note:

    A system requirements specification is frequently considered to be a synonym for ↑requirements specification.

    Abbreviation: SyRS

Data privacy settings

This website may use cookies to ensure a good user experience. Further information can be found in our (cookieconsent-privacylink: Privacy Policy).

Technically necessary cookies help to make a website usable by enabling basic functions such as page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

This website may display content and media from external sites such as YouTube. Cookies from external sites are stored in the process.