Configuration and Customisation


Carry out Customisation

Complete agreed customisation
  • Requirements
  • Gap analysis
  • List of Customisations
    1. Carry out analysis and design of the customisations.
    2. Build the customisation.
    3. Prototype with users.
    4. Revise customisations (if required).
    5. Carry out system and integration testing.
  • Customisations ready for User Acceptance Testing

For each customisation, you will need to work out the most appropriate method to complete the work.

  • Where it is clear what is required, the analysis and design can be completed before the business are asked to sign off the change. It can then be constructed. An example may be a report where business are clear what needs to be on the report, how it should be sorted, and there is an example to work from.
  • Where it is less clear what is required, it may be more appropriate to use a prototyping approach. This will entail building a non functioning version of a screen or report and discussing it with the business to get their feedback. This may be repeated a number of times - each time with more functionality being added - as it evolves into a final product. An example may be an input screen to carry out a particular transaction which is new to the business.

After the customisation is complete, each component should be tested to ensure it operates within the application environment. For example, a report may run perfectly when it is run directly against a database. When run from within the application, it may have unforeseen problems.

Occasionally when developing a customisation, investigation uncovers that the functionality, or similar functionality, is already available within the application. This is quite normal and is typically the result of some thinking outside the square when investigating a proposed solution. In this case, the customisation may be cancelled.


Return to the top