Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Acceptance Criteria ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Acceptance Criteria define the conditions that a subject must satisfy for an authorized actor or process to accept it for a specified purpose. | ||
| + | |||
| + | The subject may include: | ||
| + | |||
| + | * An [[public: | ||
| + | * An [[public: | ||
| + | * An [[public: | ||
| + | * A [[public: | ||
| + | * A deployment | ||
| + | * A release | ||
| + | * A test result | ||
| + | * A service | ||
| + | * A transition between [[public: | ||
| + | |||
| + | Acceptance Criteria may specify: | ||
| + | |||
| + | * Required characteristics | ||
| + | * Permitted values | ||
| + | * Prohibited conditions | ||
| + | * Quantitative thresholds | ||
| + | * Required test results | ||
| + | * Required evidence | ||
| + | * Applicable policy conditions | ||
| + | * Required approvals | ||
| + | * Required compliance outcomes | ||
| + | |||
| + | Acceptance Criteria differ from verification procedures: | ||
| + | |||
| + | * Acceptance Criteria define the conditions that must be satisfied | ||
| + | * Verification procedures define how an evaluator determines whether those conditions are satisfied | ||
| + | |||
| + | Acceptance Criteria also differ from requirements: | ||
| + | |||
| + | * A requirement states an obligation | ||
| + | * Acceptance Criteria define the conditions used to determine whether a result is acceptable for a specified purpose | ||
| + | |||
| + | A requirement may incorporate or reference Acceptance Criteria. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //criteria that define the conditions a subject must satisfy for acceptance for a specified purpose// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Acceptance Criteria should be: | ||
| + | |||
| + | * Specific | ||
| + | * Observable | ||
| + | * Measurable when measurement is applicable | ||
| + | * Testable | ||
| + | * Traceable to the applicable requirement, | ||
| + | |||
| + | Satisfaction of Acceptance Criteria establishes acceptance only for the specified purpose and context. | ||
| + | |||
| + | Acceptance does not necessarily establish that the subject is approved for release, authorized for deployment, compliant with every applicable policy, or suitable for another purpose. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | Acceptance Criteria for an Infrastructure Environment require the environment to contain the specified compute, storage, and network resources, satisfy the applicable security settings, and pass the identified connectivity tests. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||