![]() |
|
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 |
|
Hobbyist Programmer
|
UML Use Case Diagrams - Generalization vs Extends
Can someone explain to me how the generalization and extends purposes differ in a UML Use Case Diagram? It seems like the both describe inheritance.
|
|
|
|
|
|
#2 |
|
Professional Programmer
Join Date: Jun 2005
Location: India, The great.
Posts: 435
Rep Power: 4
![]() |
I don't think generalizations and extends etc. relationships are shown in a Use Case diagram. These are shown in the class diagrams.
Here's a little tutorial on UML Use Case Diagrams.
__________________
PFO - My daily dose of technology. |
|
|
|
|
|
#3 |
|
Hobbyist Programmer
|
Did you look through that? That tutorial shows the use of the extends arrow, but not the generalization arrow. I think that the extends arrow basically says that I can use any one of the options that extends the use case, and the use case itself. Whereas a generalization arrow says that the use case is a base case for the use cases inheriting from it and that I must choose one of the ones that inherit the base case.
|
|
|
|
|
|
#4 |
|
Hobbyist Programmer
Join Date: Jan 2006
Location: UK
Posts: 242
Rep Power: 3
![]() |
A specialisation/Generalisation relationships are similar to Class diagrams where a Super use case represents common properties of its sub use case.
An extend relationship is usually used to deal with further explicit interactions, or with exceptional cases that normally does'nt occur. They are both forms of generalisation, and are both poorly defined in UML. Depending on the situation, it can be argued which is more appropriate. |
|
|
|
|
|
#5 | |
|
Professional Programmer
Join Date: Jun 2005
Location: India, The great.
Posts: 435
Rep Power: 4
![]() |
Quote:
__________________
PFO - My daily dose of technology. |
|
|
|
|
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|