AM2D Software Systems Consulting

Go to content

Main menu:


Proof of Concept (POC) and Prototyping implementation ...

Why carry out a POC?
    • Reduce risk of unknown or unvalidated tchnologies
    • Provide a level of confidence for proposed solutions
    • Provide a 'what if ?' scenario test environment
    • Reduce risk of requirement changes in later development phases
    • Eliminate 'gaps' between requirement and architecture

A POC is a demonstration in principle, a quantification of the feasibility, and the verification that a concept or theory has a potential of being realised.
It is not (usually) a complete solution; in most cases will explore some functional aspect(s), (but not all) of the intended architecture/design.

A proof of concept or prototype can be used to evaluate an important and/or high risk element in a proposed solution;
it provides a low risk evaluation alternative before committing to the use of a particular technology, architecture or design within the system solution.
It enables us to confront evaluate an provide solutions to fundamental problems at an early stage in the development process, learning from mistakes before they have a major impact on the system. Hence reducing risk, saving time and investment money.

 POC implementation ...
In order to be of value a POC must be carefully designed and executed. The goals, scope evaluation and success/failure criteria must be rigorously defined.

MD² POC Solution Services:

  • Prerequisite planning:
    1. Define the purpose, goals, objectives and scope
    2. Outline the evaluation and testing methods
    3. Determine the most suitable implementation environment i.e. coding language, Operating System, etc.
    4. Clearly define each (if multiple sub-sections exist) study/test to be executed within the POC 
    5. Define the key decisions to be made at the conclusion of the POC
    6. Define POC stakeholders and participants
    7. Establish baseline, interim, and final evaluation studies
    8. Establish success/failure criteria for the POC, with input from all stakeholders
    9. Outline the benefits of conducting the POC, and the risks of not doing so.

  • POC execution, analysis, and documentation:
    1. Establish a clear well defined baseline state
    2. Execute the POC according to the testing methods defined in the prerequistite planning
    3. Perform required analyses on recorded results 
    4. Validate and verify results and analyses
    5. Document results
    6. iterate execution, analysis and document process cycle through any defined interim states to final evaluation study state

  • Presentation of results and conclusions:
    1. Prepare results for presentation
    2. Present results and conclusions to client stakeholders 
    3. If required, conduct post-POC evaluation/analysis.
Back to content | Back to main menu