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
C
  • Change request

    In RE: A well-argued request for changing one or more ↑baselined ↑requirements.

  • Class

    A representation of a set of ↑objects of the same kind by describing the structure of the objects, the ways they can be manipulated and how they behave.

  • Class diagram

    A diagrammatic representation of a ↑class model.

  • Class model

    A model consisting of a set of ↑classes and relationships between them.

  • Configuration

    A consistent set of logically coherent ↑items. The items are individually identifiable ↑work products or parts of work products in at most one ↑version per item.

  • Conformity

    The degree to which a ↑work product conforms to regulations given in some ↑standard .

  • Consistency (of requirements)

    The degree to which a set of ↑requirements is free of contradicting statements.

  • Constraint (in RE)

    A ↑requirement that limits the solution space beyond what is necessary for meeting the given ↑functional requirements and ↑quality requirements.

  • Context boundary

    The boundary between the ↑context of a ↑system and those parts of the ↑application domain that are irrelevant for the ↑system and its ↑requirements.

    Note:

    The context boundary separates the relevant part of the environment of a system to be developed from the irrelevant part, i.e., the part that does not influence the system to be developed and, thus, does not have to be considered during Requirements Engineering.

  • Context model

    A ↑model describing a ↑system in its ↑context .

  • Customer requirements specification

    A coarse description of the required capabilities of a ↑system from the ↑customer’s perspective.

    Note:

    A customer requirements specification is usually supplied by the customer.

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.