Difference between revisions of "Acceptance criteria"
(→Definitions) |
(→Related lectures) |
||
| Line 12: | Line 12: | ||
Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results. | Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results. | ||
| − | == | + | ==See also== |
| − | |||
| − | [[Category: Business Analysis]][[Category: Septem Artes Administrativi]][[Category: Articles]] | + | ===Related lectures=== |
| + | :*[[Verification vs Validation]]. | ||
| + | :*[[Business Analysis Quarter]]. | ||
| + | |||
| + | [[Category: CNM Cyber Placement]][[Category: Business Analysis]][[Category: Septem Artes Administrativi]][[Category: Articles]] | ||
Revision as of 04:57, 11 November 2020
Acceptance criteria (hereinafter, the Criteria) is the specification for a set of conditions that the marketable must meet in order to satisfy the customer. In Agile methodology, the product owner writes statements from the customer's point of view that explain how a user story or feature should work. In order for the story or feature to be accepted it needs to pass the Criteria; otherwise, it fails.
Definitions
According to the BABOK Guide (3rd edition),
- Acceptance criteria. Criteria associated with requirements, products, or the delivery cycle that must be met in order to achieve stakeholder acceptance.
Test
- Main wikipage: Acceptance test
Acceptance test is the derivative from the Criteria that verifies whether a feature is functional. The test has only two results: pass or fail. The Criteria usually include one or more acceptance tests.
Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
