It is difficult to find a clear definition of the term 'globalisation' but it is clear that it is associated with particular characteristics; the following is a list of some of those characteristics:

• Growth in technology
• Capitalist or market economic systems
• Corporate expansion
• Trade issues
• Poverty and inequality
• Impact on the environment
• Communication
• Brand expansion and recognition

MDI (Multiple Document Interface) is a Microsoft Windows programming interface for creating an application that enables users to work with multiple documents at the same time. Each document is in a separate space with its own controls for scrolling. The user can see and work with different documents such as a spreadsheet, a text document, or a drawing space by simply moving the cursor from one space to another.

An MDI application is something like the Windows desktop interface since both include multiple viewing spaces. However, the MDI viewing spaces are confined to the application's window or client area . Within the client area, each document is displayed within a separate child window . MDI applications can be used for a variety of purposes - for example, working on one document while referring to another document, viewing different presentations of the same information, viewing multiple Web sites at the same time, and any task that requires multiple reference points and work areas at the same time

Silly window syndrome is a problem in computer networking caused by poorly-implemented TCP flow control. If a server with this problem is unable to process all incoming data, it requests that its clients reduce the amount of data they send at a time (the "window" setting on a TCP packet). If the server continues to be unable to process all incoming data, the window becomes smaller and smaller, sometimes to the point that the data transmitted is smaller than the packet header, making data transmission extremely inefficient. The name of this problem is due to the window size shrinking to a "silly" value.

Since there is a certain amount of overheadassociated with processing each packet, the increased number of packets means increased overhead to process a decreasing amount of data. The end result is thrashing.

• Presentation Layer
• Business Logic Layer
• Data Access Layer

In most of the cases the data entered by the end user needs some kind of validation or further processing. This is the responsibility of Business Logic Layer.

Finally, your application data needs to be stored and retrieved in some data store (RDBMS, XML etc.). This task is handled by Data Access Layer.

In short, the process works like this:

• User requests for some application data.
• The data access layer retrieves the data and is forwarded to the presentation layer via business logic layer. Sometimes data access layer gives this data directly to presentation layer.
• Presentation layer receives the data to be displayed via business logic layer.
• The user changes the data and initiates the appropriate action (such as insert, or update).
• The business logic layer validates the data submitted by the user.
• If the data is valid it is handed over to data access layer for updating into the database.

• The applications gets divided in logically isolated pieces reducing tight coupling between the UI, business processes and database.
• Change in the underlying database and data access methods do not have any effect on the presentation layer or client application.
• Client application no longer has SQL statements embedded in it. This makes it de-coupled from rest of the application.
• Table and column names can be effectively eliminated from the client-side code.
• The client application is unaware from where data comes (location transparency).
• It becomes easier to modify or extend your application, without breaking or recompiling the client-side code.