Proof of Concept

Parent Previous Next

Proof of Concept


1. Information about the Deliverable

Identifier:

eaM.d124.pocd.10

Date Last Reviewed:

08 October 2007

Description:

Create a Proof of Concept document.  The proof of concept is usually considered a milestone on the way to a fully functioning prototype.

Deliverable Type:

Document

Effort:

Days



2. How to construct the deliverable using the eaMindShare CE approach

Phase

High level Action

A. Engagement

Orientate with current situation

B. Calibration

Special notice of

C. Discovery

Discover what needs to be proved

D. Envisioning

Envision dependencies and create POC

E. Validation

Iteratively Refine

F. Realisation

Make POC available



3.  Template/s & Samples

View

Template

Notice


Export Views

Map View

Template/s are disabled for eaMindShare Community Edition due to document sizes.  Rather use  eaMindShare Professional  Edition  and/or eaMindShare Workgroup Edition if you want to access the templates.


Ideally export and further refine in:



4. Additional Information

In software development "proof of concept" (often abbreviated to PoC) is often incorrectly used interchangeably with "proof of technology" (PoT) or "pilot project". The three terms refer to processes with different objectives and different participant roles and are therefore not synonymous. A proof of concept is a partial solution to a business problem intended to prove the viability of the business concept. A proof of concept may involve a small number of users acting in a business (non-IT) role using the system to establish that it satisfies some aspect of the requirements for the complete solution.

The proof of concept implementation will not affect business operational data although it may integrate with existing business systems to some extent. By contrast, the objective of a "proof of technology" is to determine the solution to some technical problem such as how two systems might be integrated or that a certain throughput can be achieved with a given configuration. No business users need be involved in a proof of technology. The third term, "pilot project", refers to an initial roll out of a system into production targeting a limited scope of the intended final solution. The scope may be limited by the number of users which can access the system or by the business categories affected or the business partners involved or other restrictions as appropriate to the domain. The intent of a pilot project is to validate that the system is working in production as designed and limiting the business exposure if it is not.







Created with the Personal Edition of HelpNDoc: Create HTML Help, DOC, PDF and print manuals from 1 single source