Design: Scope and other Decisions

The property level concept maps coming out of the understanding phase still need some consideration.
Let us revisit the Supplier Parts context:
Stacks Image 61
Notice that Status is a property of Supplier. First of all this means that the naming could be improved, SupplierStatus would be more appropriate. Another thing is that Status might, in fact, be a business object in its own right. Frequently things like this have both a code (number, whatever) and a value (description). If that is important, it should be modeled at the concept level.

The concept model that is to be delivered is the requirements specification of a to be data model. At this point in time we are not much concerned about data modeling issues like keys, uniqueness etc.

What matters most at this time is scope. Is it the right concepts we push forward to the data model? Is it too much, too little? Can we phase it? Break it down into agile sprints? This is a lot of business decisions and that is was design is all about.
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