First let's look at the definition of a Business Use Case and a Use
Case.
Business Use Case: The processes of a business are defined as a number
of
different business use cases, each of which
represents
a specific workflow in the business. A business use
case defines what should happen in the business when
it is performed; it describes the performance of a
sequence of actions that produces a valuable result
to
a particular business actor.
Use Case : In its simplest form, a use case can be described as
a
specific way of using the system from a user��s
(actor��s)
perspective. A more detailed description might
characterize a use case as:
- a pattern of behavior the system exhibits
- a sequence of related transactions performed by
an actor and the system
- delivering something of value to the actor
Use cases provide a means to: capture system
requirements,
communicate with the end users and domain experts,
and
test the system. Use cases are best discovered by
examining
the actors and defining what the actor will be able
to do
with the system.
>From these definitions it is clear that Business Use Cases are used to
capture
the high level busisness model -- they have nothing to do with the
system to be
designed except that they give the designer an understanding of how the
business
works. Once the designer has this understanding, they can move on to
Use Cases.
Use Cases deal with the system being designed -- they capture how the
system which
will be used by the business is required to work.
Once the Use Cases are set you should have a basic idea of what the
system is
required to do. Then it is time to move on to Use Case Realizations.
Use Case Realization: A use case realization is a graphic sequence of
events, also
referred to as a scenario or an instance of a use
case. These
realizations or scenarios are depicted in either a
sequence or
collaboration diagram. The two most common
scenarios are the
typical (or primary) scenario, where all is well
and the exception
(secondary) scenario, which addresses the
deviations. The
exception scenario address the "what if?" elements
of the use case.
So for each Use Case there will be one or more Uxe Case Realizations
that deal with
specific scenarios. It is in the Sequence Diagrams, Collaboration
Diagrams, Activity
Diagrams, and/or State Diagrams of the Use Case Realizations that you
begin to get an
idea of what objects will be needed to implement your system. From here
you move on
to designing the class hierarchy etc, etc...
Hope this helped.
-Frank
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of GZ MIS - Kent Liu
> Sent: Tuesday, July 16, 2002 6:12 PM
> To: [EMAIL PROTECTED]
> Subject: Re: (ROSE) Use Case
>
>
>
> To my knowledge, I guess business use case is refer to
> business module. After study the user requirement, then can
> get some business modules that all combine to be the whole
> business rule. Then the use case is the each scenario of the
> business use case. If using UML diagram, I guess can make the
> relation as below:
>
> ----------------------------- 1..n
> 0..n -----------------
> |Business Use Case| -------------------------------------|Use Case|
> -----------------------------
> -----------------
>
> Can anyone teach me does this right or not ?
> Thanks.
>
>
> -----ԭʼ�ʼ�-----
> ������: ANBEESWARAN Ramachandran [mailto:[EMAIL PROTECTED]]
> ����ʱ��: 2002��7��16�� 22:42
> �ռ���: rose
> ����: (ROSE) Use Case
>
>
>
> Hello All,
>
> If anybody have the idea about the 'business
> usecasee' and 'use case', is it possbile to make me
> clear about these use cases. Where we have to use
> these use cases.
>
> Thanks in Advance.
>
> Anbeeswaran.
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
> **************************************************************
> **********
> * Rose Forum is a public venue for ideas and discussions.
> * For technical support, visit http://www.rational.com/support
> *
> * Post or Reply to: [EMAIL PROTECTED]
> * Subscription Requests: [EMAIL PROTECTED]
> * Archive of messages:
> * http://www.rational.com/support/usergroups/rose/rose_forum.jsp
> * 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
> *
> * Post or Reply to: [EMAIL PROTECTED]
> * Subscription Requests: [EMAIL PROTECTED]
> * Archive of messages:
> * http://www.rational.com/support/usergroups/rose/rose_forum.jsp
> * 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
*
* Post or Reply to: [EMAIL PROTECTED]
* Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
* http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
* To: [EMAIL PROTECTED]
* Subject: <BLANK>
* Body: unsubscribe rose_forum
*************************************************************************
