By Topic

Specifying reactive systems by abstract events

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Astesiano, E. ; Dept. di Inf. e Sci. dell''Inf., Genoa Univ., Italy ; Reggio, G.

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.

Published in:

Software Specification and Design, 1993., Proceedings of the Seventh International Workshop on

Date of Conference:

6-7 Dec 1993