Designing Client/Server Applications › Action Diagram Tool

Action Diagram Tool

The PrADs for distributed process applications must contain separate logic for the client and server components. The client logic has two parts. One part receives input from the user, begins processing, and passes control to the server. A second part receives control from the server and ends the processing for that procedure step.

Generally speaking, the separation of logic occurs along the following areas of processing:

• Client (Input)
  • Presentation of information
  • Dialog control
  • Input validation
  • Event processing
• Client (Output)
  • Error reporting
  • Reformatting of extracted data
• Server
  • Data actions against the database
  • Error recovery
  • Input validation requiring data access

Tracking between the client and server logic is easier if you match the command sent and received. You can accomplish this by creating a similar CASE OF COMMAND structure in the PrADs for the client and server components. Although the structure is similar, the actions for the commands differ in each PrAD.

For more information about the Action Diagram tool, see the Action Diagram User Guide.