An (Architecture-Centric) Approach for Tracing, Organizing, and Understanding Events in Event-Based Software Architectures

Hendrickson, Scott A.; Dashofy, Eric M.; Taylor, Richard N.

doi:10.1109/wpc.2005.6

Cited by 4 publications

(1 citation statement)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…TSL is later evolved in to the architecture description language Rapide (Luckham and Vera 1995), which provides extensive support for event-based specifications of software architectures. Hendrickson et al (2005) propose an approach that aids in understanding, debugging, and visualizing the reactive behavior of event-driven systems. This approach can address the problems due to possible mistakes during the evolution of statecharts, which is mentioned as future work in Section 14.4.…”

Section: C3mentioning

confidence: 99%

Experimental evaluation of a tool for the verification and transformation of source code in event-driven systems

et al. 2009

View full text Add to dashboard Cite

In event-driven systems, separating the reactive part of software (i.e., event-driven control) from the non-reactive part is a common design practice. The reactive part is typically structured according to the states and transitions of a system, whereas the non-reactive part is typically structured according to the concepts of the application domain (e.g., the services provided by the system). In such systems, the non-reactive part of software stimulates the reactive part with event calls. Whenever the non-reactive part is modified (e.g., during evolution), the existing event calls may become invalid, new event calls may become necessary, and the two parts of software may become incompatible. Manually finding and repairing these types of defects is a time-consuming and error-prone maintenance task. In this article, we present a solution that combines source code model checking and aspectoriented programming techniques, to reduce the time spent by developers and to automatically find defects, while performing the maintenance task mentioned above. In addition, we present controlled experiments showing that the solution can reduce the time by 75%, and enable the prevention of one defect per 140 lines of source code.

show abstract

Section: C3mentioning

confidence: 99%