A Visualization of OCL Using Collaborations

Bottoni, Paolo; Koch, Manuel; Parisi-Presicce, Francesco; Taentzer, Gabriele

doi:10.1007/3-540-45441-1_20

Cited by 43 publications

(24 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Constraint diagrams [20,21] lack mechanisms to compose constraints modularly similarly to the VCL constraint composition mechanisms illustrated here. Visual OCL [24,22], like VCL, also provide logical operators and quantifiers, and a way of composing constraints, but does does not support set-based constraints; also Visual OCL has more visual concepts than VCL, which does not favour usability. Story Decision Diagrams [23] notation has modular operators and quantifiers.…”

Section: Related Workmentioning

confidence: 99%

Specifying Structural Properties and Their Constraints Formally, Visually and Modularly Using VCL

Amálio

Kelsen

2010

Enterprise, Business-Process and Information Systems Modeling

View full text Add to dashboard Cite

Abstract. The value of visual representations in software engineering is widely recognised. This paper addresses the problem of formality and rigour in visual-based descriptions of software systems. It proposes a new language, VCL, designed to be visual, formal and modular, targeting abstract specification at level of requirements, and that aims at expressing visually what is not visually expressible using mainstream visual languages, such as UML. This paper presents and illustrates VCL's approach to structural modelling based on the VCL notations of structural and constraint diagrams with a case study. VCL's contributions lie in its modularity mechanisms, and the support for two alternative styles of visual constraint modelling (one closer to set theory expressions and based on Euler diagrams, the other closer to predicate calculus and based on object graphs).

show abstract

Section: Related Workmentioning

confidence: 99%

Specifying Structural Properties and Their Constraints Formally, Visually and Modularly Using VCL

Amálio

Kelsen

2010

Enterprise, Business-Process and Information Systems Modeling

View full text Add to dashboard Cite

show abstract

“…These rules are akin to the differential meaning of VCL contract diagrams. Visual OCL [17], [18] also uses graph transformations to go from contracts to OCL. Like VCL, these approaches follow a translational approach to semantics.…”

Section: Related Workmentioning

confidence: 99%

Modular Design by Contract Visually and Formally Using VCL

Amálio¹,

Kelsen²

2010

2010 IEEE Symposium on Visual Languages and Human-Centric Computing

View full text Add to dashboard Cite

Visual representations are widely used to describe modern-day software systems, but, in most cases, they lack rigour. This paper addresses the problems of formality, rigour and complexity in visual descriptions of software systems. It proposes a new language, VCL, that is designed to be visual, formal and modular, and that targets abstract specification at the level of requirements. VCL aims at expressing visually structural and behavioural properties of software systems. This paper presents design of VCL, outlining syntax and semantics of VCL notations of structural, behavioural, constraint, and contract diagrams, together with VCL's approach to behavioural modelling based on design by contract. VCL's novelty lies in the fact that contracts are modular units.

show abstract

“…Special attention in association end selection must be paid to the association end's multiplicity specification 4 : Multiplicity of an association end may declare exact upper and/or lower limits; or it may designate the upper and/or lower bounds which the multiplicity of an association end must not exceed or underrun (respectively). Being able to declare exact limits and/or minimal and maximal bounds provides for further flexibility in query specification based on structural arrangements.…”

Section: Multiplicity Restrictionsmentioning

confidence: 99%

“…It is important to note that the OCL operation evaluates the senders' and receivers' base classifiers rather than their role specifications. This is accomplished deeming that selections should consider the full specification of classifiers rather than restricted 4 The same counts for the multiplicity specification of attributes (see sample classifier pattern in Table 1 for an example). 5 Technically, fix upper and lower limits are specified as stereotypes of multiplicity ranges.…”

Section: Message Selectionmentioning

confidence: 99%

“…Considering that most submissions to OMG's QVT RFP propose to use OCL as a query language, JPDDs also relate to existing approaches for the visualization of OCL expressions in general, such as Constraint Diagrams [11] or Visual OCL [4] [12]. Constraint Diagrams represent a graphical notation to specify invariants on objects and their associations (i.e., links) depending on the state they are in.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

A Graphical Notation to Specify Model Queries for MDA Transformations on UML Models

Stein

Hanenberg

Unland

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract.Specifying queries on models is a prerequisite to model transformations in the MDA because queries select the model elements that are the source of transformations. Current responses to OMG's MOF 2.0 QVT RFP mostly propose to use (and/or extend) OCL 2.0 as specification language for queries. In this paper, we demonstrate that using textual notations (like OCL) quickly leads to complex query statements even for simple queries. In order to overcome this handicap, we present a graphical notation based on the UML that facilitates comprehension of query statements as well as estimation of the (ultimately) selected model elements. We advocate that queries should be specified in terms of user model entities and user model properties (rather than meta model entities and meta model properties) for the sake of feasibility and comprehensibility to the user.

show abstract

A Visualization of OCL Using Collaborations

Cited by 43 publications

References 8 publications

Specifying Structural Properties and Their Constraints Formally, Visually and Modularly Using VCL

Specifying Structural Properties and Their Constraints Formally, Visually and Modularly Using VCL

Modular Design by Contract Visually and Formally Using VCL

A Graphical Notation to Specify Model Queries for MDA Transformations on UML Models

Contact Info

Product

Resources

About