UML colors
From Wikipedia, the free encyclopedia
UML color standards are a set of four colors associated with Unified Modeling Language (UML) diagrams. The coloring system indicates which of several archetypes apply to the UML object. UML typically identifies a stereotype which is a bracketed comment for each object identifying whether it is a class, interface, etc.
These colors were first suggested by Peter Coad, Eric Lefebvre and Jeff De Luca in a series of articles in The Coad Letter, and later published in their book Java Modeling In Color With UML.
Over hundreds of domain models, it became clear that four major "types" of classes appeared again and again -- just named differently to suit the domain. These were termed "archetypes" (after much discussion) which is meant to convey that the classes of a given archetype follow more or less the same form. That is, attributes, methods, associations, and interfaces are fairly similar among classes of a given archetype.
When attempting to classify a given domain class, one typically asks about the color standards in this order:
-
- pink
- moment-interval — Does it represent a moment or interval of time? An example would be an object that temporarily stores login information during the authentication process.
- yellow
- roles — Is it a way of participating in an activity (by either a person, place, or thing)? Signing into a system as an administrator, which changes program behavior by requiring a password that guest accounts do not, is one example.
- blue
- description — Is it simply a catalog-like description which classifies or 'labels' an object? If users of a system are labeled based on the department of a company they work within and this doesn't change the way the system behaves, this would be a description.
- green
- party, place, or thing — Something tangible, uniquely identifiable. Normally, if you get through the above three questions and end up here, your class is a "green." The user of the system and the sub-sections of the system they visit are all PPTs.
Although the actual colors vary, most systems tend to use lighter color palettes so that black text can also be easily read on a colored background. Coad, et al, used the 4-color pastel Post-it notes, and later had UML modeling tools support the color scheme by associating a color to one or more class stereotypes.
Many people feel colored objects appeal to the pattern recognition section of the brain. Others advocate that you can begin a modeling process with a stack of four-color note cards or colored sticky notes.
The value of color modeling was especially obvious when standing back from a model drawn or projected on a wall. That extra dimension allowed modelers to see important aspects of the models (the pink classes, for instance), and to spot areas that may need reviewing (unusual combinations of color classes linked together).
The technique also made it easy to help determine aspects of the domain model -- especially for newcomers to modeling. For example, by simply looking first for "pinks" in the domain, it was easy to begin to get some important classes identified for a given domain. It was also easy to review the standard types of attributes, methods, and so on, for applicability to the current domain effort.
[edit] See also
[edit] References
- ^ The Coad Letter
- ^ The Coad Letter: Modeling and Design Edition, Issue 44. The original color scheme was changed slightly. Further articles appeared in issues 51, 54, 58-65 and others.
- ^ Peter Coad, Eric Lefebvre, Jeff De Luca: Java Modeling In Color With UML: Enterprise Components and Process, Prentice Hall, 1999, ISBN 0-13-011510-X
- Edward Tufte: Envisioning Information, Graphics Press, 1990, ISBN 0-9613921-1-8
[edit] External links
- Developing a UI Design from a UML Color Model
- Stephen Palmer (2002). A New Beginning. Retrieved on June 7, 2006. Appeared in The Coad Letter: Modeling and Design Edition, Issue 68
