Objects by Design Forums Here you can view your subscribed threads, work with private messages and edit your profile and preferences Registration is free! Calendar Find other members Frequently Asked Questions Search Home  
Objects by Design Forums : Powered by vBulletin version 2.3.5 Objects by Design Forums > Main Forums > UML Questions > Business vs System usecases
  Last Thread   Next Thread
Author
Thread Post New Thread    Post A Reply
Manikandan
Junior Member

Registered: May 2004
Location:
Posts: 21

Business vs System usecases

Hi all,

I am not clear with business and system usecases.

From "UML Distilled" by Flower, chapter 3 usecases:

Business and System Use Cases:
......
"Often you hear people talk about system use cases and business use cases. The terms are not precise, but the general usage is that a system use case is an interaction with the software, whereas a business use case discusses how a business responds to a customer or an event."
.......

Here:

...a system use case is an interaction with the software...
Here my perception is like...for example "in usage of ATM..", user withdrawing cash from ATM..That is... user is interacting with the ATM(ie system) by entering PIN number, selecting menu option, entering amount, getting cash & receipt...Thereby completes the usecase. Is my perception is right here?


...business responds to a customer or an event...
Here unless user/actor interacts, how business will respond ?
Here the business encapsulates the system..right ?

I am not able to differentiate the system and business usecases..

Please input your thoughts to clear my doubts on this...

rgds,
Manikandan

Last edited by Manikandan on 07-05-2004 at 06:04 AM

Report this post to a moderator | IP: Logged

Old Post 07-05-2004 06:02 AM
Manikandan is offline Click Here to See the Profile for Manikandan Click here to Send Manikandan a Private Message Find more posts by Manikandan Add Manikandan to your buddy list Edit/Delete Message Reply w/Quote
RUPractitioner
Junior Member

Registered: Jan 2004
Location: Moscow, Russia
Posts: 16

Lightbulb Business Use Case relared definitions

Hi,

.. whereas a business use case discusses how a business responds to a customer or an event."

That's right. From RUP v2003 documentation:

A Business Use Case describes a business process from an external, value-added point of view.
Business Use Cases are business processes that cut across organization boundaries, possibly
including partners and suppliers, in order to provide value to a stakeholder of the business.

Business Use Cases are useful for anybody who wants to know what value the business provides
and how it interacts with its environment.
Stakeholders, business-process analysts, and business
designers use Business Use Cases to describe business processes and to understand the effect
of any proposed changes (for example, a merger or a first CRM implementation) on the way
the business works. Business Use Cases are also used by system analysts and software architects
to understand the way a software system fits into the organization.
Test managers use Business
Use Cases to provide context for developing test scenarios for software systems. Project managers
use Business Use Cases for planning the content of business-modeling iterations and tracking progress.


Here my perception is like...for example "in usage of ATM..", user withdrawing cash from ATM..That is... user is interacting with the ATM(ie system) by entering PIN number, selecting menu option, entering amount, getting cash & receipt...Thereby completes the usecase. Is my perception is right here?

In that story, User mostly interacts with ATM machine (and its software) --which is a key "object" but not with the Bank representing business. Therefore, its a system UC not business one. Now suppose the User interacts with the Bank (through its employee) when he wants to open an account and obtain a PIN --no ATM, no software in here, only employee (business worker) and the User (business actor). This is business UC

Here unless user/actor interacts, how business will respond ?
Here the business encapsulates the system..right ?


Business can respond through its business worker (by sending an e-mail with lost PIN code to the User, for example) --this way doesn't involve an ATM (and its software as the system being developed)

---
Finally a few more definitions from RUP documentation becuase these definitions can be used with any SDP that uses UML and Use Case approach, and for future discussion:


business actor (class)
Defines a set of business-actor instances, in which each business-actor instance plays
the same role in relation to the business.

business actor (instance)
Someone or something, outside the business that interacts with the business.

business analysis model
An object model describing the realization of business use cases.
Synonym: business object model.

business entity
A business entity represents a significant and persistent piece of information that
is manipulated by business actors and business workers.

business event
A business event describes a significant occurrence in space and time, of importance
to the business. Business events are used to signal between business processes and
are usually associated with business entities.

business process
A group of logically related activities that use the resources of the organization
to provide defined results in support of the organization's objectives. In the RUP,
we define business processes using business use cases, which show the expected
behavior of the business, and business use-case realizations , which show how that
behavior is realized by business workers and business entities. See also: process.

business use-case (class)
A business use case defines a set of business use-case instances, where each instance
is a sequence of actions a business performs that yields an observable result of value
to a particular business actor. A business use-case class contains all main, alternate
workflows related to producing the "observable result of value".

business use-case (instance)
A sequence of actions performed by a business that yields an observable result of value
to a particular business actor.

business use-case model
A model of the business intended functions. The business use-case model is used as an
essential input to identify roles and deliverables in the organization.

business use-case package
A business use-case package is a collection of business use cases, business actors,
relationships, diagrams, and other packages; it is used to structure the business
use-case model by dividing it into smaller parts.

business use-case realization
A business use-case realization describes how the workflow of a particular business
use case is realized within the business analysis model, in terms of collaborating
business objects.

business worker
A business worker represents a role or set of roles in the business. A business worker
interacts with other business workers and manipulates business entities while participating
in business use-case realizations.


Hope this helps

Report this post to a moderator | IP: Logged

Old Post 07-15-2004 04:23 AM
RUPractitioner is offline Click Here to See the Profile for RUPractitioner Click here to Send RUPractitioner a Private Message Visit RUPractitioner's homepage! Find more posts by RUPractitioner Add RUPractitioner to your buddy list Edit/Delete Message Reply w/Quote
Manikandan
Junior Member

Registered: May 2004
Location:
Posts: 21

Thanks RUPractitioner for the reply...

rgds,
Manikandan

Report this post to a moderator | IP: Logged

Old Post 07-23-2004 01:21 PM
Manikandan is offline Click Here to See the Profile for Manikandan Click here to Send Manikandan a Private Message Find more posts by Manikandan Add Manikandan to your buddy list Edit/Delete Message Reply w/Quote
Powdrhound
Junior Member

Registered: Apr 2004
Location: Wellington New Zealand
Posts: 10

I agree with Rupractitioner .
But when I am engaging with a new customer in determining their business requirements, I will take them through an excerise of determining their affected processes end to end.

each step is a candidate business use case (even where the role is performed by a system).
I say upfront "there is no system in this world" The reason for this is that it forces the customer to think in terms of what their business requires as opposed to how it works in an existing system.
What comes out is a set of pure business requirements devoid of any system. At this point we can work with the customer to determine what requirements (that we have already identified) should be met by the system and how. Those affected business use cases are developed into system Use Cases.

Report this post to a moderator | IP: Logged

Old Post 09-21-2005 11:17 PM
Powdrhound is offline Click Here to See the Profile for Powdrhound Click here to Send Powdrhound a Private Message Find more posts by Powdrhound Add Powdrhound to your buddy list Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 04:47 PM. Post New Thread    Post A Reply
  Last Thread   Next Thread
Show Printable Version | Email this Page | Subscribe to this Thread

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 

< Contact Us - Objects by Design >

Powered by: vBulletin Version 2.3.5
Copyright ©2000 - 2018, Jelsoft Enterprises Limited.
Copyright 1999-2005, Objects by Design, Inc.