Architectural design in object-Z

McComb, Tim; Smith, Graeme

doi:10.1109/aswec.2004.1290460

Cited by 10 publications

(9 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although the complete specifications are not included here, the Object-Z examples of a few classes in this pattern are enough to show how a formal method can be applied to treat the architectural construct and compensate the insufficiency of objectoriented language such as UML. The Object-Z specification provides a better amount of generality and abstraction than UML and concrete examples, with the power of both formalization and object orientation for elementary element building blocks -it has the properties that an architectural specification should have [23]. However, the Object-Z specification is not intended to replace natural language specifications.…”

Section: Discussionmentioning

confidence: 99%

Synchronizable Objects in Distributed Multimedia Applications

Feijs

2010

Transactions on Edutainment IV

View full text Add to dashboard Cite

Abstract. In training and gaming systems, distributed multimedia are often used, in which the basic content elements must be conveyed or presented in a synchronized order at synchronized moments over multiple devices and in many cases over a network. These content elements are often presented or represented as "Synchronizable Objects" with which their control and management fall into a design pattern. This paper uses the pattern language to capture the common features of these "Synchronizable Objects", in combination of the formal Object-Z specification to treat the architectural construct. The proposed pattern can be applied for content elements with or without intrinsic timing in distributed multimedia applications. Examples are given to show how this pattern can be applied in distributed applications.

show abstract

Section: Discussionmentioning

confidence: 99%

Synchronizable Objects in Distributed Multimedia Applications

Feijs

2010

Transactions on Edutainment IV

View full text Add to dashboard Cite

show abstract

“…al. [Cor04,CCS02] and McComb [MS04,McC04]. Cornèlio defines refactorings and proves their correctness for a refinement-based object-oriented language (ROOL), McComb and Smith use Object-Z.…”

Section: Related Workmentioning

confidence: 99%

“…Additional constraints might constrain the application of the pattern. An overview of these kind of formal approaches to refactoring can be found in [MT04], in particular [MS04] and [MS06] follow this approach for Object-Z specifications, one of the formalisms we will be interested in here. While a lot of the approaches surveyed in [MT04] show behaviour-preservation only for specific properties (e.g.…”

Section: Introductionmentioning

confidence: 99%

“…While a lot of the approaches surveyed in [MT04] show behaviour-preservation only for specific properties (e.g. certain invariants of classes or relationships between objects), the basis for the correctness proof of [MS04] is the notion of data refinement [dE98,DB01] in Object-Z. Refinement exactly guarantees the intended substitutability requirement: for an external observer the classes before and after refactoring are not different, and this holds for any kind of (external) observation on the class.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Refactoring Object-Oriented Specifications with Data and Processes

Ruhroth

Wehrheim

2007

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Refactoring is a method for improving the structure of programs/specifications as to enhance readability, modularity and reusability. Refactorings are required to be behaviour-preserving in that -to an external observer -no difference between the program before and after refactoring is visible. In this paper, we develop refactorings for an object-oriented specification formalism combining a state-based language (Object-Z) with a process algebra (CSP). In contrast to OOprogramming languages, refactorings moving methods or attributes up and down the class hierarchy, in addition, need to change CSP processes. We formally prove behaviour preservation with respect to the failuresdivergences model of CSP.

show abstract

“…To bridge this gap between specification and implementation, specification refactoring rules have been proposed [7,8,9,11,2,5]. These allow the structure of a specification to be incrementally transformed to represent a given design.…”

Section: Introductionmentioning

confidence: 99%

A Minimal Set of Refactoring Rules for Object-Z

McComb

Smith

2008

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This paper presents a minimal and complete set of structural refactoring rules for the Object-Z specification language that allow for the derivation of arbitrary object-oriented architectures. The rules are equivalence preserving and work in concert with existing class refinement theory, so that any design derived using the rule set can be shown to be equivalent to, or a refinement of, the original specification.

show abstract

Architectural design in object-Z

Cited by 10 publications

References 16 publications

Synchronizable Objects in Distributed Multimedia Applications

Synchronizable Objects in Distributed Multimedia Applications

Refactoring Object-Oriented Specifications with Data and Processes

A Minimal Set of Refactoring Rules for Object-Z

Contact Info

Product

Resources

About