OCL: Syntax, Semantics, and Tools

Richters, Mark; Gogolla, Martin

doi:10.1007/3-540-45669-4_4

Cited by 71 publications

(59 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In section 3 we propose a different approach to building operation contracts and we claim the need for non-query operation effects to be allowed in pre and post-conditions. In section 4 we propose a new kind of OCL pre and postconditions and define its semantics using the approach of [14,16]. Finally, in section 5 we present the conclusions.…”

Section: Outline Of the Papermentioning

confidence: 99%

“…In this section we propose an extension of OCL pre and post-conditions and present its semantics by extending the OCL semantics presented in [14,16].…”

Section: Extending Oclmentioning

confidence: 99%

“…In [14,16], all common OCL expressions could be used in pre-conditions. No extension was given for this type of constraints.…”

Section: Extending Oclmentioning

confidence: 99%

“…where CLASS, ATT c , OP c , ASSOC, associates, roles, multiplicities, and < are as defined in [14,16]; ASSERT OPc is an OP c -indexed set of assertion pairs (that is, a finite set of name pairs). ♦…”

Section: Definition 1 (Syntax Of Object Models)mentioning

confidence: 99%

“…, and Ι(Ω Μ ), are as defined in [14,16], and Ι(Α Μ ) assigns each assertion pair a∈Α Μ a total function Ι(a): → Pre-Expr Boolean × Post-Expr Boolean . The sets Pre-Expr Boolean and Post-Expr Boolean are the OCL pre-condition boolean expression set and the OCL post-condition boolean expression set, respectively (as defined in definitions 3 and 5 below).…”

Section: Definition 2 (Data Signature)mentioning

confidence: 99%

See 4 more Smart Citations

An OCL Extension for Low-Coupling Preserving Contracts

Nunes¹

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Design by contract, as introduced by B.Meyer, is of increasing importance to the OO community in the specification, reuse, and monitoring of classes. We strongly feel that class libraries of all programming languages should be equipped with contracts, insofar as these constitute a powerful and simple interface definition. Very powerful and expressive contracts can be written using the OCL language, although for operations with many effects on the system state, these contracts can become unmanageable and incomprehensible. In order to maintain contracts at a manageable level of complexity, we claim that the OCL powerful mechanism of navigation through associations should be used moderately when building contracts, and that the effects of non-query operations should be allowed to be referred to within pre-and post-conditions. To achieve that purpose, we propose an extension to OCL and present a formal semantics for it.

show abstract

Section: Outline Of the Papermentioning

confidence: 99%

“…In this section we propose an extension of OCL pre and post-conditions and present its semantics by extending the OCL semantics presented in [14,16].…”

Section: Extending Oclmentioning

confidence: 99%

“…In [14,16], all common OCL expressions could be used in pre-conditions. No extension was given for this type of constraints.…”

Section: Extending Oclmentioning

confidence: 99%

Section: Definition 1 (Syntax Of Object Models)mentioning

confidence: 99%

Section: Definition 2 (Data Signature)mentioning

confidence: 99%

See 3 more Smart Citations

An OCL Extension for Low-Coupling Preserving Contracts

Nunes¹

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

The analysis of architectural languages for the needs of practitioners

Özkaya

2018

Softw Pract Exp

View full text Add to dashboard Cite

Summary Architectural languages (ALs) have attracted much attention as the modeling notations for specifying and reasoning about important design decisions. In this study, 124 different existing ALs have been analyzed for a set of requirements that are crucial for practitioners. These requirements are concerned with language definition, language features, and tool support. Some of the important findings obtained from the analysis are as follows: (1) performance is the top popular nonfunctional requirement supported by ALs; (2) no ALs offer both textual and visual notation sets, one of which could be used independently; (3) process algebras are the top preferred formal method by formal ALs; (4) the physical, deployment, and operational viewpoints are rarely supported by ALs; (5) the top preferred extension mechanism of the extensible ALs is XML for syntax extension; (6) Java is the top preferred programming language in generating software code; (7) the exhaustive model checking is the top preferred automated analysis method; (8) the logic‐based formal techniques are so popular in specifying system requirements; (9) among the analysis properties considered, consistency is the top supported property for the automated checking; and (10) most ALs do not provide any discussion platform (eg, forums). Hence, these findings can be used by the new AL developers in addressing the needs of practitioners and bridging the gaps in the field. Practitioners can also use the findings to find out about the existing ALs and compare them to choose the one(s) that suits their needs best.

show abstract

An Extended Type System for OCL Supporting Templates and Transformations

Kyas

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Based on our experience in implementing a type-checker for the Object Constraint Language (OCL), we observed that OCL is not suitable for constraining a system under development, because changes in the underlying class diagram unnecessarily invalidate the type correctness of constraints, while their semantic value does not change. Furthermore, the type system of OCL does not support templates. To alleviate these problems, we extended the type system of OCL with intersection and union types and bounded operator abstraction. The main advantage of our type system is that it allows more changes in the contextual class diagrams without adapting the OCL constraints.

show abstract

OCL: Syntax, Semantics, and Tools

Cited by 71 publications

References 13 publications

An OCL Extension for Low-Coupling Preserving Contracts

An OCL Extension for Low-Coupling Preserving Contracts

The analysis of architectural languages for the needs of practitioners

An Extended Type System for OCL Supporting Templates and Transformations

Contact Info

Product

Resources

About