Hello,
I am trying to come up with some rules for creating good, well formed use
cases. I'm referring to concrete use cases - ones directly connected to
actors. Our people are new to UML and use cases and keep coming up with use
cases like "Enter Line Item" (not a complete function), "Make Change" (not a
'system' function) and "Calculate Tax" (among other things, internal - an
analysis issue). We are trying to adhere to the OMG 1.3 UML Specification
and are using RUP.
Does anyone have any ideas or suggestions on this? Has anyone seen a list
of 'rules' posted anywhere?
Thanks in advance for any help!
Rusty Williamson
---------------------------------------------------------------
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
*
*************************************************************************
