On some Problems with Modelling of Exceptions in UML

  • Authors:
  • Radosław Klimek;Paweł Skrzyński;Michał Turek

  • Affiliations:
  • AGH University of Science and Technology, Al. Mickiewicza 30, 30-095 Kraków, Poland, e-mails: {rklimek, skrzynia, mitu}@agh.edu.pl;AGH University of Science and Technology, Al. Mickiewicza 30, 30-095 Kraków, Poland, e-mails: {rklimek, skrzynia, mitu}@agh.edu.pl;AGH University of Science and Technology, Al. Mickiewicza 30, 30-095 Kraków, Poland, e-mails: {rklimek, skrzynia, mitu}@agh.edu.pl

  • Venue:
  • Proceedings of the 2005 conference on Software Engineering: Evolution and Emerging Technologies
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

During the last couple of years UML has been becoming more popular and has been rapidly accepted as the standard modelling language for specifying software and system architectures. Despite this popularity using UML 1.x caused some trouble and developers face some limitations due to the fact that software industry has evolved considerably during last seven years and software system become more and more complex. One of the most important issues in modem software systems is exception handling. Exception handling mechanism enables to make software systems robust and reliable [6]. However mechanism provided even by the 2.0 version of UML, in authors opinion, seems to be insufficient and is far from well-known implementation practise. UML does not put proper emphasis on exceptions handling the aim of the paper is to present the possibilities of excep-tions modelling in UML using statechart diagrams. These approach seems to be the most natural way to model the mechanism. Alternative methods, which should be taken into consideration in future research, are discussed at the end of the paper. UML dialect used is proposed by Telelogic so does the tool Tau G2.