2010
DOI: 10.1007/978-3-642-13977-2_5
|View full text |Cite
|
Sign up to set email alerts
|

Proving and Visualizing OCL Invariant Independence by Automatically Generated Test Cases

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2010
2010
2019
2019

Publication Types

Select...
7
2

Relationship

2
7

Authors

Journals

citations
Cited by 13 publications
(10 citation statements)
references
References 14 publications
0
10
0
Order By: Relevance
“…In this paper we show a proposal that follows this latter approach, making use of some of the concepts, languages and tools that have proved to be very useful in the case of model specification and validation [16]. In particular, we generalize model transformation contracts [2,17] for the specification of the properties that need to be checked for a transformation, and then apply the ASSL language [18] to generate input test models, which are then automatically transformed into output models and checked against the set of contracts defined for the transformation, using the USE tool [19].…”
Section: Introductionmentioning
confidence: 99%
“…In this paper we show a proposal that follows this latter approach, making use of some of the concepts, languages and tools that have proved to be very useful in the case of model specification and validation [16]. In particular, we generalize model transformation contracts [2,17] for the specification of the properties that need to be checked for a transformation, and then apply the ASSL language [18] to generate input test models, which are then automatically transformed into output models and checked against the set of contracts defined for the transformation, using the USE tool [19].…”
Section: Introductionmentioning
confidence: 99%
“…For instance, it should be possible to create an instance that satisfies all the constraints in the model simultaneously. Also, it is desirable to be aware of redundancies among constraints [21], [22], [23]. These correctness properties can be formally checked using bounded verification.…”
Section: Overviewmentioning
confidence: 99%
“…Automated, more efficient support for this task (e.g., like the method proposed in [30]) is left for future work. Similarly, constraint redundancy can be (manually) investigated with solvers like USE [17], but automating this task is also left for future work. Once the constraint for package visibility is deleted from Employee, USE would return a model like the one in Figure 10(a), proving that there is no conflict, and provide the designer with an example of use of the designed annotation.…”
Section: Annotation Validationmentioning
confidence: 99%