Summary: Reactive systems are increasingly developed using high-level
modeling tools. Such modeling tools may facilitate formal reasoning
about concurrent programs, but provide little help when timing-related
problems arise and deadlines are missed when running a real system.
In these cases, the modeler has typically no information about timing
properties and costly parts of the model; there is little or no guidance
on how to improve the timing characteristics of the model. In this paperHere,
we propose a design methodology where interactive timing analysis is an
integral part of the modeling process. This methodology concerns how
to aggregate timing values in a user-friendly manner and how to define
timing analysis requests. We also introduce and formalize a new timing
analysis interface that is designed for communicating timing information
between a high-level modeling tool and a lower-level timing analysis tool.