Between the two of them, basic use-case and business-process documentation may provide enough information to make the structure and flow of the data through the system obvious, or at least transparent enough that development won't need any additional information. The Refuel process we've been looking at probably falls into that category, but let's see what a data-flow diagram for it might look like anyway.
The data that's coming in (the Refuel Data in the flowchart) was defined earlier in Use Cases section, and at least some of the related data flow was also noted, but having some names to associate with those values, and knowing what types of value they are, will be helpful:
-
odometer: The current odometer reading (probably an <int> value)
-
fuel_quantity: The amount of fuel used to fill the truck (probably a <float> value...