It’s possible to show the name of the owning package for an actor displayed in a use case diagram?
I would like to display it 'cause I’m modelling a system for an hospital and I would put in evidence that a “Doctor” actor is extending the “Operator” actor. Whereas the Operator is contained in a package-model containing all the stuff of a pre-existing system, while the “Doctor” actor is placed in another package containing all of the hospital stuff.
SInce Actor are no more classifier in UML 2.0 this option seems no more available… but I think it would be nice to have. In the attached image there is an example of what I would like to display. Screenshot at 2012-08-27 17:10:20.png
Obviously I don’t want to pretend to know things better than the authors themselves (I honestly don’t :lol:) but because I know that its easy to overlook options in this extensive software (been there, done that myself several times :mrgreen:) I can’t help sharing this anyway:
Keep in mind that VP-UML allows you to add text snippets to your diagrams. Sure; by default they pop up in a blue squared object but that is easily changed:
[list]
Go to the ‘Freehand’ section in the ‘diagram menu’ and select 'Text’
Click somewhere and add the text to your diagram. I know; now you have a blue section with your text, not what you want.
Right click: Styles and Formatting -> Transparent. That’s one, but you still have a border.
Now: Right click again, Styles and Formatting -> Formats… Set the Style to ‘None’, click Ok.
When you have your text object selected you still see a dotted (striped) border. Don’t let that fool you, the moment your object is not selected you’ll only end up with plain text.
Now its easy: move the text object onto the right place (below your actor) and you can mimic the behaviour you mentioned above. I know this isn’t a one-on-one solution (and it could be tedious to maintain should you ever have the need to rename the package, but I figured I’d mention this anyway. Its a little bit of a hack, but VP-UML can provide if need be.
thanks for the workaround. Unfortunately, during the analysis phase, I always very often change names, packages and organization of things until I’m not satisfied (you know, representing a system is always a continue refinements loop).
So writing a free text is not the best solution…
