What Should You Include in Your Model?

Many of the important choices you make in developing a model have to do with selecting aspects of the real system to include or not to include. One approach is to include everything that you are aware of, to ensure that you are not neglecting any important mechanism. The problem with this approach is it can be too time-consuming in terms of building the model and also that it can produce a model that is too computationally expensive. In other words, simulations may take longer to run than desirable, or than is necessary to get good results.

Choosing which behaviors to represent in a model is one of the most difficult tasks a modeler faces. This makes sense because the modeling effort is supposed to teach us which parts of the system are responsible for the system behaving or performing a particular way. Therefore, it is hard to know in advance which aspects of the system are significant. So, you are required to make a judgement call. Your decisions will later be backed up through validation. Your initial model should be based on a list of suspects if you are investigating a problem in your network, or if you anticipate possible problems with a future network or modified network. In other words, you should make an educated hypothesis about what will matter to answer your questions. Then, you can change your hypothesis and build several other models that emphasize different aspects of the system. This will help you learn what is significant and what is not with respect to your particular objectives.

When working in a component-oriented environment like Modeler, you have a library of models that are packaged for ease-of-use. This helps to clarify your choices. Your basic choices relate to the following:

  • Which objects should you use from the library?
  • Which protocols should you enable?
  • How should you assign the attributes of objects?
  • How should you model traffic in the network? Should you use explicit application traffic, Transaction Analyzer packet trace-generated traffic, background traffic, or a combination?
  • What type of analysis best meets your needs? Should you do a discrete event simulation, a flow analysis, a NetDoctor validation, or a combination?

Because your modeling decisions as an Modeler user are guided by the model library, the majority of this section focuses on assisting you in understanding its models and how to work with them.