2012
DOI: 10.1007/978-3-642-30473-6_13
|View full text |Cite
|
Sign up to set email alerts
|

Evaluating and Debugging OCL Expressions in UML Models

Abstract: Abstract. This paper discusses the relationship between tests and proofs with focus on a tool for UML and OCL models. Tests are thought of as UML object diagrams and theorems or properties which are to be checked are represented as OCL constraints, i.e., class invariants or operation pre-and postconditions. The paper shows for the UML and OCL tool USE (UML-based Specification Environment) how to trace and debug the validity of an expected theorem (an OCL constraint) within a given test case (a state model in t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2013
2013
2020
2020

Publication Types

Select...
3
1

Relationship

2
2

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 6 publications
0
5
0
Order By: Relevance
“…1. It was continuously extended with new features, e. g. the Evaluation Browser (Brüning et al 2012) in the lower-right corner, state machine diagrams (Hamann, Hofrichter, & Gogolla 2012a) and communication diagrams in upperright corner.…”
Section: The Evolution Of Usementioning
confidence: 99%
“…1. It was continuously extended with new features, e. g. the Evaluation Browser (Brüning et al 2012) in the lower-right corner, state machine diagrams (Hamann, Hofrichter, & Gogolla 2012a) and communication diagrams in upperright corner.…”
Section: The Evolution Of Usementioning
confidence: 99%
“…In this paper, the UML-based Specification Environment tool (USE, [2]) is used together with the socalled model validator plugin that allows to generate system states for UML/OCL models based on a relational logic encoding [6]. There is earlier work showing features of the USE tool that help to analyze and debug OCL expressions, namely the evaluation browser [1], but we concentrate on the model validator and its model checking aspects in this work.…”
Section: Model Verification With the Use Toolmentioning
confidence: 99%
“…The GUI is split into three tabs that each cover a part of the configuration. 1 The first tab is the basic types tab in which the domains for the basic types of OCL are defined. The domains can be defined as ranges or specific values that will be used by the model validator.…”
Section: Configuration Guimentioning
confidence: 99%
See 1 more Smart Citation
“…This tool allows the designer to provide an instantiation of the schema and to check whether it satisfies the OCL constraints. USE may also trace and debug the validity of an expected theorem (i.e., an OCL constraint) within a given instantiation provided by the designer (Brüning et al 2012), but it does not tell the user whether there are other causes (i.e., explanations) for the same problem as AuRUS does. USE behaves as model checking since it may determine whether a constraint is violated, but it is not able to invent new instances that could complement the given test case to make it valid if it is not.…”
Section: Tools For Checking the Correctness Of A Uml/ocl Conceptual Smentioning
confidence: 99%