This is the phase in which we either write or adapt the processes that will describe how to use the new solution as defined in the prototyping phase.
Based on the prototype and testing results (by virtue of “use cases”, among other things), we structure the roles and work cycles into processes and sub-processes that describe how the new solution can be used most effectively.
Documents that explain in detail the processes and sub-processes to be used in subsequent phases, one purpose being to customize user training.
Developing adaptations that will address the solution’s specific use requirements as described in the analysis phase.
Based on the specifications defined in the analysis phase, we develop and test the desired adaptations. These adaptations of the standard solution may extend to:
The plug-in integrating the different remedies is added to the standard solution and the resulting adapted solution is tested on the basis of the “use cases” developed in the prototyping phase.
We create interface points between the new solution and third-party software and databases with which it has to interact.
We develop the desired interface points in the lab.
We prepare data sets for use in interface testing
We make the necessary corrections (once again, in the lab) until the integration begins to respond to the prototype’s desired outcomes.
Finally, we install the interface points and plug-ins in the client’s testing framework and we test the integrated solution in order to validate results before moving on to deployment.
The interface points are introduced into the solution and the entire set of changes is tested, validated and readied for the deployment phase.