A systematic approach for structuring exception handling in robust component-based software

Filho, Fernando Castor; Guerra, Paulo Asterio de C.; Pagano, Vinícius Asta; Rubira, Cecília Mary Fischer

doi:10.1590/s0104-65002005000100002

Cited by 8 publications

(1 citation statement)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This complementary activity has been addressed in previous work [6,16,17] . In the context of high confidence systems, the essential contributions of the paper are in the specification, verification and testing of fault-tolerant software architectures.…”

Section: Introductionmentioning

confidence: 65%

Architecting Fault Tolerance with Exception Handling: Verification and Validation

Brito

Lemos

Rubira

et al. 2009

J. Comput. Sci. Technol.

View full text Add to dashboard Cite

When building dependable systems by integrating untrusted software components that were not originally designed to interact with each other, it is likely the occurrence of architectural mismatches related to assumptions in their failure behaviour. These mismatches, if not prevented during system design, have to be tolerated during runtime. This paper presents an architectural abstraction based on exception handling for structuring fault-tolerant software systems. This abstraction comprises several components and connectors that promote an existing untrusted software element into an idealised fault-tolerant architectural element. Moreover, it is considered in the context of a rigorous software development approach based on formal methods for representing the structure and behaviour of the software architecture. The proposed approach relies on a formal specification and verification for analysing exception propagation, and verifying important dependability properties, such as deadlock freedom, and scenarios of architectural reconfiguration. The formal models are automatically generated using model transformation from UML diagrams: component diagram representing the system structure, and sequence diagrams representing the system behaviour. Finally, the formal models are also used for generating unit and integration test cases that are used for assessing the correctness of the source code. The feasibility of the proposed architectural approach was evaluated on an embedded critical case study.

show abstract

Section: Introductionmentioning

confidence: 65%

Architecting Fault Tolerance with Exception Handling: Verification and Validation

Brito

Lemos

Rubira

et al. 2009

J. Comput. Sci. Technol.

View full text Add to dashboard Cite

show abstract

On the modularization and reuse of exception handling with aspects

et al. 2009

View full text Add to dashboard Cite

This paper presents an in‐depth study of the adequacy of the AspectJ language for modularizing and reusing exception‐handling code. The study consisted of refactoring existing applications so that the code responsible for implementing error‐handling strategies was moved to newly created exception handler aspects. We have performed quantitative assessments of five systems—four object‐oriented and one aspect‐oriented—based on four key quality attributes, namely separation of concerns, coupling, cohesion, and conciseness. Our investigation also included a multi‐perspective analysis of the refactored systems, including (i) the extent to which error‐handling aspects can be reused, (ii) the beneficial and harmful aspectization scenarios for exception handling, and (iii) the scalability of AOP to support the modularization of exception handling in the presence of other aspects. Copyright © 2009 John Wiley & Sons, Ltd.

show abstract