wood burning stoves 2.0*
The moose likes OO, Patterns, UML and Refactoring and the fly likes UML - Use Cases Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "UML - Use Cases" Watch "UML - Use Cases" New topic
Author

UML - Use Cases

Sarikaa Bhatnagar
Greenhorn

Joined: May 10, 2005
Posts: 26
Hello All,

I am new to UMl and in the process of learning. Can someone tell me whether we identify the actors for each module or for the entire system.

Secondly, is the task performed by each actor is one use case.

Thanks,
Padmaja Godbole
Greenhorn

Joined: May 10, 2003
Posts: 14
Hi Sarika,

Following is my understanding about the Use Cases :

Use Cases define the scope of the system, they are very similar to requirements, they enable us to visualise size and scope of the entire development.

The sum of the use cases is the whole system, that means anything not covered by a use case is out side the boundary of the system we are developing

Now the answer of your question is :
One can identify Actors for a Module as well as for the whole system, it depends upon the UML diagram he/she is preparing for.

Use Cases that are presenting a Module will include actors involved in that Module only.
[ May 11, 2005: Message edited by: Padmaja Godbole ]

Padmaja Godbole<br />---------------------<br />SCJP2
Padmaja Godbole
Greenhorn

Joined: May 10, 2003
Posts: 14
And also task performed by each actor will be a use case but granular tasks should not be included, only the main main tasks will make the possible Use Cases.

Is my understanding up to the mark ranchers?
Scott Ambler
author
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
You might find some of the links at Agile Models Distilled to be helpful. There are several links to use case related topics.

- Scott


<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
Sarikaa Bhatnagar
Greenhorn

Joined: May 10, 2005
Posts: 26
Hey Scott,

Thanks a lot! The link is really good and useful
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Also notice that the bubbles in use case *diagrams* are just placeholders for the *actual* use cases, which are textual.

Depending on the reason for modeling use cases, getting the different types of actors right probably isn't particularly important.


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
Showing different types of actors is sometimes helpful when communicating with business folks, but they don't always affect the software much. If you know you have to have a mechanism for things some users can do and others cannot, it will probably handle 2 types of actors or 200 the same. Non-human actors are interesting to me because they imply some kind of protocol and API with other systems.


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Scott Ambler
author
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
The line between an actor and a use case implies an interface of some sort. When the actor is a human, it's a user interface. When the actor is a system, it's a system interface.

- Scott
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: UML - Use Cases