Reflexion Models for State Machine Extraction and Verification

Said, Wasim; Quante, Jochen; Koschke, Rainer

doi:10.1109/icsme.2018.00025

Cited by 7 publications

(8 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Models are checked against LTL properties to validate state merges as they are encountered. In an attempt to model and verify software systems [22], state machines describing software behaviour are generated by checking a hypothetical, manually drawn model against the code. The user specifies a set of states and state invariants which are translated into relevant pre and post conditions in the code.…”

Section: Related Workmentioning

confidence: 99%

Learning Concise Models from Long Execution Traces

Jeppu

Melham

Kroening

et al. 2020

2020 57th ACM/IEEE Design Automation Conference (DAC)

View full text Add to dashboard Cite

models of system-level behaviour have applications in design exploration, analysis, testing and verification. We describe a new algorithm for automatically extracting useful models, as automata, from execution traces of a HW/SW system driven by software exercising a usecase of interest. Our algorithm leverages modern program synthesis techniques to generate predicates on automaton edges, succinctly describing system behaviour. It employs trace segmentation to tackle complexity for long traces. We learn concise models capturing transaction-level, systemwide behaviourexperimentally demonstrating the approach using traces from a variety of sources, including the x86 QEMU virtual platform and the Real-Time Linux kernel.

show abstract

Section: Related Workmentioning

confidence: 99%

Learning Concise Models from Long Execution Traces

Jeppu

Melham

Kroening

et al. 2020

2020 57th ACM/IEEE Design Automation Conference (DAC)

View full text Add to dashboard Cite

show abstract

“…This technique was adapted to state machine for ensuring the correspondence in terms of specified states and transitions among models and codes. 12 In the context of architecture-driven modernization, reflexion analysis was also applied to check conformance between the current and the planned architecture which are both represented with knowledge discovery metamodels. 13 Recent empirical studies 9,29 show that this technique is in widespread use in practice for architecture conformance checking.…”

Section: Architecture Conformance Checkingmentioning

confidence: 99%

“…Generally, this technique is conducted by comparing the implemented architecture and the architecture the system should have, that is, the intended architecture. There are two main means of conducting architecture conformance checking: 11 reflexion analysis 12,13 and compliance rules 14,15 . Even though several approaches to conformance checking exist in both directions (e.g., References 12 and 15), none of them explore how to check for architecture conformance in DDD‐based projects.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

DOMICO: Checking conformance between domain models and implementations

Zhong,

Zhang,

Huang

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

As a predominant design method for microsservices architecture (MSA), domain‐driven design (DDD) utilizes a series of standard patterns in both models and implementations to effectively support the design of architectural elements. However, an implementation may deviate from its original domain model that uses certain patterns. The deviation between a domain model and its implementation is a type of architectural drift, which needs to be detected promptly. This paper proposes an approach, namely DOMICO, to check the conformance between the domain model and its implementation, by which the conformance is formalized by defining eight common structural patterns of domain modeling and their representations in both models and the corresponding source code. Based on the formalization, our approach can not only identify the discrepancies (e.g., divergence, absence, and modification) with respect to pattern elements, but also detect possible violations of 24 compliance rules imposed by the patterns. To validate DOMICO, we performed a case study to investigate its use in a supply chain project and its performance. The results show that DOMICO can accurately identify 100% inconsistency issues in the cases examined. As the first conformance checking approach for DDD, DOMICO can be integrated into the regular domain modeling process and help ensure the conformity of microservice implementations to models.

show abstract

“…Murphy at al. [30], Koschke and Simon [18] and Said et al [34] propose reflection model techniques as architectural solutions for controlling the software erosion. The reflection model techniques compares a model of the implemented architecture and a hypothetical model of the intended architecture.…”

Section: Related Workmentioning

confidence: 99%

Detecting Architectural Erosion using Runtime Verification

Marmsoler

Petrovska

2019

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

The architecture of a system captures important design decisions for the system. Over time, changes in a system's implementation may lead to violations of specific design decisions. This problem is common in industry and known as architectural erosion. Since it may have severe consequences on the quality of a system, research has focused on the development of tools and techniques to address the presented problem. As of today, most of the approaches to detect architectural erosion employ static analysis techniques. While these techniques are well-suited for the analysis of static architectures, they reach their limit when it comes to dynamic architectures. Thus, in this paper, we propose an alternative approach based on runtime verification. To this end, we propose a systematic way to translate a formal specification of architectural constraints to monitors, which can be used to detect violations of these constraints. The approach is implemented in Eclipse/EMF, demonstrated through a running example, and evaluated using two case studies.

show abstract

Reflexion Models for State Machine Extraction and Verification

Cited by 7 publications

References 26 publications

Learning Concise Models from Long Execution Traces

Learning Concise Models from Long Execution Traces

DOMICO: Checking conformance between domain models and implementations

Detecting Architectural Erosion using Runtime Verification

Contact Info

Product

Resources

About