![]() |
Telelogic TAU (steve huntington) | ![]() |
Topic Title: Analyst stereotypes Topic Summary: having actor and package in same diagram Created On: 6-Dec-2007 20:36 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Is it possible to have actors and packages in same diagram. Essentially, I want to model containers of usecases?
I tried to play with the stereotypes, but could not assign an actor stereotype to package diagram, and could not add package to usecase diagram. I could not find an Analyst forum, so posted to this group. Please advise if I need to post to another group. Thanks, --Greg |
|
![]() |
|
![]() |
|
The diagram types are designed to enforce certain UML concepts for creation an representation in the diagram. However you can often drag & drop items which you are not allowed to create onto a diagram. In your example you may wish to create a set of hierarchical packages with names describing what they contain. Containment of the packages can be indicated by a 'containment' line or by drawing the packages inside one another. To show the actors in the packages drag them from the model browser onto the diagram. In your case you may want to place them within the packages that own them. You won't receive the stick figure, but you will receive a symbol with the name and the appropriate stereotype indicated. You can then navigate from these as you can on any diagram.
|
|
![]() |
|
![]() |
|
Hi Greg,
I guess you have a few options... a) use a Subject Symbol. That's probably the best way to "group" use cases. But, you only get 1 per UC diagram, which isn't too bad. However it does not really do a lot for 'containment' hierarchy in the Model View. Depends if the picture is sufficient or not for you. b) group them in a package hierarchy in the Model View instead of graphically on the diagrams (generally Use Cases are "flat") c) you can put Classes on a Class Diagram and stereotype them <<actor>> d) you can group a set of Use Cases under a Collaboration in the Model View. Each Collaboration then is one grouping of use cases. A Collaboration can be visualized on a Class Diagram as a dashed circle. You can connect it to <<actor>> stereotyped Classes. A Class Diagram can also have Packages on it. Collaborations can have Use Case Diagrams and Use Cases contained in them. Generally, you are not allowed to put Packages on a UCD, that's illegal UML. Same as putting an <<actor>> stereotype on a Package Diagram. They are only allowed on Classes. Greg ------------------------- Greg Gorman Vice President, Product Management Modeling and Test Products Telelogic AB |
|
![]() |
|
![]() |
|
By the way. If you are using D/A then I like to use the "Advanced" view instead of the more limited Analyst View. Hit the "+/-" button to get the bigger display that shows the Model View and Message windows. Then right click on the menu bars and turn on the standard menus (I don't have my VMWare booted so I am running from my very poor memory...).
Select View->Reconfigure Model View or press Alt+4. Then select "Standard View". You get a more detailed hierarchy in the Model View and a little more access to advanced model structure. Greg ------------------------- Greg Gorman Vice President, Product Management Modeling and Test Products Telelogic AB |
|
![]() |
|
![]() |
|
Thanks. I guess I really need a profile. However, I think I can do item c on your previous list.
Thanks all for your input. --Greg |
|
![]() |
Telelogic TAU
» TAU/Developer
»
Analyst stereotypes
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.