Can Use Case be an actor for another use case


I got a question in my mind that whether a use case can be a actor for another use case, If yes then how.

I have a scenario for Payroll system, where there is use case called “service book” then there are some other use cases(“Manage Personal Info”,“Manage designation” …) depending to use case “service book”.

can use case “service book” work as an actor for use case “Manage Personal Info”

Thats the problem …


Well it is pushing the boundary a little, but if the service book is another system you can represent it as an actor.

But it looks like you are better of to have the use case as an .