"The easiest and simplest way to create global e-business applications is to start from scratch with a well-trained development team, but most companies do not enjoy such a luxury. They often employ development teams located in multiple locations and use myriad hardware and software platforms. Furthermore, new applications have to work with existing applications that were most likely not originally designed to support global e-business. One very useful tool in tackling these issues is to define a set of corporate wide Globalization Architecture Imperatives (GAI) that the various development teams are required to follow.
"The objective of the GAI is not to define in detail how an application is to be implemented, but rather to lay down some fundamental principles for all development groups to follow, so that different applications handle different languages consistently, can inter-operate, are translatable, and function well in an on-demand environment. They will help companies move effectively and efficiently towards e-business across the globe."
-- Charles Pau
Director, Globalization Architecture and Technology
IBM Software Group
Different companies will define different GAI depending on the applications and platforms involved. The following pages summarize basic principles that are likely to be common across all companies. |