Eric,

Original question:
Does anyone know if there is any kind of requirement that use cases in
extent and include relationships must always be abstract use cases?

You teach a Rational OOA&D class and you do not know what an abstract use
case is?  I don't know what to say to that.  An abstract use case is one
that is not complete - can not stand by itself and can not be connected to
an actor (versus a concrete use case which is always connected to an actor).
This definition (I paraphrased of course) can be found in the OMG UML Spec,
all of the 3-A's books on UML and UP as well as just about every use case
book I've read.  I'm sure your going to shake your head and go 'oh yeah...'.

Anyway I found the answer to my question... I guess. Interestingly I
searched the OMG specification and also the 3-A's UML Reference and User
Guide and could not find anything on my particular question.  Maybe I just
missed it.  Also, so far, replies from the industry (this forum, newsgroups,
cafes) all say 'unknown' or 'not that I know of'.

 However, in the RUP eCoach (i.e. the web pages that describe RUP), in the
sections on:
* Guidelines: Include Relationship
* Guidelines: Extend Relationship

It states that:
* Included use cases are 'always' abstract
* Extended use cases 'may be' abstract

Hmm... is that really the 'standard'?  I guess that it makes sense based on
the strict definitions (although it's going to change some of what we've
done).  Live and learn...

Thanks!
Rusty
---------------------------------------------------------------
Rusty Williamson
Sr. Systems Architect

Corporate Office
GERS, Inc.
10431 Wateridge Circle * San Diego, CA 92121
(800) 854-2263 * CA (858) 457-3888
FAX (858) 484-9237 * Desk (858) 484-9237
E-mail:  [EMAIL PROTECTED] * Web http://www.gers.com
"e-Business Solutions for the Consumer-Driven World"


 -----Original Message-----
From:   Aker, Eric [mailto:[EMAIL PROTECTED]] 
Sent:   Wednesday, March 21, 2001 11:00 AM
To:     'Williamson, Rusty'; 'Rose Forum'
Subject:        RE: (ROSE) UML question number one

No there is not.
What is a "abstract use case"?
I know what an abstract class is.

Eric Aker

-----Original Message-----
From: Williamson, Rusty [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 21, 2001 10:14 AM
To: 'Rose Forum'
Subject: (ROSE) UML question number one



Hello,

Does anyone know if there is any kind of requirement that use cases in
extent and include relationships must always be abstract use cases?

Thanks!
Rusty
---------------------------------------------------------------
Rusty Williamson
Sr. Systems Architect

Corporate Office
GERS, Inc.
10431 Wateridge Circle * San Diego, CA 92121
(800) 854-2263 * CA (858) 457-3888
FAX (858) 484-9237 * Desk (858) 484-9237
E-mail:  [EMAIL PROTECTED] * Web http://www.gers.com
"e-Business Solutions for the Consumer-Driven World"

************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages: 
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************

Reply via email to