Mom is making a sandwich for Kid. Overall, the process of making and serving the sandwich includes handling bread, handling peanut butter, handling jelly, and serving the sandwich.

All components of serving are optional, but, naturally, one does not serve peanut butter or jelly without bread. Therefore, before adding these components, Mom elicits Kids requirements, i.e.:

- asks whether they would like a sandwich,

- asks whether they would like any peanut butter on their sandwich,

- asks whether they would like any jelly on their sandwich.

Kid expresses their preferences as binary answers (e.g., Yes, please or No, thank you). Mom proceeds based on a response by either adding the component or skipping to the next step. Assume that this is all Mom needs to know to serve the sandwich and there is no variation in how the sandwich is made; i.e., no other qualitative or quantitative information is necessary. When Mom passes the sandwich, Kid takes the sandwich, while simultaneously thanking Mom. Passing and taking the sandwich, and thanking means information of acknowledging that the sandwich was passed and received.

Sketch your process model of the as-is business process on paper as a UML activity diagram for the entire scenario above. Include swim lanes for actors, all relevant activity and decision nodes (for now, ignore the merge nodes). Assume you are concerned with the information (control) flow only (ignore any flows of objects, materials or energy).