It's a very busy use case diagram - you should really consider a set of simple diagrams based on a single main actor rather than pull together such an elaborate group. Remember that the use case diagram indicates the interfacing between the actor who precipitates system processing and the system,so they are most useful and meaning ful when they concentrate on the interface action - a "happy day" and alternate scenarios can then be spun off this to develop system processes dependent on the use case.
It's a very busy use case diagram - you should really consider a set of simple diagrams based on a single main actor rather than pull together such an elaborate group. Remember that the use case diagram indicates the interfacing between the actor who precipitates system processing and the system,so they are most useful and meaning ful when they concentrate on the interface action - a "happy day" and alternate scenarios can then be spun off this to develop system processes dependent on the use case.
ReplyDelete