Modular reasoning in the presence of event subtyping

Abstract

Separating crosscutting concerns while preserving modular reasoning is challenging. Type-based interfaces (event types) separate modularized crosscutting concerns (observers) and traditional object-oriented concerns (subjects). Event types paired with event specifications have been shown to be effective in enabling modular reasoning about subjects and observers. Similar to class subtyping there are benefits to organizing event types into subtyping hierarchies. However, unrelated behaviors of observers and their arbitrary execution orders could cause unique, somewhat counterintuitive, reasoning challenges in the presence of event subtyping. These challenges threaten both tractability of reasoning and reuse of event types. This work makes three contributions. First, we pose and explain these challenges. Second, we propose an event-based calculus to show how these challenges can be overcome. Finally, we present modular reasoning rules of our technique, and show its applicability to other event-based techniques including join point types. AbstractSeparating crosscutting concerns while preserving modular reasoning is challenging. Type-based interfaces (event types) separate modularized crosscutting concerns (observers) and traditional object-oriented concerns (subjects). Event types paired with event specifications were shown to be effective in enabling modular reasoning about subjects and observers. Similar to class subtyping, organizing event types into subtyping hierarchies is beneficial. However, unrelated behaviors of observers and their arbitrary execution orders could cause unique, somewhat counterintuitive, reasoning challenges in the presence of event subtyping. These challenges threaten both tractability of reasoning and reuse of event types. This work makes three contributions. First, we pose and explain these challenges. Second, we propose an event-based calculus to show how these challenges can be overcome. Finally, we present modular reasoning rules of our technique and show its applicability to other event-based techniques.

The design and implementation of Candoia: A platform for building and sharing mining software repositories tools as apps

“…An app built for one project setting can run across diverse project settings without requiring any change. 4. Customizability: Facilitate easy customization of apps by clearly defining various components of a Candoia app and choosing efficient script-based domain-specific languages (DSLs) to build the components.…”

“…Panini [40,41,43,39,54,55,69,3,56,42], a concurrent programming language to reimplement the backend of Candoia to further improve its efficiency. Another possibility might be to investigate the use of event-driven architecture and languages such as Ptolemy [58,57,19,6,22,4,25,5,19,7,19,22,25,23] to realize incremental data generation where a reader module fetches inputs from forges, e.g.…”

“…3 shows the relative number of null checking revisions. For some projects, the frequency of these fixes is quite significant, and for others e.g.…”

“…4 shows the values for NOE, EF and DMO metrics along with the number of bugs in the projects. For quite a few projects there is a strong correlation between bugs and the EF metrics.…”

Toward a Concurrent Programming Model with Modular Reasoning

“…In addition to the work presented in this thesis, I have been involved in the work on translucid contracts [17,20,21] to enable modular reasoning about functional and flow behaviors of event-based systems for both normal and exceptional executions [19] in the presence of event subtyping [15,16,50,53,54]. Translucid contracts build on the Ptolemy language [140][141][142] which supports explicit announcement and handling of typed events and allows for event type polymorphism [60].…”