Considerations for System Structure Design

You can use the results of elementary process/entity type usage, user task analysis, distribution analysis, and current systems analysis to decide:

Whether data that is used by users at the same type of location can be stored on client workstations to support distributed process procedures.
Whether data should be stored on a shared server because it is used by a wide range of organizational units or users.
Whether current systems logic can be reused for new distributed presentation procedures.
Whether new logic should be placed either on a server for remote presentation, or on a client for combining local with remote data.
How many of the user tasks should be automated on the client.

In general, the functions of client and server procedures should be:

Client procedures deal with user task support, the user interface, simple field validation, work-flow logic and interworking with other workstation-based facilities (such as for managing documents and spreadsheets).
Server procedures manage business rule and data integrity logic, and therefore logic that provides access to shared stored data.