The point of a model – of any sort- is to take some aspect of the real world and create an abstraction of it. Then use that to help do something new. How much of The World you choose to model can be a burden. A really big one. So choose your scope carefully, and only model what you NEED to model , and what you have time to understand.
I was once asked to review a model built by some experts in ecology. They wanted to model the causes of ecological threats, especially pollution, and what happens as a result. This could then serve as the basis for ecology-related software solutions.
As is often the case with model reviews, I’m shown into a meeting room with lots of smart people – industry experts – and me. I usually get a bad feeling when they all sit on one side of the table, and put me on the other. Sets a non-collaborative tone. So they explained their model was in three halves, set out on a HUGE whiteboard:
- The left-hand side, bit which set out the main pollutants: animals, vegetable, mineral. Well thought through, very comprehensive
- The right-hand side, which had all the effects of pollution: death, disaster etc. Also seemed well modelled.
- They said the middle bit was a problem.
It was a while ago, but I’m sure that the middle bit, where they were going to describe how the pollutants on the left CAUSED the effects on the right, contain one class. It was called: