In agile: Criteria that the implementation of a ↑user story must satisfy in order to be accepted by the ↑stakeholders.
Acceptance criteria may also be written for ↑backlog items other than user stories.
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.
In agile: Criteria that the implementation of a ↑user story must satisfy in order to be accepted by the ↑stakeholders.
Acceptance criteria may also be written for ↑backlog items other than user stories.
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.
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 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.
The CPRE glossary is also available for download as PDF document in:
• Chinese (Mandarin)
• Dutch
• English
• French
• German
• Italian
• Persian
• Polish
• Portuguese (Brazil)
• Russian
• Swedish
• Spanish