Reasoning About Exception Flow at the Architectural Level

Filho, Fernando Castor; Brito, Patrick H. S.; Rubira, Cecília Mary Fischer

doi:10.1007/11916246_4

Cited by 3 publications

(6 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Anchored exceptions [39] and the work of Malayeri and Aldrich [28] enable modular reasoning about flow of exceptions using more expressive exception interfaces. EJFlow [11] enables reasoning about exception flow using architectural level exception ducts. Jex [33], and the works of Jo et al [18], Sinha et al [35] and Fu et al [13] propose global flow analyses for exceptions in Java.…”

Section: Related Workmentioning

confidence: 99%

On exceptions, events and observer chains

Bagherzadeh

Rajan

Darvish

2013

Proceedings of the 12th Annual International Conference on Aspect-Oriented Software Development

View full text Add to dashboard Cite

Modular understanding of behaviors and flows of exceptions may help in their better use and handling. Such reasoning tasks about exceptions face unique challenges in event-based implicit invocation (II) languages that allow subjects to implicitly invoke observers, and run the observers in a chain. In this work, we illustrate these challenge in Ptolemy and propose Ptolemyχ that enables modular reasoning about behaviors and flows of exceptions for event announcement and handling. Ptolemyχ's exception-aware specification expressions and boundary exceptions limit the set of (un)checked exceptions of subjects and observers of an event. Exceptional postconditions specify the behaviors of these exceptions. Greybox specifications specify the flows of these exceptions among the observers in the chain. Ptolemyχ's type system and refinement rules enforce these specifications and thus enable its modular reasoning. We evaluate the utility of Ptolemyχ's exception flow reasoning by applying it to understand a set of aspect-oriented (AO) bug patterns. We also present Ptolemyχ's semantics including its sound static semantics.

show abstract

Section: Related Workmentioning

confidence: 99%

On exceptions, events and observer chains

Bagherzadeh

Rajan

Darvish

2013

Proceedings of the 12th Annual International Conference on Aspect-Oriented Software Development

View full text Add to dashboard Cite

show abstract

“…Build a language-independent representation of the architecture. This intermediate representation is based on a system model described elsewhere [26]. It includes architectural elements that are instances of types defined by exceptional styles and exception-related information associated to these elements through relations that correspond to the properties listed of Table 3 Exception flow analysis consists in verifying if the generated Alloy specification satisfies Alloy predicates corresponding to properties of interest.…”

Section: Analyzing Exception Flowmentioning

confidence: 99%

“…O artigo que este capítulo contém será publicado como um capítulo do livro Rigorous Development of Complex Fault-Tolerant Systems [27] da série Lecture Notes in Computer Science. Uma versão preliminar [26] Campinas -SP -Brasil {fernando,pbrito,cmrubira}@ic.unicamp.br…”

Section: Capítulo 4 Análise De Fluxo De Exceções No Nível Arquiteturalunclassified

“…In a previous work, Castor and coleagues [26] described an initial version of the model presented in this paper. This early work does not unify the definitions of components and ducts and is harder to use and less scalable.…”

Section: Related Workmentioning

confidence: 99%

“…The operators all, <:, &&, and in represent, respectively, universal quantification, domain restriction, logical conjunction, and subset. A more detailed description of the system model defined by Aereal is available elsewhere [26]. Figure 3.12 shows a counterexample generated by the AA when we analyzed exception flow in the Alloy specification of the IB system.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Tratamento de exceções no desenvolvimento de sistemas tolerantes a falhas baseadas em componentes

Filho¹

View full text Add to dashboard Cite

Exception handling mechanisms were conceived as a means to help managing the complexity of fault-tolerant software. They promote an explicit textual separation between normal code and the code that deals with abnormal situations, in order to support the construction of programs that are more concise, evolvable, and reliable. Several mainstream programming languages and most of the existing component models implement exception handling mechanisms.In spite of its many benefits, exception handling can be a source of many design faults if used in an ad hoc fashion. Recent studies show that developers of large-scale software systems based on component infrastructures have habits concerning the use of exception handling that make applications vulnerable to faults and hard to maintain. Software components introduce new challenges which are not addressed by traditional exception handling mechanisms and increase the chances of problems occurring. Examples include unavailability of source code and architectural mismatches.In this work, we propose two complementary techniques centered on exception handling for the construction of fault-tolerant component-based systems. Both of them emphasize system structure as a means to reduce the impact of fault tolerance mechanisms on the overall complexity of a software system and the number of design faults that stem from complexity. The first one is an approach for the architectural design of a system's error handling capabilities. It addresses the problem of verifying whether a software architecture satisfies certain properties of interest pertaining the flow of exceptions between architectural components, e.g., if all the exceptions signaled at the architectural level are eventually handled. The proposed approach is based on a set of existing tools that automate this process as much as possible. The second one consists in applying aspectoriented programming (AOP) to better modularize exception handling code. We have conducted a through study aimed at improving our understanding of the effects of AOP on exception handling code and identifying the situations where its use is advantageous and the ones where it is not. viii AgradecimentosNormalmente, uma tese é o resultado do sangue, do suor, das lágrimas e dos neurônios de uma quantidade de gente muito maior do que caberia na maior das listas de agradecimentos. Esta não é exceção à regra e eu gostaria de expressar meus mui sinceros agradecimentos a todas as pessoas que contribuíram de alguma forma, mínima que seja, para a sua realização. Em especial, eu gostaria de agradecer... Em primeiro lugar à minha família, sem a qual eu não existiria e graças a quem eu cheguei até aqui: meus pais, Fernando e Maria, minha irmã, Donandréa, minha "mãe preta", Tia Zefinha, meu cunhado, Filipe, meu Avô, Nelson, e o dogo Bara. Amo vocês.À minha orientadora Cecília, pelos muitos ensinamentos, pelas várias discussões e idéias interessantes, sempre regadas a muito café, pelas diversas oportunidades que me proporcionou de evoluir como pesquisador e indiví...

show abstract