Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
The moose likes OO, Patterns, UML and Refactoring and the fly likes UML Use Case....need help again Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "UML Use Case....need help again" Watch "UML Use Case....need help again" New topic
Author

UML Use Case....need help again

Pappu Kumar
Ranch Hand

Joined: Oct 01, 2002
Posts: 69
This is in continuation of the posts i had made earlier.
I use Rational Rose for Java for my modelling.
I have a requirement where the user does many operations on a entity(ex. Client). In my use case diagram i was able to bundle all these operations under add/modify/delete client. But the clients wants to see all operations under those three use cases. I added another use case diagram under those three use cases as (add details/modify details/delete detaiils). Is that a good technique ? If try to display all use cases in the Main use case diagram....it gets too too congested and hard to read.
My questions are :
1.) Was my approach right ?
2.) Should i use Sequence Diagrams ? instead of having a detail Use Case Diagram inside every Use Case , i would have a Sequence Diagram for each (add/modify/delete use case) ?
3.) Any suggestions as to whats the right way to implement this ? and also letting the client see all their operations
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by Pappu Kumar:
I have a requirement where the user does many operations on a entity(ex. Client). In my use case diagram i was able to bundle all these operations under add/modify/delete client. But the clients wants to see all operations under those three use cases.

Why? What does he use the diagram for?

I added another use case diagram under those three use cases as (add details/modify details/delete detaiils). Is that a good technique ?

Did it make your client happy?
If try to display all use cases in the Main use case diagram....it gets too too congested and hard to read.
My questions are :
1.) Was my approach right ?

Can't tell from here wether it was the best approach, but it certainly isn't a bad one in general...

2.) Should i use Sequence Diagrams ? instead of having a detail Use Case Diagram inside every Use Case , i would have a Sequence Diagram for each (add/modify/delete use case) ?

A sequence diagram is typically used to show the chronology of events. From your description, I doubt that it would have communicated better...
3.) Any suggestions as to whats the right way to implement this ? and also letting the client see all their operations

I don't think I understand this question. What exactly do you mean by "implement"? How do you decide about its rightness?


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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: UML Use Case....need help again