Making Sense of the Concepts

The initial concept maps from the exploration phase are carry information about concepts and the terminology used.
Let us assume that we have been doing a bottom up analysis of three tables in a relational database:
Stacks Image 61
(Yes, they are some of Chris Date's favourite examples).
Concept models use named relationships. Naming the relationships adds a new level of powerful information. Some relationships are rather vague (using the verb “has,” for example). Other relationships are much more business-specific (for example, “supplies.”) The data modeler must work with the business to find helpful, specific names for the relationships.

The presence of a verb in the relationship between supplier and city, for example, could well mean that it is not a straightforward property relationship. In fact, cities do not share identity with suppliers; suppliers are located in cities. (This is how to resolve functional dependencies.)
All concepts in concept model, which have simple relationships (has, is...), and which only depend on the one and same referencing concept, can be reduced to actually being just properties of some concept, which represents a business object.

Visually we represent the properties like rounded rectangles and the relationship between object and property is without arrowhead:
Stacks Image 81
This representation carries a lot of meaning. The relationships in particular communicate about processes going on, which are related to the Supply chain. At this stage we know much more about the business area, we have been exploring and mapping.
You may follow the sequence or explore the site as you wish:

You could also take a look at the book about Business Concept Mapping:

Stacks Image 54