Supporting automatic model inconsistency fixing

Xiong, Yingfei; Hu, Zhenjiang; Zhao, Haiyan; Song, Hui; Takeichi, Masato; Mei, Hong

doi:10.1145/1595696.1595757

Cited by 67 publications

(77 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The work presented in this paper relates to the area of model traceability [24] and fixing model inconsistency. Egyed [5] and Xiong et al [25] create consistency rules between different types of UML models. The rules, either built-into a tool [5] or specified by an engineer [25], are checked and propagated automatically or semi-automatically when a model is modified.…”

Section: Related Workmentioning

confidence: 99%

“…Egyed [5] and Xiong et al [25] create consistency rules between different types of UML models. The rules, either built-into a tool [5] or specified by an engineer [25], are checked and propagated automatically or semi-automatically when a model is modified. In our framework, we maintain behavioral consistency between models of the same type, but of different scopes.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Distributing refinements of a system-level partial behavior model

Krka

Medvidović

2013

2013 21st IEEE International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Abstract-Early in a system's life cycle, a system's behavior is typically partially specified using scenarios, invariants, and temporal properties. These specifications prohibit or require certain behaviors, while leaving other behaviors uncategorized into either of those. Engineers refine the specification by eliciting more requirements to finally arrive at a complete behavioral description. Partial-behavior models have been utilized to compactly capture, analyze, and elaborate the partial system specification. Under the current practices, software systems are reasoned about and their behavior specified exclusively at the system level, disregarding of the fact that a system typically consists of interacting components. However, exclusively refining a behavior specification at the system-level runs the risk of arriving at an inconsistent specification, i.e. one that is not realizable as a composition of the system's components. To address this problem, we propose a framework that provides the lacking support: when a system's partial behavior model is refined in accordance with a new requirement, our framework distributes the refinement to the components' models and ensures overall consistency. We discuss the framework's soundness and correctness, and demonstrate its features on a case study previously used in related literature.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Distributing refinements of a system-level partial behavior model

Krka

Medvidović

2013

2013 21st IEEE International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

show abstract

“…Most progress has been on the detecting of inconsistencies [35], [36], [37], [38], [39], [40], [41], [42] because an inconsistency is indicative of an incomplete or incorrect change propagation. There also have been attempts in generating fixes for inconsistencies [43], [44], [37] where the "fixes" could be seen analogous to propagated changes. Approaches such as xLinkIt [43] or Beanbag [37] are representative of this group.…”

Section: Collaboration Awarenessmentioning

confidence: 99%

“…There also have been attempts in generating fixes for inconsistencies [43], [44], [37] where the "fixes" could be seen analogous to propagated changes. Approaches such as xLinkIt [43] or Beanbag [37] are representative of this group. Change propagation has been addressed more directly by Briand et al [45] who identify specific change propagation rules.…”

Section: Collaboration Awarenessmentioning

confidence: 99%

Towards collaboration-centric pattern-based software development support

Dorn

Egyed

2013

2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)

View full text Add to dashboard Cite

Abstract-Software engineering activities tend to be loosely coupled to allow for flexibly reacting to unforeseen development complexity, requirements changes, and progress delays. This flexibility comes a the price of hidden dependencies among design and code artifacts that make it difficult or even impossible to assess change impact. Incorrect change propagation subsequently results in costly errors. This position paper proposes a novel approach based on monitoring engineering activities for subsequent high-level pattern detection. Patterns of (i) collaboration structures, (ii) temporal action sequences, and (iii) artifact consistency constraints serve as input to recommendation and automatic reconfiguration algorithms for ultimately avoiding and correcting artifact inconsistencies.

show abstract

“…Recently, a lot of research effort has been put into automatic bug fixing [1,2,3,4,5,6]. Given a violated correctness condition, these approaches try to modify the code to satisfy the condition.…”

Section: Introductionmentioning

confidence: 99%

Safe Memory-Leak Fixing for C Programs

Gao

Xiong

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

Self Cite

View full text Add to dashboard Cite

Abstract-Automatic bug fixing has become a promising direction for reducing manual effort in debugging. However, general approaches to automatic bug fixing may face some fundamental difficulties. In this paper, we argue that automatic fixing of specific types of bugs can be a useful complement.This paper reports our first attempt towards automatically fixing memory leaks in C programs. Our approach generates only safe fixes, which are guaranteed not to interrupt normal execution of the program. To design such an approach, we have to deal with several challenging problems such as inter-procedural leaks, global variables, loops, and leaks from multiple allocations. We propose solutions to all the problems and integrate the solutions into a coherent approach.We implemented our inter-procedural memory leak fixing into a tool named LeakF ix and evaluated LeakF ix on 15 programs with 522k lines of code. Our evaluation shows that LeakF ix is able to successfully fix a substantial number of memory leaks, and LeakF ix is scalable for large applications.

show abstract

Supporting automatic model inconsistency fixing

Cited by 67 publications

References 16 publications

Distributing refinements of a system-level partial behavior model

Distributing refinements of a system-level partial behavior model

Towards collaboration-centric pattern-based software development support

Safe Memory-Leak Fixing for C Programs

Contact Info

Product

Resources

About