1. Requirements:

In conjunction with the client we perform an analysis to understand the existing IT application landscape and architecture, along with the various interface mechanisms available to each application. We then discuss performance, thresholds, and technical requirements.

We identify the required i-Con components, discuss infrastructure requirements, and come up with a project implementation plan.

Once in agreement we move onto the design phase.

2. Design

We design the system architecture to deploy the i-Con platform, as well as a blueprint for the i-Con interfaces based on the Client’s specific business requirements. We create a test plan with defined test samples that are incorporated into the test harness . Once the client has signed off on this, we move onto the development phase.

The i-Con Test Harness was born over time when we kept finding ourselves waiting for systems to become available. These systems would be the Provider of information that the Consumer required. As the Broker we had the power to control where the messages were sent, as well as the content of the messages.

Eventually it made more and more sense that ProSolutions Integration offered a product that could be used to shorten the project test cycles. By applying the test harness during the Development (Dev) and End-To-End (ETE) environments, we have found that the test cycles in a System Integration Testing (SIT) environment are more efficient and tend to be a lot shorter.

3. Development

In this phase we create any custom components needed to address all specified requirements. We create the event processes and integration flows based on ProSolutions best practise. We also document and test all event processes.

4. Testing

We perform functionality and load testing on all event processes. We implement the testing harness.

5. Going Live

We run User Acceptance Tests (UAT) and train the users. The project is signed off, and we are almost done.

6. Maintenance

At ProSolutions we don’t believe that a project is finished just because we have handed it over and it has gone live. During this final, but ongoing phase of a project, we provide maintenance and support services for the deployed event processes. We continue to design, test and deploy enhancements to existing event processes as well as designing, testing and deploying new event processes to meet new requirements. We provide ongoing monitoring of services as well as quarterly optimisations and audits/reviews of event processes.

Note that the i-Con Test Harness is used for integration testing to shorten the testing cycles normally encountered when Provider systems are not available during the DEV and ETE stages of a project.