The processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. A deployment unit represents grouping of business function, service, or application components. The processing diagram addresses the following questions:
- Which set of application components needs to be grouped to form a deployment unit?
- How one deployment unit connects/interacts with another (LAN, WAN, and the applicable protocols)?
- How application configuration and usage patterns generate load or capacity requirements for different technology components?
See network computing hardware diagram. Processing diagrams will use deployment in a more generic way, in order to present deployment units. Deployment units can be presented as component instances where application components are deployed, or as physical utility components that will host the deployed application component (for example, an application server).
Associations between these deployment units will represent the connection (for example, a network), while information flows will indicate the nature of the information being exchanged.
In these diagrams, indications about capacity requirements are provided.
This processing diagram shows how application components are deployed under the different kinds of application servers
The deployment configuration above is still independent of future deployment on physical servers.
Entity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.
Process application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.
Utility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.
Information flow: Defines the flow of any kind of information (business entity, event, product, informal, etc) between active entities of the enterprise.
Association between two classes: An association has a name, and for each extremity provides the role name and cardinalities (possible number of occurrences) of related elements.