Checking Model Consistency Using Data-Flow Testing

Wang, Chen-Wei; Cavarra, Alessandra

doi:10.1109/apsec.2009.58

Cited by 7 publications

(5 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Finally, a set of constraints is often denoted as consistent if there exists at least one solution (e.g., a variable assignment) that satisfies all constraints (B. Wang et al 2010;C. Wang & Cavarra 2009;Gogolla et al 2009;Hao et al 1992;Straeten et al 2003).…”

Section: Consistencymentioning

confidence: 99%

Tolerance in Model-Driven Engineering: A Systematic Literature Review with Model-Driven Tool Support

Weidmann¹,

Kannan²,

Anjorin³

2021

Preprint

View full text Add to dashboard Cite

Managing models in a consistent manner is an important task in the field of Model-Driven Engineering (MDE).Although restoring and maintaining consistency is desired in general, recent work has pointed out that always strictly enforcing consistency at any point of time is often not feasible in real-world scenarios, and sometimes even contrary to what a user expects from a trustworthy MDE tool. The challenge of tolerating inconsistencies has been discussed from different viewpoints within and outside the modelling community, but there exists no structured overview of existing and current work in this regard.In this paper, we provide such an overview to help join forces tackling the unresolved problems of tolerating inconsistencies in MDE. We follow the standard process of a Systematic Literature Review (SLR) to point out what tolerance means, how it relates to uncertainty, which examples for tolerant software systems have already been discussed, and which benefits and drawbacks tolerating inconsistencies entails. Furthermore, we propose a tool-chain that helps conducting SLRs in computer science and also eases the reproduction of results. Relevant meta-data of the collected sources is uniformly described in a textual modelling language and exported to the graph database Neo4j to query aggregated information.

show abstract

Section: Consistencymentioning

confidence: 99%

Tolerance in Model-Driven Engineering: A Systematic Literature Review with Model-Driven Tool Support

Weidmann¹,

Kannan²,

Anjorin³

2021

Preprint

View full text Add to dashboard Cite

show abstract

“…CONCLUSION We propose the BOOSTER object modelling notation for describing operations as first-order predicates that characterise the intended state effects. As operations are combined into workflows, our previous work [3][4] present a novel testing methodology (Figure 1) for detecting inconsistency-w.r.t. the developers understanding about the requirements-in such behavioural models.…”

Section: Laws Booster Predicatesmentioning

confidence: 99%

“…In [3] [4] we already introduce an approach-as visualised in Figure 1to testing design models. We adopt an object modelling language named BOOSTER [5] targeted at the model-driven development [6] of information systems.…”

Section: Introductionmentioning

confidence: 99%

“…test scripts and concrete data values) for their implementing systems. Contribution: Under the same testing framework as established in [3][4], we present a contribution-highlighted in boldface in Figure 1-which facilitates the developers on revising their behavioural design model. We develop a list of rewriting rules (as summarised in Table I on page 6) to which the developers can refer when there is a needeither as requirements evolve, or as these requirements are not properly reflected in the design-to revise their behavioural design model.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Formal Approach for the Iterative Design of Behavioural Models

Wang

2012

2012 19th Asia-Pacific Software Engineering Conference

View full text Add to dashboard Cite

In the process of specifying update operations of an information system, it is critical to ensure that the resulting design is consistent with the developers' understanding about the requirements, before it is adapted to a chosen platform of implementation. We present a formal approach to testing behavioural specifications that characterise the intended effects on the state as two-state, first-order predicates. By supplying use-case scenarios that are of interest, the developers are able to examine the test results, decide if the model under test is consistent, and revise the source specifications if necessary. To facilitate an iterative process of this, in this paper we develop a list of equivalence and refinement (rewriting) laws of predicates that are targeted at information system states. Our development is built upon the formal semantics and logical properties of a formal language of substitutions that serves as an abstract implementation language for these predicates.

show abstract

“…We refer to "modeling assistants" as any software artifact intended to assist MDD users during modeling. Some examples of such novel approaches are the following: intelligent modeling assistants [11], wizards for generating models [12], and model consistency checkers [13,14]. All these data show the perspective of researchers on how to assist software modeling.…”

mentioning

confidence: 99%

Assisted-Modeling Requirements for Model-Driven Development Tools

Mosquera

Ruiz

Pastor

et al. 2022

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Model-driven development tools (MDD) allow software development teams to increase productivity and decrease software time-to-market [1]. MDD tools use models for automatically generating software source code. However, MDD tools are rarely adopted by software development practitioners. Some authors show that MDD tools have not yet surpassed the benefits of classical approaches such as the code-centric approach [2]. This has motivated researchers to investigate and establish unaddressed challenges to

show abstract

Checking Model Consistency Using Data-Flow Testing

Cited by 7 publications

References 14 publications

Tolerance in Model-Driven Engineering: A Systematic Literature Review with Model-Driven Tool Support

Tolerance in Model-Driven Engineering: A Systematic Literature Review with Model-Driven Tool Support

A Formal Approach for the Iterative Design of Behavioural Models

Assisted-Modeling Requirements for Model-Driven Development Tools

Contact Info

Product

Resources

About