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

    Synonym: bug, fault

    An imperfection or deficiency in a ↑work product that impairs its intended use.

  • Design

    1. A plan or drawing produced to show how something will look, function or be structured before it is made.

    2. The activity of creating a design.

    3. A decorative pattern [This meaning does not apply in the software engineering ↑domain ].

    Note:

    1. In software product development, we distinguish between creative design which shapes the look and feel of the product, i.e., its perceivable form, function and quality, and technical design (also called software design) which determines the inner structure of the product, in particular the software architecture.
    2. The creative design of products is also called product design.
    3. The creative design of digital solutions is called digital design.

  • Domain

    A range of relevant things (for some given matter); for example, an ↑application domain .

  • Domain model

    A ↑model describing phenomena in an ↑application domain .

    Note:

    1. In RE, domain models are created with the intention to understand the ↑application domain in which a planned ↑system will be situated.

    2. Static domain models specify (business) objects and their relationships in a ↑domain of interest.

    3. Domain story models specify visual stories about how actors interact with devices, artifacts and other items in a ↑domain .

  • Domain requirement

    A ↑domain property in the ↑context of a ↑system that is required to hold.

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.

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