Clarification on sequence execution flow UVM cookbook figure

[HepoH]

It still looks like the authors were illustrating the blocking nature of these calls:

1. Blocking nature of start_item. There’s a solid arrow starting from start_item, since it simultaneously places the req into the sequencer’s request FIFO.

2. Blocking nature of get_next_item. Since the driver doesn’t actually do anything in this call except wait for the next request, there’s no other solid line there.

3. Blocking nature of finish_item. There’s a solid arrow starting from finish_item, because that call simultaneously sends the request to the driver through the sequencer.