Topics

Introduction
Guidelines

Introduction To top of page

This guideline focuses on designing the details of an Application Client. Additional guidance on Application Clients is provided in Guidelines: Application Client.

Guidelines To top of page

The designer must consider what mechanisms the Application Client uses to communicate with the rest of system. Does it, for example, interact directly with EJBs, or indirectly via HTTP or JMS? Also, application clients can use Java threads, and so concurrency within the application client needs to be considered. These are decisions made as part of Activity: Describe the Run-Time Architecture.

The designer must also consider what classes and subsystems execute as part of the application client, what interfaces (if any) that they in turn expose to the rest of system, and what dependencies they have on other parts of the system. See Artifact: Design Subsystem for details.



Rational Unified Process   2003.06.15