I am creating a use case diagram for an elevator control system program, and I am a little confused about using includes for sequential actions. What I mean is that when the user calls the elevator, it is required that subsequently the call button light must turn on and the elevator must go to the called floor. After the elevator goes to the called floor, it is required that the doors open. There is other functionality I will add, but just consider this simple case.

Are my arrows pointing the wrong way? It's a little confusing to think about a process backwards.

Should the arrow point to the action that happens first rather than second?

Here is what it would look like with the arrows the other way

I am creating a use case diagram for an elevator control system program, and I am a little confused about using includes for sequential actions. What I mean is that when the user calls the elevator, it is required that subsequently the call button light must turn on and the elevator must go to the called floor. After the elevator goes to the called floor, it is required that the doors open. There is other functionality I will add, but just consider this simple case.

Are my arrows pointing the wrong way? It's a little confusing to think about a process backwards.

Should the arrow point to the action that happens first rather than second?

Here is what it would look like with the arrows the other way

*edit: question title