Difference between revisions of "Validation"
(Created page with "Validation (business analysis) is the process of checking that a deliverable is suitable for its intended use. See also requirements validation. ==Definitions== Accor...") |
|||
| Line 4: | Line 4: | ||
According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
:[[Validation]] ([[business analysis]]). The process of checking that a deliverable is suitable for its intended use. See also requirements validation. | :[[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. | ||
| − | [[Category: Business Analysis]][[Category: Articles]] | + | [[Category: Business Analysis]][[Category: Articles]][[Category: Systems Engineering]] |
Revision as of 21:41, 20 July 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.
