51 citations found. Retrieving documents...
I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 2nd edition, 1993.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:

First 50 documents  Next 50

An Executable Semantics for a Formalized Data Flow Diagram .. - Wahls, Baker, Leavens (1993)   (Correct)

....the bubble outputs to its outflows. These conditions are written as first order predicate calculus (FOPC) assertions over the values on the inflows and outflows of the bubble. Thus, RT SPECS has much in common with SPECS (a non graphical specification language developed at ISU) VDM [6] and Z [5] [18] 19] in that specification is done using FOPC pre and post conditions. RT SPECS thus has the formality of these specification techniques, and also the advantage of a graphical notation. 1.3 Goal of this paper The goal of this paper, then, is to provide a formal semantics for RT SPECS. ....

Hayes, I. Specification Case Studies. Prentice-Hall, International Series in Computer Science, 1987.


Preliminary Design of JML: A Behavioral Interface.. - Leavens, Baker, Ruby (1999)   (113 citations)  (Correct)

....than software that has yet to be implemented. ffl The notation used in JML should be readily understandable by Java programmers, including those with only standard mathematical training. A preliminary study by Finney [9] indicates that graphic mathematical notations, such as those found in Z [13, 45] may make such specifications hard to read, even for programmers trained in the notation. This accords with our experience in teaching formal specification notations to programmers. Hence, our strategy for meeting this goal has been to shun most special purpose mathematical notations in favor ....

....standard Java libraries as pure. A pure class must have a specification such that: ffl it only extends other pure classes, ffl all the methods in each interface it implements extends are pure, ffl all its methods and constructors must be specified to be pure in the sense described above, and 13 ffl all its data fields must be of some primitive value type or a pure type. Recursion is permitted, both in pure methods and in data members of pure classes. However, a pure method must be proved to terminate when its preconditions is met. When recursion is used in a specification, the proof ....

[Article contains additional citation context not shown here]

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, Inc., second edition, 1993.


Guidelines for the Manual Conversion of Object-Z to C++ - Johnston, Rose (1993)   (11 citations)  (Correct)

....APPENDIX C C SET HIERARCHY TO CODE C.1 Object Z Specification This is a specification of the generic mathematical classes of set, relation, partial function, one one function, relation on and directed acyclic graph. The operations are based primarily on the Z glossary of mathematical notation [7]. In this specification, it is assumed that all the specified operations are visible. Set Set[X] is specified first; it has operations IsEmpty , IsEqual , Size, IsElmt , IsSubset , IsSubsetProper and IsDisjoint to query the state, operations AddElmt , AddNewElmt , SubtractElmt and RemoveElmt to ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. PrenticeHall, 2nd edition, 1993.


Guidelines for the Manual Conversion of Object-Z to C++ - Johnston, Rose (1993)   (11 citations)  (Correct)

....mobile phone system (MPS) see Appendix E 1 Examples from these are used to illustrate the points raised. Other case studies have been undertaken to exercise the guidelines. These include ffl Logica s button study (Buttons) described in [9] ffl a portion of the Unix filing system described in [6] ffl a calculator described in [5] 2 Guidelines for Translating an Object Z class into C Object Z and C are both object oriented languages and as one would expect, there is a fairly straightforward mapping at the class level from Object Z to C . These guidelines form the basis of the class ....

....The Environment The declarations of the type Boolean and the global variable success can be written in a separate file for inclusion in all generated class file headers. 18 APPENDIX A A Object Z Overview A. 1 Introduction Object Z[2, 3, 4] is an extension of the formal specification language Z[6, 10, 11] to accommodate object orientation[8, 1] The main reason for this extension is to improve the clarity of large specifications through enhanced structuring. A Z specification typically defines a number of state and operation schemas. A state schema groups together variables and defines the ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. PrenticeHall, 1987.


A Semantic Foundation for Object Identity in Formal.. - Griffiths, Rose (1995)   (10 citations)  (Correct)

....of an implicit reference model for identity as suggested by Duke and Rose [DR93] Section 3 describes the necessary semantic domains. That description involves the formal development of a semantic universe for Object Z similar in style to the semantic universe for the specification language Z [Hay87, Spi88, BKN 92] Previous semantic descriptions differ from our work in that they: 1. are not formal; 2. do not require that identity be a part of the semantics of the language [DD90] or, 3. are not set theoretic. We acknowledge the work of Lano [Lan94] which considers the role of ....

I Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, 1987. 29


Structuring Z Specifications: Some Choices - MacDonald, Carrington (1995)   (Correct)

....which can be seen in Hayes[4, Chapter 2] The third style parameterises similar components to avoid duplication. Hayes[4, Chapter 5] provides an example. The final two techniques use extensions to Z to impose structure: the first uses a library module extension of Z developed by Wildman and Hayes[4, 5] and the second uses Object Z[2, 11] Combining object orientation with Z has been investigated by many people, including Schuman and Pitt[12] and Hall[3] Two collections[15, 7] capture recent work on extending Z with object oriented features. This section first discusses the production cell case ....

Ian Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, London, UK, 2nd edition, 1993.


Providing a Z Interface to the Sum Tools - Johnston (1998)   (Correct)

....of only those constructs which can be translated to Sum ffl Testing a Z specification which included samples of Z type violations. ffl Testing of Z specifications taken from the course notes of Workshop on Using Z (a workshop run by the SVRC) some case studies from a book of case studies, [5], and some other specifications. The test cases: 1. A Specification of all Z Constructs A comprehensive test suite was built from the Z concrete syntax, according to [6] which included all the allowable Z constructs. This suite is incomplete in the sense that only a sample of the In Fun, ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 2nd edition, 1993.


The Object-Z Specification Language: Version 1 - Duke, King, al. (1991)   (Correct)

.... : 60 Additional Class Operators : 61 Temporal operators : 61 iv 1 Introduction Object Z is an extension of the formal specification language Z[13, 22, 25, 19, 8] to accommodate object orientation[16, 3] The main reason for this extension is to improve the clarity of large specifications through enhanced structuring. In this report we discuss the features of Object Z (concentrating on those aspects which extend Z) and illustrate its use through four case ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 1987. 55


JML: A Notation for Detailed Design - Leavens, Baker, Ruby (1999)   (56 citations)  (Correct)

....of such a specification language has to learn a notation for assertions that is different than their programming language s notation for expressions. A preliminary study by Finney [Finney96] indicates that a large number of special purpose, graphic mathematical notations, such as those found in Z [Hayes93] [Spivey92] may make such specifications hard to read, even for programmers trained in the notation. In JML we use a compromise approach, hiding these details behind Java classes. These classes are pure, in the sense that they reflect the underlying mathematics, and hence do not use side effects ....

Hayes, I., editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, Inc., second edition, 1993.


Requirements Visualization - Teyseyre, Orosco, Campo   (Correct)

....Representation We have decided to start the validation process from a formal speci cation. Formal speci cation languages have a formal syntax and semantics which makes it possible to unambiguously denote the meaning of the requirements. The best know formal speci cations languages are Z [Hayes, 1987] and VDM [Jones, 1990] among others. In our case, we have chosen Z as our speci cation language. However, in order to present an animation a Z speci cation is not enough, it must be translated to an executable version. A Z speci cation, can be translated and executed relatively easily to ....

Hayes, I., editor (1987). Specication Case Studies. International Series in Computer Science. Prentice-Hall, Inc.


JML: a Java Modeling Language - Leavens, Baker, Ruby (1998)   (8 citations)  (Correct)

....than software that has yet to be implemented. ffl The notation used in JML should be readily understandable by Java programmers, including those with only standard mathematical training. A preliminary study by Finney [8] indicates that graphical mathematical notations, such as those found in Z [11, 37] may make such specifications hard to read, even for programmers trained in the notation. This accords with our experience in teaching formal specification notations to programmers. Hence, our strategy for meeting this goal has been to shun most special purpose mathematical notations in favor of ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, Inc., second edition, 1993.


Preliminary Design of JML: A Behavioral Interface.. - Leavens, Baker, Ruby (1999)   (113 citations)  (Correct)

....software that has yet to be implemented. The notation used in JML should be readily understandable by Java programmers, including those with only standard mathematical training. A preliminary study by Finney [Finney96] indicates that graphic mathematical notations, such as those found in Z [Hayes93,Spivey92] may make such specifications hard to read, even for programmers trained in the notation. This accords with our experience in teaching formal specification notations to programmers. Hence, our strategy for meeting this goal has been to shun most special purpose mathematical notations in favor of ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, Inc., second edition, 1993.


Protective Interface Specifications - Leavens, Wing (1998)   (3 citations)  (Correct)

....value; hence it will not be possible to prove anything about such a term. This kind of logic is used in the Larch Shared Language, LSL [GHG 93, Chapter 4] GHM90] which is the mathematical component of the Larch family BISLs [GHG 93] in the BISLs of the RESOLVE family [OSWZ94] and in Z [Hay93, Spi92] according to its draft standard [WJ96] The subtle problems that underspecification may cause for the unwary in LSL (and similar logics) are discussed in Appendix A; indeed Jones s paper pointing out these problems [Jon95] motivated the present work. It is not the purpose of this paper ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, Inc., second edition, 1993.


Prospects for A Viable Software Industry - Enterprise Models, .. - Bjørner (1993)   (Correct)

.... is a comprehensive method (language, proof system, design techniques) for implementing non parallel software. 33, 1, 2] cover VDM, 18. Z for Zermelo Frankel Set Theory. is a comprehensive method (language, proof system, design techniques) for implementing non parallel software. [29, 55, 51, 52, 54, 12, 46, 36] cover Z. Most, if not all of the above have tool sets; some, notably RAISE, but also, to a large extent Estelle, Larch, Lotos, VDM and Z, are industrial strength. It is sobering to observe, that as HOL is being fairly well established in the hardware community of the electronic industry for ....

Ian J. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire HP2 4RG, UK, 1987.


Some Modifications to the Dexter Model for the Formal.. - Lamberti, Maioli, Vitali   (Correct)

....such as authoring and versioning. Besides the modification to the Dexter, they depend strictly on some specific procedures of our project, therefore we defer their formal specification to another paper. 2 The Dexter model 2. 1 The Z notation Z notation is described in [Spi89] examples are in [Hay87] or [Nic91] Z notation models the data of any system through the use of mathematical data types. The data types are not oriented towards computer representation, but they satisfy a rich collection of mathematical laws which make it possible to reason effectively about the way a specified system ....

Hayes, I. (ed.): Specification case studies. Prentice Hall, International Series in Computer Science, 1987.


LSL traits for using Z with Larch - Hua Zhong   (Correct)

....defined all of the Z mathematical toolkit using LSL traits. These traits appear in Appendix A. Thus users can use the Z mathematical toolkit for writing Larch C specifications. A summary of these traits is given in Tables 2.1, 2.2, 2.3, 2.5, 2.4, 2.6, and 2.7. Table 2. 1: Sets Trait Name Page in [4] Operations Symbols in Z ZPowerSet 89,90 mem 2 nem 62 emptyset,varemptyset fag , fa; bg , fa; b; cg ZSet 90 subs pset P psetone P 1 SetUnionIntersectDiff 91 int uni [ setminus n GeneUniInt 92 duni [ dint Table 2.2: Relations Trait Name Page in [4] ....

....[4] Operations Symbols in Z ZPowerSet 89,90 mem 2 nem 62 emptyset,varemptyset fag , fa; bg , fa; b; cg ZSet 90 subs pset P psetone P 1 SetUnionIntersectDiff 91 int uni [ setminus n GeneUniInt 92 duni [ dint Table 2. 2: Relations Trait Name Page in [4] Operations Symbols in Z Rel 95 rel map 7 DomRan 96 dom dom ran ran Id 97 id id Cmp 97 fcmp o 9 cmp ffi DresRres 98 dres C rres B DsubRsub 99 dsub Gamma C rsub Gamma B RelInv 100 inv R RelImg 101 img (jj) RelOvr 102 fovr Phi TclRtcl 103 tcl rtcl Table ....

[Article contains additional citation context not shown here]

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, 1987.


Object Orientation in Z - Rose (1992)   (2 citations)  (Correct)

....of Computer Science University of Queensland Queensland 4072, Australia Object Orientation in Z S. Stepney and R. Barden and D. Cooper 1992, sv, Workshops in Computing pp 59 77 1.1 Object Z Overview 1.1. 1 Introduction Object Z[2, 3, 4] is an extension of the formal specification language Z[5, 7, 8] to accommodate object orientation[6, 1] The main reason for this extension is to improve the clarity of large specifications through enhanced structuring. A Z specification typically defines a number of state and operation schemas. A state schema groups together variables and defines the ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 1987.


Composing Grammar Transformations to Construct a.. - Wildman, Hayes (1995)   (1 citation)  Self-citation (Hayes)   (Correct)

....The full parser can then be specified by composing the separate transformations to give a grammar incorporating all the desired features. 1 Introduction In working towards a suitable framework for writing large specifications we have developed a library construct [2] that allows a Z [8, 3] specification to be presented in a structured form. In this paper we examine the application of libraries to the specification of an extended parser for a structured editor. The editor A generic language based editor [1] has been developed to provide support for software development. Two major ....

I.J. Hayes (editor). Specification Case Studies. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 2nd edition, 1993.


Specifying Parallel and Distributed Systems in Object-Z.. - Dong, Zucconi, Duke (1997)   (2 citations)  Self-citation (Case)   (Correct)

....in software system specification in the last few years. As a formal specification language can provide a precise system model which is implementation language independent, a number of standards bodies are recommending the use of formal notations for specifying software systems. For example, Z[23, 14] is recommended to define the Open Distributed Systems ODP system[16] Object Z[12, 19, 13] is recommended in standards work on presentation environments for multi media objects (the PREMO project) 18] Object Z has also been used to define the information model of ODP trader[8] and ODP type ....

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. PrenticeHall, 2nd edition, 1993.


Knowledge, State, Event and Time in System Modeling -.. - Dong, Duke, Sun (2006)   (Correct)

No context found.

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 2nd edition, 1993.


A Formal Specification Of Signalling System No.7 Telephone User Part - Smith (1989)   (Correct)

No context found.

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, 1987.


th Australian Computer - Science Conference Jan   (Correct)

No context found.

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 1987.


Formalising Behavioural Compatibility for Reactive.. - Duke, King, Smith (1991)   (1 citation)  (Correct)

No context found.

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice-Hall, 1987.


Temporal Logic and Z Specifications - Duke, Smith (1989)   (19 citations)  (Correct)

No context found.

I. Hayes, editor. Specification Case Studies. International Series in Computer Science. Prentice Hall, 1987.


An Object-Oriented Approach to the Formal Specification of ODP.. - Dong, Duke (1993)   (2 citations)  (Correct)

No context found.

I. Hayes, editor. Speci#cation Case Studies.International Series in Computer Science. Prentice-Hall, 1987.

First 50 documents  Next 50

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