Domain Analysis by Color Modeling

There are many methods for domain modeling, and different models may be produced for the same problem domain by applying different modeling approaches. So, I often hear such a question: How to ensure the correctness of the modeling process?
It sounds like a straightforward question, but in fact it could be more complicated than we might expect. Firstly, we need to make clear what is the purpose of modeling. If it is just for describing problems, then there is no right or wrong modeling, but only differences resulting fromvarious point of views and perspectives; however, if we are talking about modeling an enterprise business system, then, the question should be changed to: “How can we ensure the model is capable of supporting the operation of an enterprise?”
I would like to answer this question in brief with the following example.
Before carrying out analysis and modeling, we have to know what the purpose of an enterprise business system is. Generally, the purpose of enterprise business systems is relevant to the demands of decision makers or management. The next step is to empathize with a manager, and to find out what his or her demands are exactly.
Now, assume that you are a COO of an online eBook store. One day, a customer suddenly complains to you that one book he bought is missing, and the total price is miscalculated, that he overpaid some money. Before you make a commitment to settle the claim, you should firstly verify whether what the customer said is true. To do that, do you know what information is helpful for you to make an accurate judgment?
To put it simply, you need to know which books were ordered and how much money was paid by the customer, and which books were delivered actually by the bookstore. Unfortunately, due to the limitation of technology, you are unable to see what has happened. You don’t havedrive a time machine to drive and see. But fortunately, you don’t need to do so; instead, you can obtain the relevant information by checking the order form of the customer, the transaction record of your e-bank and the stub of express waybill delivered by your bookstore to the courier.
You check the order form and the stub of the courier waybill, and you find out that the customer ordered the books three days before, and your bookstore already sent out those books the day before yesterday. Besides, you also learn from the order form that the customer ordered seven books in total, but on the waybill there is only information about address, parcel number, postage and weight, without any information relevant to books. And now, you think you should ask the distribution department for more details.
From the distribution department you find out details about the parcel based on itsparcel number, and sure enough there are only six books. Besides, you find a delayed delivery order which indicates that due to stockout, one book bought by the customer is prepared to be delivered.
So, the remaining matter is payment. From the e-banking record, the customer paid a total amount of 132.5 excluding postage; the amount shown in the order form is also 132.5, which clearly indicating that the customer didn’t overpay.
To ensure the correctness, you re-select those seven books on the website to see whether the price is right or not. However, it is surprising that the total amount is only 128.3. After a careful verification, you find out that one of the books is now on sales promotion. And now, the problem is when did the sales promotion start?
The market department shows you a recent promotion plan, and you find that the book in question was on sales promotion from yesterday. That is to say, the customer placed the order before the sales promotion started.
And then, you might think you should make a phone call to your customer to apologize, to discuss book prices, and to explain the sales promotion.
Do you think this is too much for a COO? It is certainly a fictional example.


