A type system for object models

Edwards, Jonathan; Jackson, Daniel; Torlak, Emina

doi:10.1145/1029894.1029921

Cited by 21 publications

(21 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [11], the authors present a system for checking the type compatibility of constraints on object models expressed in Alloy, a language similar in purpose to the combination of OCL and MOF. They propose an algorithm using bounding types and base types to determine whether an expression has meaning with respect to a given object model.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

On model typing

2007

View full text Add to dashboard Cite

Where object-oriented languages deal with objects as described by classes, model-driven development uses models, as graphs of interconnected objects, described by metamodels. A number of new languages have been and continue to be developed for this modelbased paradigm, both for model transformation and for general programming using models. Many of these use single-object approaches to typing, derived from solutions found in object-oriented systems, while others use metamodels as model types, but without a clear notion of polymorphism. Both of these approaches lead to brittle and overly restrictive reuse characteristics. In this paper we propose a simple extension to object-oriented typing to better cater for a model-oriented context, including a simple strategy for typing models as a collection of interconnected objects. We suggest extensions to existing type system formalisms to support these concepts and their manipulation. Using a simple example we show how this extended approach permits more flexible reuse, while preserving type safety.

show abstract

Section: Related Workmentioning

confidence: 99%

“…However, as discussed in [11] and mentioned in [19], the use of such type systems in a modeloriented context renders programs somewhat brittle with respect to changes in the metamodel, often failing in response to changes that ought not to affect their operation.…”

Section: Introductionmentioning

confidence: 99%

On model typing

2007

View full text Add to dashboard Cite

show abstract

“…In this sense, we are working along the lines of Edwards et al [13] on how to incorporate such kinds of constraints into our representation of models and metamodels.…”

Section: Discussionmentioning

confidence: 99%

Formal and Tool Support for Model Driven Engineering with Maude.

Romero¹,

Rivera²,

Durán³

et al. 2007

JOT

View full text Add to dashboard Cite

Models and metamodels play a cornerstone role in Model-Driven Software Development. Although several notations have been proposed to specify them, the kind of formal and tool support they provide is quite limited. In this paper we explore the use of Maude as a formal notation for describing models and metamodels. Maude is an executable rewriting logic language specially well suited for the specification of object-oriented open and distributed systems. We show how Maude offers a simple, natural, and accurate way of specifying models and metamodels, and offers good tool support for reasoning about them. In particular, we show how some basic operations on models, such as model subtyping, type inference, and metric evaluation, can be easily specified and implemented in Maude, and made available in development environments such as Eclipse.

show abstract

“…Since the authors proposed their transformation for UML class diagrams [26,8,17], and the Object Constraint Language (OCL) [21] presents a complex type system [7,31], these examples may also introduce a type error. Another work [3] does not consider invariants.…”

Section: Fig 2 Converting a Generalization Into A Relationmentioning

confidence: 99%

A Static Semantics for Alloy and its Impact in Refactorings

Gheyi

Massoni

Borba

2007

Electronic Notes in Theoretical Computer Science

View full text Add to dashboard Cite

Refactorings are usually proposed in an ad hoc way because it is difficult to prove that they are sound with respect to a formal semantics, not guaranteeing the absence of type errors or semantic changes. Consequently, developers using refactoring tools must rely on compilation and tests to ensure type-correctness and semantics preservation, respectively, which may not be satisfactory to critical software development. In this paper, we formalize a static semantics for Alloy, which is a formal object-oriented modeling language, and encode it in Prototype Verification System (PVS). The static semantics' formalization can be useful for specifying and proving that transformations in general (not only refactorings) do not introduce type errors, for instance, as we show here.

show abstract

A type system for object models

Cited by 21 publications

References 9 publications

On model typing

On model typing

Formal and Tool Support for Model Driven Engineering with Maude.

A Static Semantics for Alloy and its Impact in Refactorings

Contact Info

Product

Resources

About