An approach for detecting inconsistencies between behavioral models of the software architecture and the code
Proceedings - International Computer Software and Applications Conference
257 - 266
MetadataShow full item record
Please cite this item using this persistent URLhttp://hdl.handle.net/11693/28072
In practice, inconsistencies between architectural documentation and the code might arise due to improper implementation of the architecture or the separate, uncontrolled evolution of the code. Several approaches have been proposed to detect inconsistencies between the architecture and the code but these tend to be limited for capturing inconsistencies that might occur at runtime. We present a runtime verification approach for detecting inconsistencies between the dynamic behavior of the documented architecture and the actual runtime behavior of the system. The approach is supported by a set of tools that implement the architecture and the code patterns in Prolog, and automatically generate runtime monitors for detecting inconsistencies. We illustrate the approach and the toolset for a Crisis Management System case study. © 2012 IEEE.
Showing items related by title, author, creator and subject.
Sözer H.; Hofmann, C.; Tekinerdoǧan, B.; Akşit, M. (2012)To deal with increasing size and complexity, component-based software development has been employed in embedded systems. Due to several faults, components can make wrong assumptions about the working mode of the system and ...
Tekinerdoǧan, B.; Aktekin, N. (2009)One of the basic pillars in Model-Driven Software Development (MDSD) is defined by model transformations and likewise several useful approaches have been proposed in this context. In parallel, domain modeling plays an ...
A run-time verification framework for smart grid applications implemented on simulation frameworks Ciraci, S.; Sozer H.; Tekinerdogan, B. (2013)Smart grid applications are implemented and tested with simulation frameworks as the developers usually do not have access to large sensor networks to be used as a test bed. The developers are forced to map the implementation ...