Why an Object Oriented Z?

Stepney, Susan; Barden, Rosalind; Cooper, David

doi:10.1007/978-1-4471-3552-4_1

Cited by 4 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For more than a decade, there has been interest in structuring Z specifications in an object-oriented (OO) style [1]. Researchers quickly realised that Z does not directly support object-orientation; fundamental OO concepts such as object and class are not Z language primitives.…”

Section: Introductionmentioning

confidence: 99%

An Object-Oriented Structuring for Z Based on Views

Amálio

Polack

Stepney

2005

ZB 2005: Formal Specification and Development in Z and B

Self Cite

View full text Add to dashboard Cite

Abstract. There is significant interest in the use of Z in conjunction with object-orientation. Here we present a new approach to structuring Z specifications in an object-oriented (OO) style. Our structuring is based on views, it uses the schema calculus, and it does not extend Z. The resulting OO Z specifications are comprehensible, modular, and conceptually clear. The modularity of the new approach supports a templateinstantiation approach to expressing OO models in Z; practical formal verification and validation of the model can be undertaken using metaproof, meta-lemmas, and formal snapshots.

show abstract

Section: Introductionmentioning

confidence: 99%

An Object-Oriented Structuring for Z Based on Views

Amálio

Polack

Stepney

2005

ZB 2005: Formal Specification and Development in Z and B

Self Cite

View full text Add to dashboard Cite

show abstract

“…These constructs included classes, objects, inheritance and polymorphism. A number of new formal languages were developed, notable among which are those which extend VDM or Z [21,14]. The goal was to make formal methods more applicable to larger-scale systems and industrial problems [6,15].…”

Section: Introductionmentioning

confidence: 99%

Introducing Reference Semantics via Refinement

Smith

2002

Formal Methods and Software Engineering

View full text Add to dashboard Cite

Abstract. Two types of semantics have been given to object-oriented formal specification languages. Value semantics denote a class by a set of values representing its objects. Reference semantics denote a class by a set of references, or pointers, to values representing its objects. While adopting the former facilitates formal reasoning, adopting the latter facilitates transformation to object-oriented code. In this paper, we propose a combined approach using value semantics for abstract specification and reasoning, and then refining to a reference semantics before transforming specification to code.

show abstract

“…On the other hand, as a result of the effort to put VDM and Z into practice, several authors developed combinations with semiformal specification techniques like structured analysis [You89] or object-oriented analysis [CoY91]. Approaches like [ELP93], [LPT93b] for VDM, [Ran90], [SBC92] for Z (or [FrD89] for algebraic techniques) are therefore in this respect close in spirit to KARL.…”

Section: Comparison With Related Languagesmentioning

confidence: 99%

The Knowledge Acquisition and Representation Language, KARL

Fensel¹,

Angele²,

Studer³

1995

View full text Add to dashboard Cite

The Knowledge Acquisition and Representation Language (KARL) combines a description of a knowledge-based system at the conceptual level (a so-called model of expertise) with a description at a formal and executable level. Thus, KARL allows the precise and unique specification of the functionality of a knowledge-based system independent of any implementational details. A KARL model of expertise contains the description of domain knowledge, inference knowledge, and procedural control knowledge. For capturing these different types of knowledge KARL provides corresponding modeling primitives that are based on Frame-logic and Dynamic Logic. A declarative semantics for a complete KARL model of expertise is given by a novel combination of these two types of logic. In addition, an operational definition of this semantics, which relies on a fixpoint approach, is given. This operational semantics defines the basis for the implementation of the KARL interpreter which includes appropriate algorithms for efficiently evaluating KARL specifications. This enables the evaluation of KARL specifications by means of testing.

show abstract

Why an Object Oriented Z?

Cited by 4 publications

References 0 publications

An Object-Oriented Structuring for Z Based on Views

An Object-Oriented Structuring for Z Based on Views

Introducing Reference Semantics via Refinement

The Knowledge Acquisition and Representation Language, KARL

Contact Info

Product

Resources

About