Many workflow models look correct at first glance until you try to trace exactly what happens to the information being processed. You might see a clear flow of control from start to finish, yet the data itself seems to appear out of nowhere or vanish without explanation. This is a common mistake in enterprise modeling: focusing entirely on control flow while ignoring the actual state changes required to make the process work.

This section solves that problem by shifting your focus from just the “when” to the “what.” We will move beyond simple arrows to define exactly how information enters, transforms within, and exits activities. I will guide you through the practical nuances of the UML object flow activity notation, helping you represent external data stores and intermediate data dependencies with clarity.

In my experience with banking and logistics workflows, neglecting the details of data movement leads to implementation failures. By mastering the object flow activity diagram rules, you will ensure your process models are robust, logically sound, and ready for developers to build upon.

What This Section Covers

In this part of the book, we tackle the complexities of data flow to ensure your diagrams accurately reflect business reality. We will cover the following chapters:

• How do I show data flowing between activities? – Learn to use dashed object flow arrows and pin notation to visualize dependencies clearly.
• When should I use object nodes vs pins? – Understand the decision criteria for choosing between temporary data passing (pins) and persistent storage (object nodes).
• Why are my object flows creating cycles? – Diagnose and fix circular data dependencies that often break process logic.
• How do I model data transformation between activities? – Master the notation for showing how input objects change type or state as they move through your workflow.

By the end of this section, you should be able to:

• Connect activities using dashed object flow arrows to explicitly show data dependencies.
• Choose the correct notation for data transformation activity needs, distinguishing between temporary passing and storage.
• Identify and eliminate circular object flows that create logical errors in your process models.
• Represent external storage and interface passing correctly using object node notation.
• Apply the concepts of a data flow UML activity to real-world banking and logistics scenarios.