There are two closely related diagram types that are used to further specify the scenario of the Business App or Use Case Realization, the Application Structure and Application Integration diagrams. The former specificies the logical connections, using stereotypes to represent the integration patterns to be used. The latter expands on those integration styles to show the mechanisms used to realize the logical connections..
Application Structure
Application Structure Diagrams are used to show how the various application components communicate with each other. They can be used to show how the components of a Business App work together or how the components of different Business Apps, DB Schemas, and Services work together to satisfy a given scenario, typically for a Use Case Realization.
The diagram below shows an n-tiered approach for presenting the components together in their related tier.
Application Integration
The following diagram expands on the integration styles that are suggested by the exposed interface stereotypes in the Application Structure diagram above.
As you can see, the Player Rating Session no longer talks directly to the services, but rather has its requests piped through a queue to the Enterprise Service Bus. The Bus routes the request messages to the appropriate service and returns the responses back to the Player Rating Session. See Integration Styles - Enterprise Service Bus for more information.
