Object-oriented modeling and design
Object-oriented modeling and design
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The object constraint language: precise modeling with UML
The object constraint language: precise modeling with UML
Designing robust Java programs with exceptions
SIGSOFT '00/FSE-8 Proceedings of the 8th ACM SIGSOFT international symposium on Foundations of software engineering: twenty-first century applications
| Hi-index | 0.00 |
While exception handling mechanisms are very useful for implementing systems, they are equally useful when building business models. The standard method of modeling exceptions in UML is to include them in class diagrams as a kind of signal, as stereotyped classes. However this alone is insufficient, since by the very nature of exceptions, the circumstances under which particular exceptions may be raised, as well as the details of what actions the class handling the exception will perform in doing so, tend to be rather complex and in general difficult to express pictorially. In this paper, we consider how this information may be specified using the Object Constraint Language (OCL). We illustrate our approach by applying it to a simple example.