Optimize Your Code

Proof of concept will lead to a quality solution

Many projects will require a Proof of Concept as a tool that in some cases, will determine the ultimate fate of the project as a whole. While the POC can be useful and sometimes indispensable, it seldom should be seen as a sole judgment of the final proposed product. In other words, it has limitations and can only provide information that must be considered in combination with other factors.

The chief purpose of a POC should be to gain insight into the basic performance aspects and characteristics of a specific software concept. This should be looked at as one of several bits of information that can serve as a gauge for the overall feasibility of the proposed product. It is important to keep expectations of a Proof of Concept in line with what its true function is.

In the most general sense, it is a prototype that represents the capabilities or possibilities of a final product. In a manner of speaking, it is a scale model that attempts to prove that a theory can be transformed into a reality, but it should not be expected to have the same complete functionality. It does not have to perform the task, but should be only required to prove that the performance objectives are practical.

Any results from the POC need to be analyzed and applied to the larger picture in regard to individual hardware and software stack configurations. Consideration of specific environments and different migration issues can be addressed, but not entirely resolved with scaled down version. While the intent is to prove the concept as completely as possible, success will depend on the integration of all other associated factors.

For example, as the Wilbur and Orville Wright perfected the first practical airplane, they reasonably chose to test their theories before they strapped themselves to the wing of an unproven flying machine. With small models in wind tunnels, they tested the concept of manned flight. Their version of the POC would not carry passengers, fly high above the earth or do anything but demonstrate that the design would fly.

Once again, the Proof of Concept is only valuable when it is understood as a tool for building the final product and not a complete representation of the project as a whole. As with the Wright brothers’ models, it is merely an indicator of the possibilities when used in conjunction with available engines, constructible wingspans and performance expectations.

Their POC served its purpose by giving them the data that showed that their objectives and ideas had enough merit to pursue further. It showed that the theory would operate in unison with other integral factors. The software Proof of Concept should only be expected to prove the same thing as the Wright wind tunnel tests did. It will prove that a project will fly and is not likely to crash.

Recommended Reading:

• 17/05/2010 -- Improving Design with the DRY principle: Don’t Repeat Yourself (0)
  The DRY, or Don't Repeat Yourself, principle is a software design concept that stresses the importance of not duplicating code. Besides the fact that [captio...
• 30/04/2010 -- Understanding and fixing Memory Leaks in Java – Part 1 (2)
  Do you see the dreaded ‘OutOfMemoryError’ while running your Java application? Does it crash every now and then? Does it have memory leaks? Is your [caption ...
• 27/04/2010 -- When throwing tin at your software problem doesn’t help! (0)
  The first thought that crosses the minds of many when they experience performance problems, is that their machine lacks enough power for the job at hand. While ...