CIT3190

Proof of Concept

The Proof of Concept is a deliverable for the project that is intended to demonstrate to the client and the University that the solution proposed by the project team is feasible and correctly interprets the client’s requirements for the project.  The Proof of Concept may contain several components in the deliverable, including one or more of the following:
  1. An initial functional prototype of the system to be developed;
  2. A mock-up of the user interface of the system;
  3. An implementation of one or more of the key functions of the system;
  4. An analysis of requirements with detailed evaluation of feasibility;
  5. A report on the current status of the team’s analysis of the problem.
The Proof of Concept must be formally reviewed with the client before submission, and a record of the client’s agreement with the concept must be obtained.  The Proof of Concept is the first attempt to address the defined User Requirements, and should be derived from and traceable to the SURAC.
 
 
---------------------------------------
BACK
---------------------------------------
Original Author: Terry Rout 

 
 
 
 
 
 
 

Redesigned: 12 October, 1996 by Tracey Osborne 
Last Updated: 12 February, 1998 by Jo Orr
Send comments, errors and suggestions to Terry Rout, T.Rout@cit.gu.edu.au