Win a copy of Practical SVG this week in the HTML/CSS/JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

UML Use Case....need help again

 
Pappu Kumar
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
Oh the stink of it! Smell my tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!