Information Models

OPNET Development Kit applications are object-oriented. The information that is manipulated within the workflows consists, at least partially, of objects that represent various aspects of the network, such as network infrastructure or network traffic. In general, network objects can correspond directly to real-world objects, such as subnets, nodes, and links. They can also be more abstract entities that serve to aggregate information, such as a schedule of failures in the network. Regardless of their purpose, the family of objects desired for an OPNET Development Kit application can be completely defined by the application developer. This is done using the OPNET Development Kit application, which provides the same facilities for defining new types of objects as NetPlanner.

An object in an OPNET Development Kit application is defined according to a model. That model determines the interface that the object presents in terms of its appearance, the information it contains, and how it behaves in the workspace. The model is a class construct; each object is an instance of such a class. Except for an advanced concept called extended attributes, an object receives all of its properties from its model.

Each object contains a group of attributes. Attributes store the data related to this object and can be of various types, including integer, double (real value), string, and compound. A compound attribute contains a table of objects, which in turn can contain any combination of attributes. This attribute hierarchy is unlimited and provides a powerful way of representing the types of hierarchical constructs that appear everywhere in networks.

For OPNET Development Kit application developers, defining these information models is a rapid, GUI-driven process. Objects and their attributes are created and their properties are defined within the GUI. Furthermore, code "entry points" or "handlers" may be associated with various events that can occur for these objects and attributes. For example, customized code can be invoked every time an object of a certain type is right-clicked; or customized code can be invoked whenever a specific attribute is edited to present a list of dynamically-computed values based on the state of other parts of the network.

One advantage of the OPNET Development Kit approach to developing applications for information modeling is that a GUI for editing and presenting the objects and their attributes is automatically provided, based on the object definitions the application developer provides. No additional programming is required to edit and work with these objects in the workspace.