Romanovsky, A., "An exception handling framework for N-version programming in object-oriented systems," Proceedings Third IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2000 Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Bridging the Gap between Hardware And Software Fault.. - Patino-Martinez.. (2002) Self-citation (Romanovsky) (Correct)
....at the application level. Exception handling is widely used as most modern programming languages incorporate it and have features for declaring exceptions in different scopes and associating handlers with them. In general, exceptions of each scope are divided into external and internal [XRR98, Rom00a] depending on whether they are propagated out of the scope where they are signalled or not. Exceptions handled in the scope where they are raised are classified as internal exceptions. Exceptions that are propagated outside the scope in which they are signalled are called external exceptions. ....
....structuring and promotes disciplined approaches to tolerating faults of many types. 14 Such exceptions are used in all situations when a server cannot deliver the required results (for example: illegal input parameters, environmental faults, delivering partial results, server failure) Paper [Rom00a] proposes a scheme that allows diversely designed servers to have external exceptions in their interfaces. Clearly all of the versions have to have the same set of external exceptions because such exceptions have to be treated as an immanent part of server specification. The scheme requires an ....
A. Romanovsky. An Exception Handling Framework for N-Version programming in Object-Oriented Systems. In Proc. of the 3rd IEEE Int. Symp. on Object-oriented Realtime Distributed Computing (ISORC'2000), pages 226--233, Newport Beach, USA, March 2000. IEEE Computer Society Press.
A Comparative Study of Exception Handling Mechanisms for.. - Garcia, Rubira (2001) (2 citations) Self-citation (Romanovsky) (Correct)
....1. Moreover, it is also important to assure that an internal exception raised by a specific component is not propagated to higher level components; that is, only exceptions categorised as external can be propagated outwards (see Section 2. 1) Ideally, the following restrictions should be imposed [Romanovsky, 2000b] given a component X, i) all its internal exceptions have to have handlers; and (ii) all external exceptions have to be signalled to the containing exception context, in order to inform that X was not able to produce the required result. These external exceptions have to be internal to each ....
....binding; v) explicit propagation; vi) termination; and (vii) concurrent exception handling. Nevertheless, it does not support either statement handlers or else explicit separation between external and internal exceptions. Exception Handling and N Version Programming. The work of Romanovsky [Romanovsky, 2000b] presents a scheme for introducing exception handling into object oriented N version programming, and shows the importance of using exceptions while applying diversely developed software. Internal and external exceptions are clearly separated in this proposal: each version has its own internal ....
Romanovsky, A., An Exception Handling Framework for N-Version Programming in ObjectOriented Systems, Proceedings of the 3rd IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, Newport Beach, USA, 2000.
High Performance Robust Computer Systems - DeVale (2001) (1 citation) (Correct)
No context found.
Romanovsky, A., "An exception handling framework for N-version programming in object-oriented systems," Proceedings Third IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2000
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC