Hi Larry,

From your description I see two things:

• you are trying to describe/model/document system/technical specifications and not business processes; you're talking about tables, fields, and types.
• you are at a very detailed level of the specification.

Given what you are trying to accomplish and the level of detail, neither the DFD nor a process flow would suit your needs.

I'm not 100% certain as to what you are trying to show but if, for example, you are trying to specify the detailed specs on how to "compute the total" then I would create a data model (Entity Relationship Diagram) to show the tables and their fields.  Then for each "function" I would use some sort of pseudocode or structured English to specify the detailed logic for getting the data you need and arriving at the desired result.

By the way, I am assuming that the business need/problem has already been clearly defined and the requirements have been elicited and documented for your project.  Also, if you have not yet specified your solution at the logical level you might consider doing so.  Before you get down to the physical/technical details you should outline your solution in terms of logical concepts.

- Adrian