Hi I have multiple fonctionalities: the manage and view share the same fontionalities but the view use case contains the view of dashboard and calender in addition. I have one actor and if he/she authenticates to his/her account then the actor can use the mobile app.
Which diagram is correct ("gerer" means "manage" and "consulter" means "view") ?
I built this use case diagram to describe the fonctionalities of my mobile application:
Both diagrams are ambiguous, because of the naming of the red and green use-cases that are specialisations of the yellow ones. The specialisation means that for example Article is a kind of Manage. This is ambiguous already grammatically, but also because your first diagram shows that articles could be managed and viewed. Moreover, use case names must be unique.
One easy way to improve this would be to rename the ones in red and green, by repeating the more general verbal group together with the specialised noun group, e.g. Manage article. This will disambiguate the diagrams.
The next step will be to address the remaining flaws:
Your approach is very explicit but has one problem: it multiplies the use-cases unnecessarily, without bringing really added value, at least at first sight. A better alternative would be to stick to generic use-cases, e.g. Manage Item, View Item and explain somewhere that Item can be articles, invoices, etc... (See also on this other question here)
