Saama has worked with both Product and End-User companies to enable their solutions to be used globally. Part-I
Customer Messaging Product Vendor:
The client, a customer messaging management solutions provider, realized that the architecture
of their product limited their ability to sell across platforms, database environments
and geographies. Re-architecting their product to work across multiple platforms and meet
the internationalization/localization requirements of global customers, posed many challenges
including hiring new people with the requisite skills, distracting the engineering team
from the next release, and doing it in time to meet customer needs. Outsourcing the development
was seen as a viable strategy and Saama was chosen as their partner.
Saama created a robust, scalable, and modular architecture based on best of breed technologies,
not only reduced the inter-dependencies or strong couplings across modules but it
also, made the product independent of database and application server environments, leading
to a 100% J2EE based architecture. The architecture also enabled the product to be
i18N ready with a common code-base and common GUI client approach.
The client was able to redirect their energies to improving the functionality and footprint of
the product, rather than spend time on rearchitecting their product. It also provided them
with the ability to get an internationalized and platform-independent product out a few
months faster than originally planned.
Leading CRM solution provider:
The client needed a more robust internationalization capability, as they were a global company
with many international customers across EMEA and Asia Pacific regions. As part of
their next release, they decided to move towards a more comprehensive i18N architecture
which would enable a common GUI in addition to the common code base that they had al-ready
implemented. This would drastically improve internationalization support, reduce
time-to-market and eliminate the engineering support challenges of having multiple GUI clients
for each locale supported. Saama consultants were engaged to assist in this effort.
Saama conducted Pseudo Localization Testing (PLT) to quickly identify the hard-coded functionality,
features, labels, headers and messages that needed to be removed from the core
code base and included in localization configuration files to enable a common GUI approach
to i18N. This was successfully completed and the local configuration files built.
The client was able to include this enhanced internationalization / localization ability in the
next version, which was, launched late 2003.
|
