• Blog
  • About Us
  • Our portfolio
  • Contact Us
​R-STYLE LAB BLOG

What is PoC in Software Development & Why do You Need it?

1/23/2017

0 Comments

 
Picture
​The Proof of Concept term has been all over the Web recently. It is often mentioned in connection with the Internet of Things – the global connected environment where gadgets collect data and exchange it over a network. What is PoC and does it exist outside the IoT realm? Read on to find out!

The whats and whys of Proof of Concept in software development
Proof of Concept (or PoC for short) is the evidence that a certain system or device can be implemented in the real world and become a commercial success. PoC is similar to prototypes (chunks of software that perform functions of the future system or gadgets built with off-the-shelf solutions like Raspberry PI and Adruino), although no deliverables are represented at the stage. The document often provides the description of business processes, their objectives and participants and demonstrates that the proposed solution meets certain business requirements.
In other words, creating PoC is a great way to find a solution to a technical problem, make sure it really works and evaluate market demand for a product.
With Proof of Concept, you can:
  • Test viability and usability of a product;
  • Check its compatibility with the available servers and databases;
  • Measure ROI;
  • All of the above.
When do you need Proof of Concept in custom software development?
You want to retrieve data from enterprise apps written in different programming languages. Enterprise application integration (EAI) is often challenging and involves major recoding; does it mean you have to create Proof of Concept? It does – as long as you implement new APIs or libraries which have never been used for this purpose.
In case similar EAI solutions exist on the market, Proof of Concept is replaced with thorough research. You address a custom software development company that analyzes the tech stack of your enterprise applications and finds the right middleware. Thus, there’s no coding done (not before you initiate the EAI process). Provided you have an in-house IT department, R&D facilities and relevant expertise, you can even conduct research on your own and simply pass the requirements to your vendor.
It’s different with IoT. A couple of months ago we published a comprehensive article on IoT product development costs, citing novelty of an IoT solution as the key reason to prepare Proof of Concept.
According to Pavel Shylenok, CTO at R-Style Lab, it makes sense to start with a POC when a market-ready product costs are considerably higher than the PoC itself. Some new ideas – like cutting-edge hardware sensors or trendy Home Automation systems –might just not be feasible due to technology limitations (it’s not there yet). Despite of the “generally it works” state, high latencies, low precision, high energy consumption (whichever applies) won’t allow POC to reach market-ready level.
When it comes to IoT solutions, PoC results most often answer the following questions:
  • Does it work?
  • Would I use it?
  • Does anyone need it?
Here’s an example. The global Home Automation market is expected to top $ 78 billion by 2022; it’s no wonder so many IoT startups want to get a share of the pie! Besides high dev costs (a complex Smart Home system might cost as much as $ 5 million to build), there’s a huge obstacle that might keep you away from success.
Home Automation systems often employ different sensors connected with some AI logic. While each sensor can work fine when used independently, combining them can be tricky due to mutual interference or high power consumption or low/unreliable performance. Before your vendor creates PoC, the questions we’ve mentioned above cannot be answered.
Picture
Same with IoT healthcare solutions. Once we were approached by a US company that manufactures intervertebral prosthetic gadgets. Each of these devices has a unique identifier, so they wanted to build a custom machine vision system to automatically decode X-ray images. Although the R-Style Lab team implemented various APIs and technologies to reach the goal, the accuracy of the image recognition software staggered around 70%. In order to achieve better accuracy, we needed 4K resolution images which are not produced by modern X-ray machines, so the project was postponed for an indefinite period of time.
4 steps to PoC success
  • Appoint champions. Champions are your vendor’s employees who ensure the success of your project and define its objectives. A team of champions typically includes a person who gives the green light to a project, process specialist who clarifies its scope, representative of the IT department, accountant executive responsible for human and tech resources management and tech expert with a deep knowledge of the industry and its business processes. Make sure your vendor possesses the required expertise, resources and facilities to handle the task and ensure smooth project execution;
  • Measure success. What is your goal and what are you doing to achieve it? What’s the real value of your product? Is there a system/solution you can compare your product to? What happens if your vendor fails to deploy it? How are you going to maintain the solution when it goes life? You have to measure success at every stage of PoC development and manage the available resources accordingly;
  • Align expectations. While creating PoC, both you and your tech team discover new capabilities of a software system, so you have to be open to making changes to the scope, prioritizing tasks and adding new developers on board (even if it translates into budget extensions);
  • Provide and collect feedback. Software development companies gather customer feedback to refine products through testing and prototyping. Quantitative feedback (including projected user adoption and success vs failure rates) helps you determine whether you’re moving in the right direction – and whether the project is actually worth your time and money.
Working on an innovative solution (be it a complex enterprise application or next generation connected gadget) requires a lot of research and planning. The more time you spend on validating your idea, the better your results will be. Provided you address a reliable IoT app development or IT system integration company, you’re most likely to succeed.
0 Comments

Your comment will be posted after it is approved.


Leave a Reply.

    Archives

    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016

    Categories

    All

Powered by Create your own unique website with customizable templates.
  • Blog
  • About Us
  • Our portfolio
  • Contact Us