component diagram -- multiple stereotypes per component??

[Andrew Zilahi]

MagicDraw allows for multiple stereotypes attached to a component. For instance, ItineraryManager <<Stateful Session Bean>> <<Session Facade>>. Does this sound ok?

Would be curious to find out how others convey same info in the component diagram?

Also, does anyone follow Cade's approach to create a component diagram per use case? It would come handy, as MagicDraw eval version prevents me from using more than 20 components per diagram...

regards,
Andrew
[ December 20, 2006: Message edited by: Andrew Zilahi ]

[Deepak Pant]

It is my understanding that typically only one stereo type is used in UML.

It doesnot matter how many component diagrams you make. I made just one diagram and got full marks.

[Dan Drillich]

Andrew,

The assignment speaks clearly about one component diagram and you know, it makes perfect sense, as in one diagram all the components and their relationships are displayed.

I think we heard in this forum about people who submitted multiple component diagrams. Try to search a bit....

I use Jude that doesn't impose a limit on the number of components.

About multiple stereotypes - The fact that MagicDraw and Jude and probably other tools allow multiple stereotypes show that it can bring value. Anything that can bring order in a standardized way is a good thing in our IT world .
Just be consistent with the use of stereotypes.

Regards,
Dan