• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

how to refer other use case in sequence diagram

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, all
I have 2 questions regarding sequence diagrams.
1. in the Prepare Itinerary use case, Pricing the Itinerary is one of the steps. How should i represent it in the diagram? Do I have to include the details of pricing in Prepare Itinerary or I can just draw an object with stereotype <<use case>> and have a message called something like "forward" sent to it?
2. if u r using Together 6.0, can u please tell me how i can label a returned message? I would like to label them with the VOs sent back.
Thanks for the help.
-tomas
 
tomas suzuki
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
can someone please help?
thanx.
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One usecase calling another usecase is pretty common however, I have not seen usecases being referred directly in sequence diagrams. What I have seen( and used) is actors being used in seq. diagrams. For instance, you can model a whole subsystem as an actor("payment processing") and use it in the seq. diagram.
If I were you, I will not be using those "rare" UML features and find a way around to represent the same concept in a more standardized way that employs common and easy to understand notations. I am not sure if you have a situation that makes this option inevitable, so I cannot offer you alternatives.
[ May 27, 2003: Message edited by: Ajith Kallambella ]
--------------------
Ajith M. Kallambella
SCJP2, SCWCD, IBM-XML Dev, SCEA.
Co-author of Java 2 Certification Passport
For more details, check it out
discuss on extends use case
 
tomas suzuki
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Harvey,
Thanks for your reply.
[I am not sure if you have a situation that makes this option inevitable, so I cannot offer you alternatives. ]
One of the situations is that in the Prepare Itinerary sequence diagram, the system needs to price the itinerary before sending back the confirmation window. Since Price Itinerary is itself a sequence diagram requested by the project, do I use some sort of notation in the Prepare Itinerary seq. diagram to reference the Price Itinerary seq. diagram OR do i include the steps of pricing itinerary in the Prepare Itinerary diagram?
I would like to know how everyone else is dealing with this.
Thanx again for the help.
-tomas
 
reply
    Bookmark Topic Watch Topic
  • New Topic