Difference between revisions of "Validation"
(→Definitions) |
(→Practices) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
According to the [[ITIL Foundation 4e by Axelos]], | According to the [[ITIL Foundation 4e by Axelos]], | ||
:[[Validation]]. Confirmation that the system, product, service, or other entity meets the agreed [[specification]]. | :[[Validation]]. Confirmation that the system, product, service, or other entity meets the agreed [[specification]]. | ||
| + | |||
| + | ==Practices== | ||
| + | *[[Service validation and testing practice]] | ||
==See also== | ==See also== | ||
Latest revision as of 21:21, 28 December 2020
Validation (business analysis) is the process of checking that a deliverable is suitable for its intended use. See also requirements validation.
Definitions
According to the BABOK Guide (3rd edition),
- Validation (business analysis). The process of checking that a deliverable is suitable for its intended use. See also requirements validation.
According to the INCOSE Systems Engineering Handbook (4th edition),
- Validation. Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled (ISO/IEC/IEEE 15288) Note: Validation is the set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals, and objectives (i.e., meet stakeholder requirements) in the intended operational environment.
According to the ITIL Foundation 4e by Axelos,
- Validation. Confirmation that the system, product, service, or other entity meets the agreed specification.
