0

I have register profile and edit profil on my use case diagram .Register profil will be for the first time when user sign up application but edit profil will be always how I must do include or extend relationship of these user cases

karabugra05
  • 55
  • 1
  • 1
  • 7
  • 2
    Possible duplicate of [What's is the difference between include and extend in use case diagram?](http://stackoverflow.com/questions/1696927/whats-is-the-difference-between-include-and-extend-in-use-case-diagram) – Geert Bellekens Mar 16 '16 at 04:13

2 Answers2

0

Don't make any extend and include at all. Just place a constraint to the use case Register Profile that it is done only once. Include/Extend shall not be used for functional decomposition. Their use is "highly sophisticated" (to avoid words like bloated or silly) and it is recommend to avoid them simply because of the first reason: no functional decomposition!

qwerty_so
  • 35,448
  • 8
  • 62
  • 86
0

It depends on how you see the relationship between the two use cases:

  • are register profile and edit profile independent ? Example: someone enters your website the first time, and choose to register; As soon as he saves his profile info, he comes back to the were he was.

  • or do you you see register profile as the first step before edit profile ? Example: someone enters your website the first time, and choose to register; As soon as he has created his profile, he automatically is in edit profile, in case he wants to do some changes. In this case edit extends register: both are self sufficient use cases, but at the end of the registration an extension point link to the extending case.

  • or do you see register profile as dependent of edit profile, which represents a significant part of it ? Example: someone enters your website and automatically gets an anonymous profile; when he chooses to register the edit profile opens that allows him to put a name on his existing profile. In this case register includes edit: one can't have the first without the second.

Note that personally, I'd opt for the first approach (as suggested by Thomas), as you definitely will need both interactions. I would reserve inclusion only use cases that are not triggered directly by the user. I would not like to use the extension as it is ambiguous (here: does edit extend register due to extension point, or does register extend edit, due to added functionality). Martin Fowler in "UML distilled" strongly advises against using extensions here because of the fierce debate they usually provoke.

Christophe
  • 68,716
  • 7
  • 72
  • 138