Re: links & messages



Date view Thread view Subject view Author view

Jos Warmer (J.Warmer@klasse.nl)
Thu, 20 Jan 2000 16:10:14 +0100


At 05:02 PM 19-01-00 +0000, John Daniels wrote: >[Robert France wrote:] >> A rule I use (and I would like feedback on the >> problems) is that a high-level design Class Diagram should show only >> persistent >> associations (i.e., associations whose links persist between >> operation invocation) > >I think that is exactly right, and really the intention in UML. I can't >see any problems with this. > >--John Daniels > Fully agreed. In UML collaboration diagrams you can have links with different kinds of stereotypes: - <<association>> link, - <<parameter>> link, - <<local>> link, - <<global>> link, - <<self>> link. In UML class diagrams you can have associations with the same set of stereotypes: - <<association>> association, (this is the default, but is defined as a stereotype as well) - <<parameter>> association, - <<local>> association, - <<global>> association, - <<self>> association. You can show e.g. <<parameter>> associations in a class diagram. However, common practice is to show only <<association>> associations in a class diagrams. Adding non-<<association>> associations is not mandatory and will most probably clutter your class diagram. UML allows you to take any approach you want. That is what UML should do, because it is just a language. How you use it in a project is up to yourself. UML is a very broad language and can be used in many different ways. This is both the strength and a potential weakness of the language.... Regards, Jos Warmer _____________________________________________________ Klasse Objecten tel : +31 (0)35 6037646 Chalonhof 153 fax : +31 (0)35 6037647 3762 CT Soest email : J.Warmer@klasse.nl The Netherlands internet: http://www.klasse.nl


Date view Thread view Subject view Author view