Use Case Diagram Option and Option AND two actor in one module same use case

Question

The case 1: The Human Resource Manager can add a new employee. HR Manager can either add the admin staff or add academic staff. And Academic staff has full-time or part-time. I know that the primary use case is add a new employee. But the Question is did I <<include>> a use case which is "select the category of staff" after "add a new employee" ?

The Case 2: The student and admin both can view, edit the student profile. But additionally admin can delete the certain info about student. So did i draw is TRUE?

This is a test, isn't it? Looks like "complete the drawings"... — qwerty_so, Oct 29 '19 at 14:22
Are you mocking us with these child drawings? Please use a proper UML tool and draw some readable diagram and then come back here. — Geert Bellekens, Oct 30 '19 at 07:27

score 0 · Answer 1 · answered Oct 29 '19 at 14:15

As you correctly stated, the UC in the first case is Add employee. Full/part time are attributes you assign to an employee object. This is part of the story (activities) you describe within the use case. These steps are not use cases. Don't fall in the trap to start functional decomposition.

The 2nd case would be ok this way. However, you can go different ways:

If Admin inherits from Student this actor has the same use cases (so Admin is associated with all the UCs).

Another way is

where you have a general editor and you add constraints for accessing use cases.

There are reasons for using each of the above which vary by different domains.

Use Case Diagram Option and Option AND two actor in one module same use case

1 Answers1