UML Modelling in Colour with Archetypes
In effective object and component models across domains we see four major kinds of classes or four major class categories appear again and again. We associate each of these class categories with a colour to form an archetype - a prototype or typical specimen. That is, a little building block that you use again and again in your models. And when you see one of the four archetypes, you know what attributes (data elements), methods (functions), associations (connections to other classes) and interactions with other classes you more or less expect to see.
For example, a yellow is a Role - a way of participating in something. A role can be played by a party (a person or an organisation) or by other things as well. Whenever we see a Role in a model we know that it is yellow and here are the kinds of attributes, methods, associations and interactions we expect to see - more or less - for that class. Whenever we see a moment or interval of time we know that it is pink and also the attributes, methods, association and interactions we expect to see - more or less - for that class.
The four archetypes - blue, green, yellow and pink - connect together in a very repeatable and predictable way to form a larger Archetypal Domain Shape - a model shape that applies across all domains. We simply start customising the archetypes for this domain area and determining whether we need each of the blue, green or yellows. That is, whether we need that level of specificity.
A simple, systematic way to rapidly develop method-rich object models across all domains.