Processing diagrams

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-componentEntity 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-componentProcess application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.

utility-componentUtility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.

information-flowInformation flow: Defines the flow of any kind of information (business entity, event, product, informal, etc) between active entities of the enterprise.

associationAssociation 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.


Nicolas Figay
0 # Nicolas Figay 2011-10-26 07:04
On this page, the difference of color between Entity Application Component and Utily component makes it not so obvious to distinguish.
In addition, some components have colors which are not explicitly defined in explanation of used symbol.
Finally, the usage of containment in order to represent the composition/decomposition makes it not so explicit (compared to relations) what is exactly the kind of composition relation.
So it should be somewhere stated which kind of composition are allowed and what is the associated semantic.
Reply | Reply with quote | Quote
0 # phil 2011-10-26 11:13

I agree that colour shall not be the only marker (black & white is still massively used)
You will see a more complete definition of used symbols in the communication diagrams.
I disagree on your comment about containment : this is the UML internal structure/parts semantics, very well defined by the UML standard.
It expresses that the application component is deployed withing the container device, or the container technological component (application server for example). It is a much clearer and precise semantics that some link. Composition has a uge number of semantic variations.
Reply | Reply with quote | Quote

Add comment

Security code


Sign in to use the forum and be informed of the latest news.

Latest comments