Specifying reactive systems by abstract events

Considers the problem of specifying reactive systems at different levels of abstraction and proposes a method for connecting the requirements to the design phase. As in a variety of other approaches, we assume that a process is modelled by a labelled transition system. The requirements phase is supposed to define a class of models, while at the design level (usually via a stepwise refinement), essentially one model is singled out. The connection between the two phases is provided by the notion of an abstract event, with its associated specification language. An abstract event is defined as a set of concrete instances, which are labelled transition sequences and can occur as partial paths over labelled transition trees. Abstract events, which may be non-instantaneous and overlapping, are a flexible tool for expressing abstract requirements and, because of their semantics in terms of labelled transition sequences, provide a rather transparent support to the refinement procedure.<
>