No label defined (Q3976659)

[For the entire collection see Zbl 0733.00019.] Two representations of models can be distinguished. The analytic representation is the detailed, low-level description required as input to analysis modules; the modeler's representation is the model specification that the user supplies, it is typically in symbolic form and should be in terms of constructs that are natural to application. The translation between these description levels is a major problem. Clearly the fomr of the model specification language determines the ease of definining models, thereby influencing the overall cost of the modeling effort; requiring the user to directly input the transition rate matrix for a model is certainly possible but would severely hinder the application of the tool. A high-level model description language tailored to a particular domain provides the ability to define models that are easy to understand, less time-consuming for the modeler, and less error prone. However, this puts the burden on the modeling tool to provide a translation from the modeler's representation to the transition rate matrix. In the presented approach all system models are defined in terms of instaces of objects and interactions of objects. The characteristics of specific applications are reflected in the object types that are used in the model specification. By providing libraries of object definitions, the modeling tool can be easily extended to new application domains. With this approach one is able to produce tailored interfaces in a matter of hours for reliability modeling and queueing networks. An implementation in Prolog of a system based on this methodology is described and some example applications are given.