Difference between revisions of "Proof of concept"
(Created page with "Proof of concept is a model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflo...") |
|||
| Line 4: | Line 4: | ||
According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
:[[Proof of concept]]. A model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflows ultimately used by the stakeholders. | :[[Proof of concept]]. A model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflows ultimately used by the stakeholders. | ||
| + | According to the [[ INCOSE Systems Engineering Handbook (4th edition)]], | ||
| + | :[[Proof of concept]]. A naïve realization of an idea or technology to demonstrate its feasibility. | ||
| − | [[Category: Business Analysis]][[Category: Articles]] | + | [[Category: Business Analysis]][[Category: Articles]][[Category: Systems Engineering]] |
Latest revision as of 21:08, 20 July 2020
Proof of concept is a model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflows ultimately used by the stakeholders.
Definitions
According to the BABOK Guide (3rd edition),
- Proof of concept. A model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflows ultimately used by the stakeholders.
According to the INCOSE Systems Engineering Handbook (4th edition),
- Proof of concept. A naïve realization of an idea or technology to demonstrate its feasibility.
