Modeling System Structure
Modeler uses two fundamental methods of describing a system:
- Objects – represent system structure by decomposing a system into smaller “pieces” and expressing the relationships between those pieces For more information, see Where System Structure Appears.
- Procedures – provide a way of expressing behavior that is dynamic and adaptive
Behavioral descriptions must account for a wide variety of conditions involving variable system state and events; furthermore, complex actions must be specified in response to these conditions. This modeling approach provides a natural way of integrating these two specifications into a unified system model, as will become clear in the remaining parts of this section.
Key Concept—Modeler uses two fundamental methods for describing a system: objects and procedures. Objects represent system structure, and procedures are used to express system behavior.
Where System Structure Appears
This section focuses on the description of system structure using objects. Objects provide a natural approach for constructing models of most systems, including communications networks. This is partially due to the fact that in the real world, systems actually include many physically distinct entities that we think of simply as objects.
Examples of physical objects in a communications network are listed in the following table.
Table 25: Some Physical Objects in a Communication Network
| Router, Gateway | Switch, Bridge, Hub |
| Workstation, PC, Terminal | Disk Drive |
| Link (cable) | Antenna |
| Telephone, PBX | Aircraft, Satellite |
Note that these are all objects that you have probably seen before and that you can describe physically. More than their physical characteristics, for modeling purposes, we are interested in describing how they work, and how they interact with other objects. Here again, there is a structural aspect and a behavioral aspect of system specification. The structural aspect of how the object works internally deals primarily with further decomposition of the object into more objects. In other words, the object is a system in its own right, and can be modeled as a collection of smaller objects that cooperate in some manner to achieve the desired functionality. There is also structure supporting the interaction of the object with other objects. This primarily involves a description of the physical interfaces provided by the object and the pathways that are in place to allow it to communicate with other objects. Pathways are often (but not necessarily) other objects (such as links) whose purpose is to allow interconnection.
Key Concept—Objects provide a natural way of describing the structure of communications networks. In addition to capturing the physical characteristics of system components, they can be used to represent their internal decomposition and interconnection.
In a theoretical sense, the use of objects is not limited to representation of a system’s physical entities. Abstract or logical entities can also qualify as objects. A few examples of non-physical objects are:
- Process
- Packet
- Job, Request, or Task
- Timer
- Probability Distribution
Modeler generally attempts to represent system components in the most intuitive way possible. Therefore, these non-physical objects do not have a visual representation. They are simply software constructs, but they are still considered objects because of the way in which they are treated, and the way in which they behave. Some of the important characteristics that make them objects are: they present a well defined interface with controlled access to internal state; they are mostly special cases of a “class” of entities that are not identical but have a similar “form”.
An interesting observation can be made from the examples in the above table: none of the abstract or logical objects could be said to actually represent system structure. They are all dynamic entities and most are created for a certain period, and then disposed of. While examples to the contrary could probably be found, it is generally the case that non-physical objects correspond mostly to the changing aspects of the system. Therefore, while they are objects in the larger sense, they are not relevant to this discussion of representing system structure. In the remainder of this section, the word “object” is used to refer to physical objects, such as those previously enumerated.
Key Concept—Abstract or logical objects, such as processes and timers, exist in a communications network. However, they are generally dynamic objects, and not elements of system structure. This section focuses on physical objects that represent system structure.
Objects and Models
The relationship between an object and a model is fundamental to all specification work performed in Modeler. When an object is created, a certain number of characteristics (sometimes all characteristics) are assumed to belong to it. The characteristics may relate to internal structure of the object, its capabilities and purpose, its presentation, and its interfaces. This information must come from some prior specification that is implicitly referenced when the object is created. This specification is referred to as a model.
The object is an instance of its model; each object can have only one model. Of course, the operation used to create the object (graphical) can be repeated, resulting in another object which is an instance of the same model. Therefore, there is a many-to-one relationship between objects and models. What is important is to realize that though the objects depend on the same model to receive certain characteristics, they exist independently of each other. In other words, changes made to one of the model instances do not affect the other. This corresponds well to the real world situation that objects represent. Consider the following example. A particular make and model of automobile can be considered a model. The model is essentially the “blueprints” for the car, together with any additional information that may describe it, such as list price, available colors, etc. Then the actual cars that consumers can purchase would be considered objects that are instances of that model. Each car exists independently of the other. For example, if one car breaks down, this implies nothing about the state of other cars of the same type.
Key Concept—Objects are instances of models. An object is a particular occurrence of a model. It exists independently from other objects and its characteristics conform to the model’s specifications. As an analogy, a particular car is an instance of the car model which is essentially the car’s design.
The collection of objects that depend on a particular model form a class. It is quite simply the class of objects of that type. The model represents the class; it is the class’ definition. When the definition of the class changes, all of the objects that belong to it are affected. For example, embedding additional specification for internal structure into the model will result in all objects receiving that internal structure. Similarly, if the interface specification of the model is modified, then all the dependent objects must change the way in which they interface with other objects. Such a change may potentially result in invalid connections or interactions, unless appropriate adjustments are made to the objects.
This mechanism provides a centralized method for applying changes to sets of objects. The power of this approach is magnified by the fact that the changes apply to all objects, including those that are not currently present within the Modeler editors. In fact, the changes even apply to future objects because they will adhere to the new model definition when they are created.
Key Concept—Models dictate object characteristics. Changing the definition of a model affects the characteristics of all of the objects that adhere to that model. This is a powerful mechanism for controlling large numbers of objects in a centralized manner.
A model includes information that is common to all of its instances. This includes specifications for the objects’ interfaces, behavior, and internal structure. The model’s interface dictates how objects interact with each other. This can include specifications related to physical interconnection. For example, a node model’s interface may include information about what types of links it can use to connect to other nodes. The model’s interface may also include the mechanics and the semantics of interaction with other objects. For complex objects, this may include timing of communication, mechanisms for transferring and sharing data, and the correct way to interpret that data.
In addition to an object’s interfaces, a model describes the behavior of the object. This means that the model defines the way in which an object will react to external stimulus, and the how and when it will spontaneously take action. A traffic source, for example, is an object that will spontaneously generate activity. For complex objects, behavior may be a function of many variables, including accumulated state information, external stimuli, time, and random variables.
Finally, a model also specifies the internal structure of an object. This has to do with the decomposition of the object into further components. These components may themselves be objects with their own models. Node models, for example, are specified in terms of objects called modules and connections, as described in later sections of this manual.
Key Concept—An object’s characteristics inherited from its model include: internal structure (what it contains), behavior (what it does spontaneously and how it reacts), and interfaces (how to interact with it).
While models specify a large part of object characteristics, further customization of the objects is usually still possible. If this were not supported, then all model instances would be identical. A model specifies which aspects of the instances is fixed, and which can be modified on a per-instance basis. The model can be thought of as being “parameterized”, meaning that it supports configuration of certain variables that the model designer chooses to “expose” to users of the model. This topic is treated in more detail later. For now, these parameters can simply be viewed as part of the model’s interface.
Key Concept—All objects that share a model are not necessarily identical. The model can allow for certain differences in each of its instances, as determined by the model designer.