David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4), April 1990.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....can be used in combination with existing, established commercial techniques and tools. The choice of the commercial tools was determined by the industrial partners, the formal concepts to use by the academics. For the description of the reactive behavior, Statecharts (i.e. the Statemate tool [17]) were chosen, and combined with the Z specification formalism [31, 32] for the description of data and temporal logic for the specification of safety critical behavioral properties [27, 7] In this paper, we report in retrospection about the notation and tool integration framework developed in ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16 No. 4, April 1990.

.... [51, 46, 15] is gaining considerable momentum since it combines earlier methods from Booch [14, 13] and Rumbaugh [66] Visual formalisms for object oriented software began with the Software Engineering research and is being made manifest today by 2D graphical methods for FSMs such as StateCharts [35]. The software engineering community realizes the benefits of modeling, but more progress is needed before we are able to launch students into an environment where they learn how to program by designing software models from the very beginning, without first necessarily resorting to text based ....

David Harel. STATEMATE: A Working Environment for the Development of Complex Reactive Systems. IEEE Transactions on Software Engineering, 16(3):403 -- 414, April 1990.

....] CONTAMINANTSITE CONTAMINANTSITE ReminiscenceEnd Reminiscence Contagion Cure reminiscence infected : PAnimal reminiscence : N cureReminiscence #reminiscence reminiscence # # reminiscence 3. 2 Specification analysis The analysis is performed by using STATEMATE [12]; an environment which allows the prototyping and the simulation of the statechart specifications. The specification analysis is based upon execution of the statecharts and can be done using two techniques. The first technique is simulation and the second is animation. In our case simulation would ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark B. Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--414, April 1990.

....means to interact with the running simulation. 2. 3 Languages for Animation and Simulation Specialized languages provide abstractions to ease programming of complicated systems whether they are reactive physical systems, rigid body dynamics systems, or autonomous agent behavior architectures [33, 32, 17, 31]. Perlin introduced the Improv scripting language to empower computer animators, allowing them to create behavior based actors controlled by scripts. Improv is an actionbased scripting language in which well defined actions can be created and later invoked. Actions are routines that control an ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4), April 1990.

....or a database. Continuous process specifications describe systems that perform a stimulusresponse mechanism. The response of these systems to any given stimulus depends on the history of previous stimuli submitted to the system; examples of continuous process systems (also called reactive systems [8, 18, 15, 17]) include an operating system or a process control system. Furthermore, each one of these specification type can be divided into two classes: operational specifications which describe a system s behavior by building an abstract mathematical model of the state of the system and the operations that ....

....Like most graphical specification techniques, this is also more readable than many formal mathematical based specification techniques. Figure 13 provides the Petri Net specification for the Continuous Process specification of Table 2. Statecharts. This notation was developed by Harel [7, 8] to describe dynamic behavioral, usually referred as control aspects, of reactive systems. Statecharts are basicly an extended finite state machine (FSM) The first extension of Statecharts to FSMs, allows a transition (i.e. the edges in a FSM) to be a function of a stimulus and the truth value ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--414, May 1990.

....a b indicates event classification: an a event causing the transition is also a b event. The class of b events is defined as the set of all events causing transitions labeled . b. Using this mechanism, Figure 4 defines event classes such as normal open and close. We take Statecharts [Harel 87, Harel et al. 90] to be an elaborate variation on the finite state machine. We have used some of the standard Statechart features, ignored others, and added some of our own. Statecharts have nested states, which translate into logic in the obvious way. Our Statechart (Figure 5) is nonstandard in having no named ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon ShtullTrauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering XVI(4):403-414, April 1990.

....separate application, we are also omitting this reasoning. 7. Related work This work is related to research in a number of different areas. Most obviously, it is related to other linguistic 42 frameworks for multiparadigm specification such as the LOTOS Act One combination [IOS89] and Statemate [Harel et al. 90] Both of these efforts provide fixed compositions of fixed sets of languages. This means that their range of expressiveness is somewhat narrower than we are able to use. For instance, Statemate incorporates no language with the expressive power of Z, and neither effort makes grammars available. ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon ShtullTrauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering XVI(4):403-414, April 1990.

....is specified in Z. Conditions over the (private and public) data space of a process can be expressed using GUARD schemas. The behaviour of a process, i.e. the actions it performs during its lifetime, are subject to the statechart diagram ( Har87] in the dynamic view. We use the STATEMATE tool ([HLN90]) to support the employed graphical languages. Thus, for statecharts, the STATEMATE syntax and semantics are adopted ( HP96] However, we extend the notation by making use of the Z notation that is available in our framework (that is, we exchanged the STATEMATE expression language by Z) We ....

David Harel et al. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16 No. 4, April 1990.

....1 SOLVE also uses graphical presentation and manipulation to convey the meaning of a specification. However, unlike QUICK, SOLVE s primary concern is to generate formal specifications. Perhaps the best known work on formal modelling of reactive systems is that embodied in the STATEMATE tool [5]. The visual formalism of statecharts allows compact, hierarchical descriptions based on a finite state machine model. The graphical model itself can be directly executed. Animation and formal analysis are possible with SOLVE, but less directly than in the case of statecharts. SOLVE deliberately ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--414, April 1990.

....in which formal methods can be used in combination with existing, established commercial techniques and tools. The choice of the notations to be used was mainly determined by the needs of the industrial partners. For the description of the reactive behavior, Statecharts (i.e. the Statemate tool [13]) were chosen, and combined with the Z specification formalism [26, 27] for the description of data and temporal logic for the specification of safety critical behavioral properties [23, 6] In this paper, we report on the notation and tool integration framework developed in Espress. We present ....

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16 No. 4, April 1990.

....system for CHSMs is a hybrid system in the tradition of lex [5] and yacc [6] where an existing (host) programming language was augmented with additional constructs. The host language chosen for CHSMs was C [7] A different approach for implementing statecharts was taken by the STATEMATE system [8]. A CHSM source description has three parts as shown in figure 1.3: declarations, a description, and a user code section; these are placed into a text file and are separated by the token (mirroring yacc grammar specifications) declarations description user code Figure 1.3: CHSM ....

David Harel, et al. "STATEMATE: A Working Environment for the Development of Complex Reactive Systems." IEEE Transactions on Software Engineering, vol. 16, no. 4, April 1990. pp. 403--414.

....here, however, they are separated by the introduction of CHSMs to clearly distinguish them from FSMs since, as shown in 1.1 and 1.2, statecharts can be implemented using ordinary FSMs. 5 A completely opposite approach has been taken by the i Logix corporation with their STATEMATE product [6] [7]. It is a complete statechart development environment with its own programming language, editor, compiler, and debugger. This goes against all of the good reasons just mentioned. Not only that, but, presumably to recoup their development, maintenance, and documentation costs of such a large ....

....include a default interactor, that is, a simple, command line interface allowing the user to interact with a compiled CHSM. It would not only allow a user to get events into the system, but could also facilitate debugging by allowing CHSMs to be traced, singledstepped, and have breakpoints planted [7]. If the user wishes something more exotic, say a mousebased, graphical user interface where the mouse can be clicked on an on screen button to trigger an event and receive visual feedback (such an the icon of a light bulb illuminating when the start button is clicked on a simulated microwave ....

[Article contains additional citation context not shown here]

David Harel, et al. "STATEMATE: A Working Environment for the Development of Complex Reactive Systems." IEEE Transactions on Software Engineering, vol. 16 no. 4, April 1990. pp. 403--414.

....The strategy for developing this argument is called the assurance strategy and is the focus of this document. Our approach integrates security and system engineering to permit the explicit tradeoff of security requirements with other critical system requirements. We use the languages of Statemate [18, 19, 20, 21], based on the formal theory of statecharts, as a rigorous foundation for illustrating the operational requirements and design of JIFI graphically. We use a variant of the Goal Structured Notation (GSN) 44, 38, 31] and the Assumptions Assertions Framework [37] to state requirements in terms of ....

....of information security and information system architectures. A high level understanding of the conceptual and physical models presented requires some understanding of graphical (CASE or CAD) design languages; a more detailed understanding requires familiarity with the languages of Statemate [18, 19, 20, 21]. Readers will also find useful a basic understanding of the Goal Structured Notation [31, 38] and the Assumptions Assertions Framework [37] which form the basis for our method of requirements specification and risk analysis. 3 Chapter 2 Background The end of the cold war has shifted the ....

[Article contains additional citation context not shown here]

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--414, April 1990.

....of the behaviour of virtual environments distinguish them from other interactive systems. We believe that virtual environments share common features with safety critical dynamic interactive systems such as aircraft flightdecks. One tool that has found practical use in this context is Statemate [7] (based around the Statechart formalism [6] The starting point for building a prototype using Statemate is a Statechart specification. This specification defines a behavioural ordering (what the user can do and in what sequence) and the response of the system to the user interaction. The ....

David Harel, Hagi Lachover, Amnon Naaad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--413, July 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4), April 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon ShtullTrauring, and Mark Trakhtenbrot. "STATEMATE: A Working Environment for the Development of Complex Reactive Systems." In Transactions on Software Engineering, vol. 16, no. 4, pp. 403-414, April 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull- Trauring, and Mark Trakhtenbrot. "STATEMATE: A Working Environment for the Development of Complex Reactive Systems." In Transactions on Software Engineering, vol. 16, no. 4, pp. 403-414, April 1990.

No context found.

David Harel, Hagi Lachover, Ammon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A Working Environment for the Development of Complex Reactive Systems. IEEE Transactions on Software Engineering, 16(3):403--414, 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16:403--414, 1990.

No context found.

David Harel, H. Lachover, et al. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--414, April 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16 No. 4, April 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16 No. 4, April 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16 No. 4, April 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad, Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A Working Environment for the Development of Complex Reactive Systems. IEEE Transactions on Software Engineering, 16(4):404--414, 1990.

No context found.

David Harel, Hagi Lachover, Amnon Naamad,Amir Pnueli, Michal Politi, Rivi Sherman, Aharon Shtull-Trauring, and Mark Trakhtenbrot. STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403--414, April 1990.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC