Hi
I created this process map as an exercise during a process modeling training.
Everyone knows how to check-out an hotel room... although there is a variation where we sometimes find the bill under the room's door at checkout date.
One advantage is that you can place it into a process architecture: at a higher level we can represent the main Hotel processes: Check-in, Check-out, Restaurant, Conference, Shop, Accounting, so that a link can be set to the Check-out process from the first level.
Similarly the "Payment" activity can invoke lower procedural levels showing the different ways a customer can pay: credit card, cheque, cash.
It should be noted that:
(1) all the forms of "Payment" should end-up with either the "Payment accepted" or "Payment not accepted" events, to be compatible with the calling level.
(2) the "Payment" activity can be basically the same when paying the restaurant, the shop, the bar (thinking about this makes me thirsty) ...
There is a lot to say about this easy process: the need for indicators, some risk identification, the use of a system, all of this makes it an excellent (and useful) storyboard for a training.
Regards,
ARIS model
