"Selecting a student" is not really a "first class" use case on its own - this step alone is incomplete, in isolation it fulfills no purpose. As you wrote about your application, the selection is actually done for choosing another operation, and only the combination of both may become something which is "really" a use case.

So "selection" is only a fragment of a use case, and it can be part of several other first-class use cases. As explained in this older SO Q&A, this means the "includes" relation will be the more appropriate choice.

"Selecting a student" is not really a first class use case on its own - this step alone is incomplete, in isolation it fulfills no purpose. As you wrote about your application, the selection is actually done for choosing another operation, and only the combination of both may become something which is a complete user task.

So the selection is only a fragment of a use case: it can be part of several other first-class use cases. As explained in this older SO Q&A, this means the "includes" relation will be the more appropriate choice.

"Selecting a student" is not really a use case on its own - this alone fulfills no purpose, and as you wrote about your application, the selection is actually done for choosing another operation.

So this only a fragment of a use case, and it can be part of several other first-class use cases. As explained in this older SO Q&A, this means the "includes" relation will be the more appropriate choice.

"Selecting a student" is not really a "first class" use case on its own - this step alone is incomplete, in isolation it fulfills no purpose. As you wrote about your application, the selection is actually done for choosing another operation, and only the combination of both may become something which is "really" a use case.

So "selection" is only a fragment of a use case, and it can be part of several other first-class use cases. As explained in this older SO Q&A, this means the "includes" relation will be the more appropriate choice.