Win a copy of Microservices Testing (Live Project) this week in the Spring forum!
  • 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
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

how model include in sequence diagram?

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've looked through a few books and have not seen how to model this.
what is the proper way to develop a sequence diagram for a use case that << include >> another?
for example, [distributor search] --- << include >> ---> [login]
I am using analysis classes in my seq. diagram classified as either boundry, controller, or entity.
for [distributor search], do i have a class called [login] with sterotype << usecase >> with a message going from my controller to [login] labeled << include >> ?
for [login], do i have a class labeled [distributor search] << usecase >> with message going to the entity? should it instead go to the controller?
[ November 03, 2003: Message edited by: Matt Dole ]
 
Ranch Hand
Posts: 260
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Matt Dole:
I've looked through a few books and have not seen how to model this.
what is the proper way to develop a sequence diagram for a use case that << include >> another?
for example, [distributor search] --- << include >> ---> [login]
I am using analysis classes in my seq. diagram classified as either boundry, controller, or entity.
for [distributor search], do i have a class called [login] with sterotype << usecase >> with a message going from my controller to [login] labeled << include >> ?
[ November 03, 2003: Message edited by: Matt Dole ]


Message from controller to login <<usecase>> can be login user instead of include.

for [login], do i have a class labeled [distributor search] << usecase >> with message going to the entity? should it instead go to the controller?
???this i could not get what you are trying to say.
What is the use case you are trying to model you sequence diagram???
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What are you modeling - is it an analysis, or a design diagram?
 
reply
    Bookmark Topic Watch Topic
  • New Topic