A Minimal Set of Refactoring Rules for Object-Z

McComb, Tim; Smith, Graeme

doi:10.1007/978-3-540-68863-1_11

Cited by 11 publications

(4 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In particular, we will examine how local changes to individual classes in Object-Z [19] specifications affect global system properties. This may be aided by recent work of Mc-Comb and Smith [21] which provides a minimal and complete set of rules for refactoring Object-Z specifications. We will determine the way properties are distributed among components by the application of these rules, and hence how changes to component properties affect system properties.…”

Section: Resultsmentioning

confidence: 99%

Property transformation under specification change

Smith

2010

Front. Comput. Sci. China

Self Cite

View full text Add to dashboard Cite

Formal specifications of software systems need to evolve in many ways during system development. Not only are changes required to refine the specification toward an implementation, they are also required in response to changes in requirements, or to incorporate different aspects of the system, e.g., fault tolerance or timing, initially ignored in order to simplify reasoning. This paper presents an approach for evolving Z specifications by the step-wise application of a number of simple rules. These rules not only document the evolution of the specification, but also make precise how properties of the system evolve with the specification. Hence, reasoning about these properties performed on the original specification need not be repeated on the new specification.

show abstract

Section: Resultsmentioning

confidence: 99%

Property transformation under specification change

Smith

2010

Front. Comput. Sci. China

Self Cite

View full text Add to dashboard Cite

show abstract

“…Refactorings have been proposed for formal specification languages such as Alloy [14,13] Object-Z [38,29], OCL-annotated UML [27], Event-B [1] and ASM [37], implementing typical refactorings such as renaming and moving elements, or introducing inheritance. Variability-aware formal specification languages are scarce, and we are not aware of refactorings aimed at them.…”

Section: Related Workmentioning

confidence: 99%

Merging cloned Alloy models with colorful refactorings

Liu

Macedo

Cunha

2022

Science of Computer Programming

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

Merging Cloned Alloy Models with Colorful Refactorings

Liu

Macedo

Cunha

2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Likewise to code, clone-and-own is a common way to create variants of a model, to explore the impact of different features while exploring the design of a software system. Previously, we have introduced Colorful Alloy, an extension of the popular Alloy language and toolkit to support feature-oriented design, where model elements can be annotated with feature expressions and further highlighted with different colors to ease understanding. In this paper we propose a catalog of refactorings for Colorful Alloy models, and show how they can be used to iteratively merge cloned Alloy models into a single feature-annotated colorful model, where the commonalities and differences between the different clones are easily perceived, and more efficient aggregated analyses can be performed.

show abstract

A Minimal Set of Refactoring Rules for Object-Z

Cited by 11 publications

References 13 publications

Property transformation under specification change

Property transformation under specification change

Merging cloned Alloy models with colorful refactorings

Merging Cloned Alloy Models with Colorful Refactorings

Contact Info

Product

Resources

About