Object-oriented development in an industrial environment
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
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
Exception handling: issues and a proposed notation
Communications of the ACM
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process
Writing Effective Use Cases
Exception handling in the development of dependable component-based systems
Software—Practice & Experience - Research Articles
Better Exception-Handling in Block-Structured Systems
IEEE Software
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Correct analysis for embedded system modeling: an outcome of east-west scientific cooperation
Proceedings of the 2008 international workshop on Software Engineering in east and south europe
DREP: A Requirements Engineering Process for Dependable Reactive Systems
Methods, Models and Tools for Fault Tolerance
Fault Tolerance Requirements Analysis Using Deviations in the CORRECT Development Process
Methods, Models and Tools for Fault Tolerance
Hi-index | 0.00 |
During the execution of an application many exceptional situations arise that interrupt the normal interaction of the system with its environment. When developing dependable software, the first step is to foresee these exceptional situations and document how the system should deal with them. Any such exception that is not identified during requirements elicitation might potentially lead to an incomplete system specification during analysis, and ultimately to an implementation that lacks certain functionality, or even behaves in an unreliable way, or in a way that is not expected by the users of the system. This paper outlines an approach that extends use case based requirements elicitation with ideas from the exception handling world. After defining the actors and the goals they pursue when interacting with the system, our approach leads a developer to systematically investigate possible exceptional situations that the system may be exposed to: exceptional situations arising in the environment that change user goals and system-related exceptional situations that threaten to fail user goals. The process requires the developer to specify means that detect such situations, and define the recovery measures, i.e. the exceptional interaction between the actors and the system, necessary to recover from such situations in handler use cases. To conclude the requirements phase, an extended UML use case diagram summarizes the standard use cases, exceptions, handlers and their relationships. In addition, all exceptional situations are carefully documented in an exception table.