how model include in sequence diagram?

[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 >> ?
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 ]

[william kane]

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???

[Ilja Preuss]

What are you modeling - is it an analysis, or a design diagram?