WOSS '02 Proceedings of the first workshop on Self-healing systems
Consistency management with repair actions
Proceedings of the 25th International Conference on Software Engineering
Runtime monitoring of cross-cutting policy
EA '09 Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design
Exploiting assumption-based verification for the adaptation of service-based applications
Proceedings of the 2010 ACM Symposium on Applied Computing
Process mining and verification of properties: an approach based on temporal logic
OTM'05 Proceedings of the 2005 Confederated international conference on On the Move to Meaningful Internet Systems - Volume >Part I
| Hi-index | 0.00 |
In our study of composite systems [Fickas&Helm, 92], we found a class of requirements that could not be guaranteed to hold. Specifically, these requirements required the environment of the overall system to behave in ways that could not be controlled. The best we could do in such cases was to note the assumptions placed on the environment for the requirements to be met, and then monitor the environment at runtime to detect deviations from our assumptions about its behavior [Fickas&Feather, 1995]. This paper discusses a short example of carrying out this type of monitoring. It introduces three tools to support requirements monitoring: (1) a tool to capture a requirement formally, (2) a tool to translate that requirement into a runtime specification, and (3) a tool to actually do the runtime monitoring.