Protective Wrapper Development: A Case Study
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
A formal architectural model for exception handling coordination
Proceedings of the 2008 ACM symposium on Applied computing
An architecture for exception management in multiagent systems
International Journal of Agent-Oriented Software Engineering
Science of Computer Programming
A definition of exceptions in agent-oriented computing
ESAW'06 Proceedings of the 7th international conference on Engineering societies in the agents world VII
A taxonomy of software architecture-based reliability efforts
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Performability modeling of exceptions-aware systems in multiformalism tools
ASMTA'11 Proceedings of the 18th international conference on Analytical and stochastic modeling techniques and applications
Supporting cross-language exception handling when extending applications with embedded languages
SERENE'11 Proceedings of the Third international conference on Software engineering for resilient systems
Exception handlers for healing component-based systems
ACM Transactions on Software Engineering and Methodology (TOSEM) - Testing, debugging, and error handling, formal methods, lifecycle concerns, evolution and maintenance
| Hi-index | 0.00 |
Designers of component-based software face two problems related to dealing with abnormal events: developing exception handling at the level of the integrated system and accommodating (and adjusting, if necessary) exceptions and exception handling provided by individual components. Our intention is to develop an exception handling framework suitable for component-based system development by applying general exception handling mechanisms which have been proposed and successfully used in concurrent/distributed systems and in programming languages. The framework is applied in three steps. Firstly, individual components are wrapped in such a way that the wrappers perform activity related to local error detection and exception handling, and signal, if necessary, external exceptions outside the component. At the second step the execution of the over-all system is structured as a set of dynamic actions in which components take parts. Such actions have important properties which facilitate exception handling: they are atomic, contain erroneous information and serve as recovery regions. The last step is designing exception handling at the action level: each action (i.e. all components participating in it) handles exceptions signalled by individual wrapped components.