Solution Design Proof of Concept

The purpose of a Proof of Concept (PoC) is to test a given software, system or configuration in a predefined environment. In this process the following activities are required to measure the success of the PoC.

Step 1: All functional and non-functional requirements are documented in an Excel spreadsheet. The functional requirements are specified from a user story perspective, eg: All users should be able to log in to the system with the use of single sign-on when entering the system from a domain joined computer. All non-functional requirements should be specified from a business or security perspective, eg: The system is built and quality assured by the ISO 270001 standards. For every requirement, the definition of success needs to be defined. 

Step 2: Based on the requirements in step 1, a very high level design document (1-3 pages) are created to specify the solution to be tested. 

Step 3: Build and deploy the solution as designed in step 2.

Step 4: Run tests on the solution based on all requirements to measure success or failure by requirement. 

Step 5. Summarise all findings in a report.  The report is presented to stakeholders who will conclude if the PoC is a success or failure. This is basis for a decision.  

This service applies, but is not limited to the following items:

Microsoft, Oracle, System Center, Windows 10, Azure, Office365, Excange, SharePoint, Skype for Business, OneDrive for business, Facebook, AWS, Bluemix, Yammer, Machine Learning, Amazon, Windows Server, Hyper-V, Hybrid,