Exception handling and object-oriented programming: towards a synthesis
OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Exception handling: issues and a proposed notation
Communications of the ACM
Alloy: a lightweight object modelling notation
ACM Transactions on Software Engineering and Methodology (TOSEM)
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
Exception handling in the development of dependable component-based systems
Software—Practice & Experience - Research Articles
Better Exception-Handling in Block-Structured Systems
IEEE Software
Model transformation of dependability-focused requirements models
MISE '09 Proceedings of the 2009 ICSE Workshop on Modeling in Software Engineering
Exception handling negligence due to intra-individual goal conflicts
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
Hi-index | 0.00 |
This paper presents the insights we gained in our research aimed at integrating exceptions and exception handling into the entire software development life cycle. We argue that exceptions are of different nature depending on the level of abstraction that the system under development is looked at. We outline a mapping relating exceptions at a high level of abstraction to exceptions and other software artifacts at lower levels of abstraction, and show that some exceptions introduced at a low level of abstraction also require the definition of corresponding exceptions at a higher level of abstraction in the case where transparent handling at the low level is not possible. Finally, we list the potential benefits of integrating exception handling into the entire software development life cycle.