Talk:Class diagram/Archive 1

Simple diagrams
Thomas G. Marshall: Can someone please put together some simple diagrams here? I would try, but would undoubtedly get something wrong.

Multiplicity
Multiplicity * means 0..*, not "more than one". And, is also known as Cardinality.

Source: "Unified Modeling Language: Superstructure version 2.0, formal/05-07-04", p. 109:

"A multiplicity with zero as the lower bound and an unspecified upper bound may use the alternative notation containing a single star “*” instead of “0..*.”" —Preceding unsigned comment added by Finem (talk • contribs)

Yellow SVG diagrams replaced by blue JPEG ones
I noticed that a past version of this article used a set of beautiful white and yellow UML diagrams. These have been replaced by in my view non-nice blue diagrams that in addition have a textual reference to a proprietary tool in their background. I would propose that someone takes these changes in diagrams back, or that someone creates another set of diagrams without the text about the proprietary tool in their background. Also, the yellow diagrams were SVG which is preferable to the current PNG. --Dan 17:55, 25 June 2006 (UTC)


 * Indeed. We do not want to have images with an ad inside. I've removed them from the article. --Ligulem 18:40, 25 June 2006 (UTC)

Generalization Example
The generalization example: "a sedan is a type of vehicle" will not be clear to readers unfamiliar with the term sedan (e.g. UK residents). Would "a car is a type of vehicle" be a better example? —The preceding unsigned comment was added by Special:Contributions/ (talk)

Role names
Could someone with the tool producing the UML diagram samples, please present an example using association end (role) names. This is an essential feature of class diagrams.--EvenT 08:58, 31 October 2007 (UTC)

Done. esap 15:29, 31 October 2007 (UTC)

Class Diagram Description
This article is lacking an account of what the different symbols (+, -, etc) used in the method and attribute sections of a class diagram mean. A short sentence about parameters and return values for methods wouldn't be amiss either. 62.25.109.195 (talk) 08:41, 22 October 2008 (UTC)

I've added another column to the visibility table with definitions from the UML 2.0 Infrastructure - but I think they could use translating into simpler English, and the Package definition really needs summarising. 62.25.109.195 (talk) 11:15, 30 March 2009 (UTC)

Biological inheritance vs Class inheritance
Pertaining to the following:

Note that this relationship bears no resemblance to the biological parent/child relationship: the use of these terms is extremely common, but can be misleading.

What is the difference? I've thought of two guesses: - Only one parent instead of two? - Defining a new type, rather than a new instance of the same type?

What are the misconceptions UML users need to be wary of and avoid? 62.25.109.195 (talk) 08:53, 17 November 2008 (UTC)

Relationships - Realization
Re: "A realization is displayed in the diagram editor as a dashed line with an unfilled arrowhead towards the supplier."

The phrase "in the diagram editor" smacks of cut-and-paste from a UML software help file. Recommend that be removed. - Mwoodman (talk) 21:07, 12 March 2009 (UTC)

Agreed, and changed. 62.25.109.195 (talk) 11:00, 30 March 2009 (UTC)