Our Story

Where we've come from

In the early 2000 the web revolution trigged the idea of POP®Software and Herman brought together a team of developers between 2002 - 2003 to help build it. In 2003 the first website was implemented with the use of POP®Software.

Partner received the award for Emerging Technology Top 100 company. "Emerging TT100 Company status is awarded to a select number of organisations which, although less than 3 years old, already display significant promise due to their outstanding levels of technological excellence and innovation". Emerging Technology Top 100 company. POP®Software was short listed for IT-Systems AIS age of innovation awards.

Between 2003 - 2004 Partner established its credentials and references and from 2007 to the present have established an nurtured its partnerships with a vast array of clients.

Our Services

Development Methodology

How we work

Over the years Partner have established its own systems development methodology. Our methodology has been adapted from enterprise standard methodologies to suit our environment and clients better. The model is a continuous improvement loop consisting of the following steps that are described below: Context setting, Modelling, Implementation, Support - looping back to Context setting ext.

Engage with the user to understand the current context.

In this phase Partner prepares a model that is presented to the business. Once approved the model becomes the system requirements.

The proposed model is a model of the business and could contain the following models:

  • Technical Model
  • Business Model

In traditional terms this would be called the Build phase.

This phase consists of the following steps:

  • Detailed Design
    The model definition is broken down into work tasks that can be handed to individual developers or teams. The detailed design consists of an overview, Functional descriptions, screen layouts and data design, test plans.
  • Task development
    Detailed design is implemented in program code by a single developer or development team.
  • Unit Testing
    The developer or development team tests their program code independent of other parts of the system. Inputs and outputs are tested against the unit test plans. Screens are shown to the users for approval.
  • System testing
    The program unit is tested with other system components to ensure the various components of the system works together according to the system test plans.
  • Integration testing
    The system is integrated with other systems in the environment and tested according to the test plans.
  • User acceptance testing
    The full system is provided to the users for acceptance.
  • Implementation
    The system is implemented according to the implementation plan. This involves the physical change control process and the possible take-on of previous data.

In this phase Partner supports the running of the system by:

  • Reacting to User requests
  • Fixing any reported problems
  • Analysing usage data to ensure the systems runs smoothly
  • Analysing user behaviour to determine future changes
  • Analysing workflow engine results to establish the performance of the business processes and to identify possible bottlenecks