You should not use generalization of actors just to capture common behavior.
The generic actor (as Olaf said) has to be reasonable, it has to really
represent a role played by users of the system you are modeling. Using
generic actors just to factor out common behavior might make diagrams
simpler (cleaner), yet less legible, understandable.
Also, take care with actors named "User". It is commonly desirable to avoid
naming an actor a "User" since virtually all humans interacting with your
system may play the "User" role. And remember, the more difficult it is to
name your actor, the more probable the actor is being wrongly modeled.
As for your original question (modeling sequence diagram with two primary
actors), I usually insert an actor with an unespecified type in the sequence
diagram, and put a note attached to it to declare its possible types.
Best,
Ricardo.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of M�nnig, Olaf
> Sent: Wednesday, September 19, 2001 4:36 AM
> To: 'Ryan Martin'; [EMAIL PROTECTED]
> Subject: RE: (ROSE) Modeling Collaboration/Sequence diagrams with 2
> Primary Actors?
>
>
> AcessoBOL, s� R$ 9,90! O menor pre�o do mercado!
> Assine j�! http://www.bol.com.br/acessobol/
>
>
>
>
> I would do so. Actually, I had the same problem, and modeled a
> generalization of actors. It works fine!
>
> However, what does "working fine" mean? We built a pure
> analysis model, and,
> well, by nature we have no problems with generalization of actors. You
> should exactly evaluate, if generalization is possible and
> reasonable (as
> you do with classes).
>
> Greetings,
> Olaf
>
> -------------------
> Diplom-Informatiker Olaf M�nnig
> T-Systems
> debis Systemhaus GEI GmbH
> Martin-Schmei�er-Weg 18, D-44227 Dortmund
> Telefon: +49 (231) 9744 664
> Telefax: +49 (231) 9744 600
> E-Mail: [EMAIL PROTECTED]
> Internet: http://www.t-systems.de <http://www.t-systems.de/>
>
> -----Original Message-----
> From: Ryan Martin [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 18, 2001 10:49 PM
> To: [EMAIL PROTECTED]
> Subject: (ROSE) Modeling Collaboration/Sequence diagrams with
> 2 Primary
> Actors?
>
>
> Hey All,
>
> I have a use case "Request A Report" with two primary actors
> (Carrier and
> Customer). Writing
> the use case was fairly easy just referring to the Actors
> like so: "The
> Carrier/Customer navigates to..."
>
> But now that I've moved onto Collaboration Diagrams and most
> importantly
> Sequence Diagrams,
> I'm stumped on how this should be modeled to represent the
> two Actors for
> the one behavior (Request A Report).
>
> The overall system I'm building is web based, with two
> identified actors,
> Carrier and Customer. For functionality that is used
> by both actors should I document and model using a User
> actor? Meaning,
> should I use generalization:
> Carrier and Customer are "types of" Users.
>
>
> **************************************************************
> **********
> * Rose Forum is a public venue for ideas and discussions.
> * For technical support, visit http://www.rational.com/support
> *
> * Admin.Subscription Requests: [EMAIL PROTECTED]
> * Archive of messages:
http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages: http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
