Pools and Lanes:

Two pools: "Customers" and "Pizza Shop."

Within the Pizza Shop pool, three lanes: "Clerk," "Chef," and "Delivery Guy."

Activities and Events:

Customer places an order $($Online or Phone$)-$ depicted as a rounded rectangle labeled "Place Order."

Clerk receives and confirms the order $-$ shown as a task labeled "Confirm Order."

Chef prepares the pizza $-$ represented as a task labeled "Prepare Pizza."

Pizza is baked and boxed $-$ depicted as a task labeled "Bake and Box Pizza."

Delivery guy picks up the pizza $-$ shown as a task labeled "Pick Up Pizza."

Delivery to the customer $-$ represented as a task labeled "Deliver Pizza."

Payment processing if not done online $-$ shown as a task labeled "Process Payment."

Flow and Decision Points:

Sequence flows connecting each task in the order they occur.

Decision points represented by diamond$-$shaped gateways, e$.$g$.,$ for type of pizza or delivery address validation.

Resources and Handovers:

Use directional arrows to illustrate the flow of information$/$resources between roles, like order information passing from customer to clerk to chef.

Handovers indicated by arrows connecting tasks where a resource or product moves from one role to another $($e$.$g$.,$ prepared pizza from chef to delivery person$).$

Additional Elements:

Customer feedback mechanism $-$ shown as a feedback loop connecting back to the "Place Order" activity.

Time tracking for delivery efficiency $-$ could be represented by a clock icon with an arrow indicating the tracking process. Draw a process modeling diagram to show the pizza delivery process.