System as an actor

eBook is a system which can scheduling courses for training centres and able to bookings online directly from client.
Can i take eBook as an actor? because there is no person who maintain bookings or scheduling courses for training centre.

[quote=Prem]eBook is a system which can scheduling courses for training centres and able to bookings online directly from client.
Can i take eBook as an actor? because there is no person who maintain bookings or scheduling courses for training centre.[/quote]
I assume you mean in a Use case diagram? Most definitely.

There are no hard cut out rules for this, but generally speaking an actor “acts” (sounds cliché, I know). I always go for the broad approach: “does x actually perform a task?”. If the answer is yes then ‘x’ is most likely an actor.

And VP also has you covered here a bit. I mean… It’s actually a system which can “do” stuff. So I would probably use this as an actor and define the things it can do through the Use case diagram (“Schedule course”, “Book online”) and then create a sub diagram which references the eBook and further explains what it can internally do.

For example an Activity or Sequence diagram which further explains its inner workings.

Hope this can help!