Exception handling in a cooperative object-oriented approach

A cooperative action (CO action) is a modelling abstraction for representing collaborative behaviour between objects at different phases of the software development. In this paper, the original definition of a cooperative object-oriented approach for software development is extended in order to include the description of exceptional behaviour. Unlike the traditional methods that usually deal with exceptions at the late design and implementation phases, the proposed approach emphasises the separation of treatments of application-related, design-related and implementation-related exceptions during the software life-cycle. The feasibility of the approach is demonstrated in terms of a benchmark case study.

[1]  Kathryn L. Heninger.  Specifying Software Requirements for Complex Systems: New Techniques and Their Application , 2001, IEEE Transactions on Software Engineering.

[2]  Rogério de Lemos,et al.  Extended RTL in the Specification and Verification of an Industrial Press , 1995, Hybrid Systems.

[3]  Brian Randell,et al.  Coordinated Atomic Actions: from Concept to Implementation , 1997 .

[4]  A. Saeed,et al.  Exception Handling in Real-Time Software from Specification to Design , 1993 .

[5]  A. Saeed,et al.  Analysis of safety requirements in the context of system faults and human errors , 1995, Proceedings of the 1995 International Symposium and Workshop on Systems Engineering of Computer-Based Systems.

[6]  Jie Xu,et al.  Coordinated exception handling in distributed object systems: from model to system implementation , 1998, Proceedings. 18th International Conference on Distributed Computing Systems (Cat. No.98CB36183).

[7]  강문설.  [서평]「The Unified Modeling Language User Guide」 , 1999 .

[8]  Cecília M. F. Rubira,et al.  Fault tolerance in concurrent object-oriented software through coordinated error recovery , 1995, Twenty-Fifth International Symposium on Fault-Tolerant Computing. Digest of Papers.

[9]  Flaviu Cristian,et al.  Exception Handling and Tolerance of Software Faults , 1995 .

[10]  Rogério de Lemos,et al.  ERTL: an extension to RTL for the specification, analysis and verification of hybrid systems , 1996, Proceedings of the Eighth Euromicro Workshop on Real-Time Systems.

[11]  Avelino Francisco Zorzo,et al.  On distribution of coordinated atomic actions , 1997, OPSR.

[12]  Anand R. Tripathi,et al.  Issues with Exception Handling in Object-Oriented Systems , 1997, ECOOP.

[13]  Claus Lewerentz,et al.  Formal Development of Reactive Systems: Case Study Production Cell , 1995 .

[14]  Stephen Riddle,et al.  An Object-Based Approach to Modelling and Analysis of Failure Properties , 1997, SAFECOMP.

[15]  Bent Bruun Kristensen,et al.  Activities: Abstractions for Collective Behavior , 1996, ECOOP.

[16]  Axel van Lamsweerde,et al.  Integrating obstacles in goal-driven requirements engineering , 1998, Proceedings of the 20th International Conference on Software Engineering.

[17]  Aloysius K. Mok,et al.  Safety analysis of timing properties in real-time systems , 1986, IEEE Transactions on Software Engineering.

[18]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[19]  Brian Randell,et al.  Error recovery in asynchronous systems , 1986, IEEE Transactions on Software Engineering.

[20]  David Lorge Parnas,et al.  Software Requirements for the A-7E Aircraft. , 1992 .

[21]  Rogério de Lemos,et al.  Coordinated atomic actions in modelling object cooperation , 1998, Proceedings First International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC '98).