Component Architecture

The Retail-J set of applications combines J2EE™ technologies with a highly componentised approach of over 9,000 Java classes, constantly increasing as more functionality is added. This provides not only a set of packaged applications, but also an underlying ‘toolkit’ that can be developed and adapted to different environments.

For example:

• The same application code can be deployed on different hardware devices in different combinations of components while implementing the same algorithms for product look-up, pricing, stock rules etc.
   
• Different applications, such as POS, queue busting and home shopping share common components – such as the promotions engine – so that functions do not have to be developed and maintained separately.
   
• Thick and thin versions of applications, such as the POS, can use 100% of the same business logic with only the user interface components differing.
   
• Customisations and enhancements can be implemented in components that are kept separate from the underlying system. This helps to retain the integrity of the core and allows customisations to be tested and deployed independently of the standard Retail-J products.

Application Components and Own Development

Initial and ongoing enhancements to the standard product to meet customer requirements make extensive use of Retail-J’s componentised architecture and are deployed as additional and modified components. Their fine granularity, and the ability of the Java™ language to control component interfaces rigorously, makes it feasible for multiple parties to enhance the product simultaneously without significant conflict.