Transformations Have to be Developed ReST Assured

Siikarla, Mika; Laitkorpi, Markku; Selonen, Petri; Systä, Tarja

doi:10.1007/978-3-540-69927-9_1

Cited by 15 publications

(7 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The question here is how to transform these extensional specifications into intensional ones. In this context, we are working on the use of the so-called model transformation by example approach [39], so that intensional specifications can be built from extensional ones, either from scratch [40,41,13,22] or using an approach that allows a refinement of the intensional specifications when a change in the extensional set of correspondences happens [35].…”

Section: Discussionmentioning

confidence: 99%

Realizing Correspondences in Multi-viewpoint Specifications

Romero

Jaen

Vallecillo

2009

2009 IEEE International Enterprise Distributed Object Computing Conference

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Realizing Correspondences in Multi-viewpoint Specifications

Romero

Jaen

Vallecillo

2009

2009 IEEE International Enterprise Distributed Object Computing Conference

View full text Add to dashboard Cite

show abstract

“…Even though there are many languages to implement transformations, very few works propose higher-level notations for transformation design [14]. To our knowledge, no language has been proposed for specification of implementation properties, as we do in this paper.…”

Section: Related Workmentioning

confidence: 98%

A Visual Specification Language for Model-to-Model Transformations

Guerra

Lara²,

Kolovos

et al. 2010

2010 IEEE Symposium on Visual Languages and Human-Centric Computing

View full text Add to dashboard Cite

Abstract-Model Driven Engineering promotes models as the core assets of projects and hence model transformations become first-class citizens in this approach. Likewise, the development of large scale transformations necessitates a systematic engineering process and supporting modelling notations. However, although many languages have been proposed to implement transformations, few allow their specification at a higher level of abstraction.In this paper we present a visual, formal, declarative specification language to express model-to-model transformations and their correctness properties. The language supports the two main approaches to model-to-model transformationtrace-based and traceless -with a unified formal semantics. Moreover, we provide a compilation of specifications into OCL as this has many practical applications, e.g. it allows injecting assertions and correctness properties for automated testing of transformation implementations based on OMG standards.

show abstract

“…The authors present a modeling approach tightly integrated with UML that is based on a REST specific UML profile and is tailored to Java EE environments. A complementary work on model driven development for REST is presented in [22], proposing an iterative approach for defining and improving model transformations. In addition to model driven approaches for REST APIs there has been developed several description languages for REST APIs.…”

Section: Related Workmentioning

confidence: 99%

A Conversation Based Approach for Modeling REST APIs

Haupt

Leymann

Pautasso

2015

2015 12th Working IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

Abstract-Conversations are a well-known concept in service design to describe complex interactions between a client and one or multiple services. The REST architectural style constrains the characteristics of clients, servers and their interactions in REST architectures which consequently has an impact on conversations in such systems. The relation between conversations and REST architectures and how such RESTful conversations can be characterized has not been studied in detail yet. In this paper we discuss the characteristics of conversations in REST architectures and introduce an initial set of commonly used conversation types. Based on this, we propose to use conversations as a modeling tool for the design of REST APIs at a higher level of abstraction. We also introduce a corresponding interaction centric metamodel for REST APIs. The characterization of RESTful conversations enables a new interaction centric viewpoint on REST architectures which can be also applied for modeling REST APIs on an abstraction level that enables users to focus on the essential functionality of their REST API.

show abstract

Transformations Have to be Developed ReST Assured

Cited by 15 publications

References 4 publications

Realizing Correspondences in Multi-viewpoint Specifications

Realizing Correspondences in Multi-viewpoint Specifications

A Visual Specification Language for Model-to-Model Transformations

A Conversation Based Approach for Modeling REST APIs

Contact Info

Product

Resources

About