2008
DOI: 10.1007/s11334-008-0065-0
|View full text |Cite
|
Sign up to set email alerts
|

UML behavioral consistency checking using instantiable Petri nets

Abstract: Model-driven engineering (MDE) development methods are gaining increasing attention from industry. In MDE, the model is the primary artifact and serves several goals, including code generation, requirements traceability, and model-based testing. MDE thus enables cost-effective building of models versus direct coding of an application. Thus model-based formal verification of behavioral consistency is desirable as it helps improve model quality. Our approach is based on translation of a UML model to instantiable… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
12
0

Year Published

2010
2010
2019
2019

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 26 publications
(12 citation statements)
references
References 14 publications
0
12
0
Order By: Relevance
“…In this category, Yong Ng et al [23] used CSP as a formal representation to check deadlock and divergence for the input UML state machines. ThierryMieg et al [32] used IPN (Instantiable Petri Nets [22]) to check deadlock and unreachable final states for the input UML activity diagrams. Also Turner et al [34] automatically formalized xUML state machines into CSP B [30] (an integrated formal language that combines CSP and B) to check deadlock.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In this category, Yong Ng et al [23] used CSP as a formal representation to check deadlock and divergence for the input UML state machines. ThierryMieg et al [32] used IPN (Instantiable Petri Nets [22]) to check deadlock and unreachable final states for the input UML activity diagrams. Also Turner et al [34] automatically formalized xUML state machines into CSP B [30] (an integrated formal language that combines CSP and B) to check deadlock.…”
Section: Related Workmentioning
confidence: 99%
“…Alternatively, Mrugalla et al in [21] presents the counter-example as sequence and timing diagrams. In another approach, the authors in [32,27] proposed compiler-style errors with valuable feedback.…”
Section: Related Workmentioning
confidence: 99%
“…The authors in [25,26] proposed presenting the model checking results (e.g., counter-example) as an object diagram that represents a snapshot of the system during the error. Alternatively, the authors in [27,28] proposed compiler style-errors with valuable feedback.…”
Section: Related Workmentioning
confidence: 99%
“…Translation of UML to CSP has been included in [17,18] which describe how to check the model dynamic behaviours and visualize the formal language into a graphical notation. Our work is more closely compared to [9,10] and [19] which consider the formalization of activity diagrams into CSP, and Petri nets respectively. The authors in [19] focus on checking deadlocks in the UML models, which is aligned to our work.…”
Section: Related Workmentioning
confidence: 99%
“…Our work is more closely compared to [9,10] and [19] which consider the formalization of activity diagrams into CSP, and Petri nets respectively. The authors in [19] focus on checking deadlocks in the UML models, which is aligned to our work. However, none of them addressed modelling the asynchronous communication between objects formally.…”
Section: Related Workmentioning
confidence: 99%