Exceptions in component interaction protocols – necessity

  • Authors:

  • Frantisek Plasil;Viliam Holub

  • Affiliations:

  • Faculty of Mathematics and Physics, Department of Software Engineering, Charles University, Prague 1, Czech Republic;Faculty of Mathematics and Physics, Department of Software Engineering, Charles University, Prague 1, Czech Republic

  • Venue:
  • Proceedings of the 2004 international conference on Architecting Systems with Trustworthy Components
  • Year:
  • 2004

Quantified Score

Hi-index 0.00

Visualization

Abstract

At ADL level, most of the current interaction protocols designed to specify components' behavior at their interfaces do not allow to capture exceptions explicitly. Based on our experience with real-life component based applications, handling exceptions as first class entities in a (formal) behavior specification is an absolute necessity. Otherwise, due to the need to capture exceptions indirectly, the specification becomes very complex, therefore hard to read and, consequently, error-prone. After analyzing potential approaches to introducing exceptions to LTS-based interaction specification (expressed via terms/expressions) in ADL, the paper presents the way we built exceptions into the behavior protocols. Finally, we discuss the positive experience with applying these exception-aware behavior protocols to a real-life Fractal component model application.