Skip to navigation Skip to main content
Logo CPRE, zur Startseite navigieren

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 RE@Agile Glossary supplements the CPRE Glossary with terms for Requirements Engineering in an agile environment.

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
CPRE Glossary
Expand all
Close all
Show only exam relevant
All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
No matching results found.
Reset filter
A
  • Acceptance

    The process of assessing whether a ↑system satisfies all its ↑requirements.

  • Acceptance criteria

    In agile: Criteria that the implementation of a ↑user story must satisfy in order to be accepted by the ↑stakeholders.

    Note:

    Acceptance criteria may also be written for ↑backlog items other than user stories.

  • Acceptance test

    A test that assesses whether a ↑system satisfies its ↑requirements.

    Note:

    Typically used by ↑customers to determine whether or not to accept a system.

  • Activity

    An action or a set of actions that a person or group performs to accomplish a ↑task .

  • Activity diagram

    A diagram type in ↑UML which models the flow of actions in some part of a ↑system including ↑data flows and areas of responsibility where necessary.

  • Activity model

    A ↑model of the flow of actions in some part of a ↑system .

  • Actor

    A person in some ↑role , a ↑system or a technical device in the context of a subject under consideration that interacts with that subject.

    Note:

    In RE, the subject under consideration typically is a ↑system . In testing, it may be a test ↑object .

  • Adequacy (of a requirement)

    The degree to which a ↑requirement expresses the ↑stakeholders' true and agreed desires and needs (i.e., those they had actually in mind when stating the requirement).

  • Agile


    1. In general:
    (a) Able to move quickly and easily.
    (b) Quick, smart, and clever.
    2. In software development: A development approach which builds a product ↑incrementally by dividing work into ↑iterations of fixed duration ( ↑timeboxes ).

    Note:

    Agile development is characterized by focusing on delivering a working product in each iteration, collaboration with ↑stakeholders with frequent feedback and adaptation of plans after each iteration based on feedback and changed ↑requirements.

  • Ambiguity

    The contrary of ↑unambiguity

  • Application domain

    Those parts of the real world that are relevant for determining the ↑context of a ↑system .

  • Artifact
  • Association

    In UML: A relationship between two ↑classes in a ↑UML ↑class model.

  • Attribute

    A characteristic property of an ↑entity or an ↑object .

Downloads

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.

Cookies

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

Cookies

  • We use the Google service ‘YouTube’, which provides media such as videos and also analyses user behaviour, among other things.

    Name: 1P_Jar, AEC, CONSENT, DV, NID
    Expiration: 1 month, 6 months, 2 years, 7 minutes, 6 month
    Provider: Google Ireland Ltd.