Programming Forums
User Name Password Register
 

RSS Feed
FORUM INDEX | TODAY'S POSTS | UNANSWERED THREADS | ADVANCED SEARCH

Reply
 
Thread Tools Display Modes
Old Apr 12th, 2006, 11:18 AM   #1
hoffmandirt
Hobbyist Programmer
 
hoffmandirt's Avatar
 
Join Date: Jul 2005
Location: PA
Posts: 125
Rep Power: 4 hoffmandirt is on a distinguished road
Send a message via AIM to hoffmandirt
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.
hoffmandirt is offline   Reply With Quote
Old Apr 12th, 2006, 11:26 AM   #2
InfoGeek
Professional Programmer
 
InfoGeek's Avatar
 
Join Date: Jun 2005
Location: India, The great.
Posts: 435
Rep Power: 4 InfoGeek is on a distinguished road
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.
InfoGeek is offline   Reply With Quote
Old Apr 12th, 2006, 12:00 PM   #3
hoffmandirt
Hobbyist Programmer
 
hoffmandirt's Avatar
 
Join Date: Jul 2005
Location: PA
Posts: 125
Rep Power: 4 hoffmandirt is on a distinguished road
Send a message via AIM to hoffmandirt
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.
hoffmandirt is offline   Reply With Quote
Old Apr 12th, 2006, 12:20 PM   #4
Seif
Hobbyist Programmer
 
Seif's Avatar
 
Join Date: Jan 2006
Location: UK
Posts: 242
Rep Power: 3 Seif is on a distinguished road
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.
Seif is offline   Reply With Quote
Old Apr 12th, 2006, 12:58 PM   #5
InfoGeek
Professional Programmer
 
InfoGeek's Avatar
 
Join Date: Jun 2005
Location: India, The great.
Posts: 435
Rep Power: 4 InfoGeek is on a distinguished road
Quote:
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.
My bad. When I read generalization and extends(or inheritance), I thought about inheritance of classes and not use cases. Sorry for that.
__________________
PFO - My daily dose of technology.
InfoGeek is offline   Reply With Quote
Reply

Bookmarks

« Previous Thread in Forum | Next Thread in Forum »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump




DaniWeb IT Discussion Community
All times are GMT -5. The time now is 2:15 AM.

Powered by vBulletin® Version 3.7.0, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2007 DaniWeb® LLC