On Formalizing the UML Object Constraint Language OCL

Richters, Mark; Gogolla, Martin

doi:10.1007/978-3-540-49524-6_35

Cited by 97 publications

(65 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Other diagrams can optionally be provided. Extra information used for test generation and other features are represented in the models by means of custom stereotypes, element properties and OCL-like annotations (Richters and Gogolla, 1998). Note that this extended notation does not break backward compatibility with existing UML tools, as they are all contained in regular UML elements.…”

Section: Figure 3 Tedeso Model-based Architecture Overviewmentioning

confidence: 99%

Experiences using Tedeso: an extensible and interoperable model-based testing platform

et al. 2013

View full text Add to dashboard Cite

Abstract. The integration of novel software quality assurance tools into existing development environments must be performed in ways that leverage the benefits of the tools while minimizing their impact on existing software processes. This supports the adoption of new methodologies with minimal interference into core business practices. This paper discusses the design of Tedeso, an extensible and interoperable model-based testing platform developed to facilitate the automatic generation of tests, while supporting the needs of different stakeholders in a diverse and broad organization. We discuss Tedeso key design characteristics, in particular its extensibility and interoperability, provided through the use of a workflow-driven service-oriented architecture, and show how it has enabled and facilitated the adoption of model-based testing techniques in different business units in different sectors within SIEMENS. We also discuss some issues that come from the adoption of service-oriented architectures, showing how they have been managed in our platform.

show abstract

Section: Figure 3 Tedeso Model-based Architecture Overviewmentioning

confidence: 99%

Experiences using Tedeso: an extensible and interoperable model-based testing platform

et al. 2013

View full text Add to dashboard Cite

show abstract

“…There are numerous papers and even some dissertations that propose a formal semantics for complete OCL or for a fragment of it, e.g., [26,27,15,28,22,[29][30][31][32] and, recently, [21]. Many other papers have identified inconsistencies in the official OCL semantics and contributed in this form to a better understanding of OCL's concepts, e.g., [33,34,25,35,24].…”

Section: Approaches To Define the Semantics Of Oclmentioning

confidence: 99%

Semantics of OCL specified with QVT

Marković

Baar

2008

Softw Syst Model

View full text Add to dashboard Cite

The Object Constraint Language (OCL) has been for many years formalized both in its syntax and semantics in the language standard. While the official definition of OCL's syntax is already widely accepted and strictly supported by most OCL tools, there is no such agreement on OCL's semantics, yet. In this paper, we propose an approach based on metamodeling and model transformations for formalizing the semantics of OCL. Similarly to OCL's official semantics, our semantics formalizes the semantic domain of OCL, i.e. the possible values to which OCL expressions can evaluate, by a metamodel. Contrary to OCL's official semantics, the evaluation of OCL expressions is formalized in our approach by model transformations written in QVT. Thanks to the chosen format, our semantics definition for OCL can be automatically transformed into a tool, which evaluates OCL expressions in a given context. Our work on the formalization of OCL's semantics resulted also in the identification and better understanding of important semantic concepts, on which OCL relies. These insights are of great help when OCL has to be tailored as a constraint language of a given DSL. We show on an example, how the semantics of OCL has to be redefined in order to become a constraint language in a database domain.

show abstract

“…The Object Constraint Language (OCL) is a language to express constraints on models [15,23]. Hamie et al consider OCL in combination with state machines and classes [8].…”

Section: Related Workmentioning

confidence: 99%

Quality of Automatically Generated Test Cases based on OCL Expressions

Weißleder

Schlingloff

2008

2008 International Conference on Software Testing, Verification, and Validation

View full text Add to dashboard Cite

In this paper, we deal with coverage criteria for boundary testing. We focus on the automatic generation of boundary tests based on OCL expressions and evaluate the quality of these tests with established coverage criteria like MC/DC. We define and apply new coverage criteria, evaluate their efficiency via mutation testing, and substantiate all explanations by an example, part of a model of an elevator control.

show abstract

On Formalizing the UML Object Constraint Language OCL

Cited by 97 publications

References 13 publications

Experiences using Tedeso: an extensible and interoperable model-based testing platform

Experiences using Tedeso: an extensible and interoperable model-based testing platform

Semantics of OCL specified with QVT

Quality of Automatically Generated Test Cases based on OCL Expressions

Contact Info

Product

Resources

About