Page 106 -

P. 106

2 The Language: Rationale and Fundamentals 93

Ordering

[else] [order not approved or timed out]

Carrier Appointment

[else] [order preparation timed out]

Freight in Transit Payment

Freight Delivered

Fig. 2.45 Working example: control-ﬂow

Freight in Transit task involves tracking an order while it is shipped to a customer
and handling any enquiries they may have about its status.
Once these two tasks have completed, the last task – Freight Delivered – can
execute. This involves handling any requests from customers to return goods or
any claims for loss or damage during its transportation that may be received. These
must be received within a speciﬁed timeframe, otherwise the order is deemed to be
complete and the process completes.

2.8.2 Data Perspective

The data perspective of the order fulﬁllment process is relatively straightforward
and centers around the notion of a purchase order. Figure 2.46 illustrates the data
elements passed between the various nets in the order fulﬁllment process. In the
main, the process-relevant data is retained in the Overall (i.e., the top-level) process.
It also illustrates the net variables in each of the nets.
The user-deﬁned data types underpinning the net variables depicted in Fig. 2.46
are summarized in Listing 2.1.

101 102 103 104 105 106 107 108 109 110 111