Data flow

Follow the data flows in the Sale example application when user-related activities are included.

Figure 1. Data flow in the Sale example application, showing user-related activities. (The root activity is not shown.) Changes from the basic Sale example described in The Sale example application are shown in bold.
The picture shows the input and output data flows described in this topic. A rectangle represents the Sale business transaction. The rectangle contains several smaller rectangles, representing the Order, Delivery, Confirm, Invoice, and Payment child activities. Another rectangle, outside the Sale transaction, represents the Menu transaction. Input and output data flows are represented by arrows. The Menu transaction collects input from the user. The output from the Menu transaction becomes the input to the Order activity. The Order activity collects further input from the user. The output from the Order activity becomes the input to the Delivery activity. The output from the Delivery activity becomes the input to the Confirm activity. The output from the Confirm activity (which requires the user to enter data) becomes the input to the Invoice activity. The output from the Invoice activity becomes the input to the Payment activity.
  1. User data collected after the user selects the Sale menu option is used as input to the Order activity.
  2. The user data collected by the Order activity is used as input to the Delivery activity.
  3. The output data produced by the Delivery activity is used as input to the Confirm activity.
  4. The output produced by the Confirm activity (which requires user input) is used as input to the Invoice activity.
  5. The output produced by the Invoice activity is used as input to the Payment activity.
Parent topic: A user-related example

dfhp9c0041.html | Timestamp icon Last updated: Thursday, 27 June 2019