Difference between revisions of "Acceptance criteria"

From CNM Wiki
Jump to: navigation, search
Line 1: Line 1:
[[Acceptance criteria]] is the specification for a set of conditions that the [[product]] 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 acceptance criteria; otherwise, it fails.
+
[[Acceptance criteria]] (hereinafter, the ''Criteria'') is the specification for a set of conditions that the [[product]] 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.
  
 +
 +
==Test==
 +
:''Main wikipage: [[Acceptance test]]''
 +
 +
[[Acceptance test]] (alternatively known as [[user acceptance test]]; hereinafter, the ''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 test]]s.
 +
 +
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.
  
 
==Related coursework==
 
==Related coursework==

Revision as of 02:19, 29 December 2018

Acceptance criteria (hereinafter, the Criteria) is the specification for a set of conditions that the product 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.


Test

Main wikipage: Acceptance test

Acceptance test (alternatively known as user acceptance test; hereinafter, the 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.

Related coursework