- In modeling: The minimum and maximum number of ↑objects in a relationship.
- In mathematics: The number of elements in a set.
In ↑UML , the term multiplicity is used for cardinality.
The CPRE Glossary covers the core terms of Requirements Engineering. The definitions of the terms are generally given in English and have not been translated. This avoids any vagueness or room for interpretation that may result from translations. In addition, the terms of the CPRE Glossary are harmonized with the terminology of the ISTQB.
The online glossary corresponds to the version available for download and is the central reference for the CPRE Foundation Level and the CPRE Advanced Level. For the Advanced Level RE@Agile, a supplementary glossary that defines the terms for Requirements Engineering in the agile environment is available for download.
A committee of ↑customer and ↑supplier representatives that decides on ↑change requests .
The Change control board should not be confused with a change advisory board, which is a committee that evaluates change requests for a ↑system in operation and typically has no decision power.
A controlled way to effect or deny a requested change of a ↑work product.
In RE: A well-argued request for changing one or more ↑baselined ↑requirements.
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.
A diagrammatic representation of a ↑class model.
A model consisting of a set of ↑classes and relationships between them.
The parts of a ↑product line that are shared by all its members.
The adherence of a ↑work product to ↑standards, conventions, regulations, laws, or similar prescriptions.
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.
The degree to which a ↑work product conforms to regulations given in some ↑standard .
The degree to which a set of ↑requirements is free of contradicting statements.
A ↑requirement that limits the solution space beyond what is necessary for meeting the given ↑functional requirements and ↑quality requirements.
Context in the second meaning is also called the ↑system context.
The boundary between the ↑context of a ↑system and those parts of the ↑application domain that are irrelevant for the ↑system and its ↑requirements.
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.
The order in which a set of actions is executed.
The degree to which the information contained in a ↑work product is provably true.
In RE, correctness is sometimes used as a synonym for ↑adequacy , particularly when validating a ↑requirement rigorously against formally stated properties in the ↑context of a ↑system .
A person or organization who receives a ↑system , a ↑product or a ↑service . Also see ↑stakeholder .
A coarse description of the required capabilities of a ↑system from the ↑customer’s perspective.
A customer requirements specification is usually supplied by the customer.
The CPRE glossary is also available for download as PDF document in:
• Chinese (Mandarin)
• Portuguese (Brazil)