A BHMI proof of concept logically fits between a feasibility study and a quick turn pilot. It is intended to successfully demonstrate that a limited set of technical functions could plausibly support a complete software application. However, it is also expected to demonstrate these functions within a broader application context. Several attributes of a proof of concept that distinguish it from a feasibility study or quick turn pilot are noted below:
- Effort is focused on a limited set of technical functions that could collectively underpin a complete application; a proof of concept has greater scope than a feasibility study.
- Reuse of code as part of developing a complete application is not a significant objective; the primary purpose of a proof of concept is to validate that certain functions are collectively doable.
- Creating a miniature application like a quick turn pilot is not a primary objective; a proof of concept is intended to demonstrate that a collection of technical functions could plausibly support a complete software application.
Like the other BHMI Software Consulting options, a proof of concept is intended to limit the risk of developing a complete software application until certain proof points have been met. By confirming that certain technical goals are attainable before embarking on a full software development cycle, you can significantly increase the probability of overall project success.