Using use cases in Executable Z

Grieskamp, Wolfgang; Lepper, Markus

doi:10.1109/icfem.2000.873811

Cited by 17 publications

(19 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Grieskamp and Lepper [7] used executable Z to describe use cases. The benefit is that this gives a complete formal specification which can even be run.…”

Section: Related Workmentioning

confidence: 99%

“…Use cases describe the system behavior in an informal way, usually using only text. In contrast to some research [7] which tries to add formal specifications directly to use cases, we will stick to text, because we believe that there needs to be an informal description of the system somewhere. Even for informal, textual use cases however, templates are used to structure the descriptions, e.g.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

From Informal to Formal Specifications in UML

Giese

Heldal

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. In this paper, we consider a way of bridging informal and formal specification. Most projects have a need for an informal description of the requirements of the system which all people involved can understand. At the same time, there is a need to make some of the requirements more formal. We present a way to relate informal requirements, in form of use cases, to more formal specifications, written in the Object Constraint Language (OCL). Our approach gives the customers of software systems a way of guiding the development of formal specifications. Conversely, the formal specification can improve the informal understanding of the system by exposing gaps and ambiguities in the informal specification.

show abstract

“…Grieskamp and Lepper [7] used executable Z to describe use cases. The benefit is that this gives a complete formal specification which can even be run.…”

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

From Informal to Formal Specifications in UML

Giese

Heldal

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Z is a "formal notation which aims to support, besides others, the specification of early requirements" [35]. In [35] Grieskamp et al detail their experiments with use cases described in an executable form of Z.…”

Section: Methods Of Quantifier Executionmentioning

confidence: 99%

“…For example, Aslantest [24], Jahob [64], and executable Z [35] all handle unbounded quantifiers in different ways.…”

Section: Methods Of Quantifier Executionmentioning

confidence: 99%

Incremental Validation of Formal Specifications

Corwin¹

View full text Add to dashboard Cite

Incremental Validation of Formal Specifications by Paul CorwinThis thesis presents a tool for the mechanical validation of formal software specifications. The tool is based on a novel approach to incremental validation. In this approach, small-scale aspects of a specification are validated, as part of the stepwise refinement of a formal model.The incremental validation technique can be considered a form of "lightweight" model checking. This is in contrast to a "heavyweight" approach, wherein an entire large-scale model is validated en masse.The validation tool is part of a formal modeling and specification language (FMSL), used in software engineering instruction. A lightweight, incremental approach to validation is beneficial in this context. Such an approach can be used to elucidate specification concepts in a step-by-step manner. A heavy-weight approach to model checking is more difficult to use in this way.The FMSL model checker has itself been validated by evaluating portions of a medium-scale specification example. The example has been used in software engineering courses for a number of years, but has heretofore been validated only by human inspection. Evidence for the utility of the validation tool is provided by its performance during the example validation. In particular, use of the tool led to the discovery of a specification flaw that had gone undiscovered by manual validation alone.iv

show abstract

“…In another strand of research, Grieskamp and Lepper combined use cases with Z [8]. Use cases benefit from Z for its added precision while a Z specification benefits from use cases for relating its operations in actual usage.…”

Section: Introductionmentioning

confidence: 99%

Precise Scenarios – A Customer-Friendly Foundation for Formal Specifications

Stone

Cooke

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. A formal specification is beyond the comprehension of the average software customer. As a result, the customer cannot provide useful feedback regarding its correctness and completeness. To address this problem, we suggest the formalism expert to work with the customer to create precise scenarios. A precise scenario describes an operation by its effects on the system state with only a few simple Z concepts. The customer would find a concrete precise scenario easier to understand than its corresponding abstract schema. The Z expert derives schemas based on the precise scenarios. Precise scenarios affords user involvement that improves the odds of a formal specification fully capturing the user requirements.

show abstract

Using use cases in Executable Z

Cited by 17 publications

References 5 publications

From Informal to Formal Specifications in UML

From Informal to Formal Specifications in UML

Incremental Validation of Formal Specifications

Precise Scenarios – A Customer-Friendly Foundation for Formal Specifications

Contact Info

Product

Resources

About