A methodology for specifying and analyzing consistency of object-oriented behavioral models

Engels, Gregor; Küster, Jochem M.; Heckel, Reiko; Groenewegen, Luuk

doi:10.1145/503234.503235

Cited by 21 publications

(39 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…-Syntactic consistency problems. This kind of consistency should guarantee that a model conforms to its abstract syntax (specified by its metamodel) [13]. -Semantic consistency problems.…”

Section: Background: Model Consistency Conceptsmentioning

confidence: 99%

See 1 more Smart Citation

A systematic review of UML model consistency management

Lucas

Molina

Toval

2009

Information and Software Technology

156

View full text Add to dashboard Cite

“…-Syntactic consistency problems. This kind of consistency should guarantee that a model conforms to its abstract syntax (specified by its metamodel) [13]. -Semantic consistency problems.…”

Section: Background: Model Consistency Conceptsmentioning

confidence: 99%

“…-Semantic consistency problems. This consistency requires that models' behaviour be semantically compatible [13].…”

Section: Background: Model Consistency Conceptsmentioning

confidence: 99%

A systematic review of UML model consistency management

Lucas

Molina

Toval

2009

Information and Software Technology

156

View full text Add to dashboard Cite

“…Thus, their approach cannot check consistency for timing behaviors of RTES. Engels et al (2001) presented a general methodology to check consistency for UML-RT state machine diagrams. UML-RT state machine diagrams were translated into CSP models.…”

Section: Uml Consistency Conceptsmentioning

confidence: 99%

Timing consistency checking for UML/MARTE behavioral models

2015

View full text Add to dashboard Cite

UML/MARTE model-driven development approaches are gaining attention in developing real-time embedded software (RTES). UML behavioral models with MARTE annotations are used to describe timing behaviors and timing characteristics of RTES. Particularly, state machine, sequence, and timing diagrams with MARTE annotations are appropriate to understand and analyze timing behaviors of RTES. However, to guarantee software correctness and safety, timing inconsistencies in UML/MARTE should be identified in the design phase of RTES. UML/MARTE timing inconsistencies are related to modeling errors and can be hazards throughout the lifecycle of RTES. We propose a systematic approach to check timing consistency of state machine, sequence, and timing diagrams with MARTE annotations for RTES. First, we present how state machine, sequence, and timing diagrams with MARTE annotations specify the behaviors of RTES. To overcome informal semantics of UML/MARTE models, we provide formal definitions of state machine, sequence, and timing diagrams with MARTE annotations. Second, we present the timing consistency checking approach that consists of a rule-based and a model checking-based timing consistency checking. In the rule-based timing consistency checking, we validate well formedness of UML/MARTE behavioral models in timing aspects. In the model checking-based timing consistency checking, we verify whether timing behaviors of sequence and timing diagrams with MARTE annotations are consistent with the timing behaviors of state machine diagrams with MARTE annotations. We support an automated timing consistency checking tool UML/MARTE timing Consistency Analyzer for a seamless approach. We demonstrate the effectiveness and the practicality of the proposed approach by two case studies using cruise control system software and guidance and control unit software.

show abstract

“…In the context of a more general methodology to specify and analyze the consistency of object-oriented behavior models, [72] addresses the problem of view consistency for protocols and component behavior in UML RT/ROOM [33]. Consistency is defined for each protocol and components connected via ports, having to specify all statecharts completely before a consistency check may be performed.…”

Section: Related Workmentioning

confidence: 99%

Separation of non-orthogonal concerns in software architecture and design

Giese

Vilbig

2006

Softw Syst Model

View full text Add to dashboard Cite

Separation of concerns represents an important principle for managing complexity in the design and architecture of large component-based software systems. The fundamental approach is to develop local solutions for individual concerns first, and combine them later into an overall solution for the complete system. However, comprehensive support for the integration of interdependent, possibly conflicting concerns related to synchronization behavior is still missing. In our work, we propose a sound solution for this complex type of composition, employing well-known UML description techniques as well as a rigorous formal model of component synchronization behavior. Based on this foundation, we describe a constructive synthesis algorithm which reliably detects conflicting concerns or generates a maximal synchronization behavior for software components with multiple interactions. An optimized implementation of the algorithm has been integrated into a CASE tool to illustrate feasibility and scalability of the presented technique to the example of a moderately large case study.

show abstract

A methodology for specifying and analyzing consistency of object-oriented behavioral models

Cited by 21 publications

References 0 publications

A systematic review of UML model consistency management

A systematic review of UML model consistency management

Timing consistency checking for UML/MARTE behavioral models

Separation of non-orthogonal concerns in software architecture and design

Contact Info

Product

Resources

About