Handling contract violations in Java Card using explict exception channels

Araújo, Juliana Iscarlaty Freire de; Souza, Rafael Castro de; Cacho, Nélio; Martins, Anamaria; Neto, Plácido A. Souza

doi:10.1109/weh.2012.6226596

Cited by 2 publications

(1 citation statement)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These findings seem to indicate that there is still much room for improving built-in EHM in programming languages. Our ongoing work encompasses the implementation of the EFlow model [2,7,8] for C# programming language. EFlow aims to improve the simultaneous satisfaction of software maintainability and reliability by using the notion of explicit exception channels, which support modular representation of global exceptional-behaviour properties.…”

Section: Resultsmentioning

confidence: 99%

Trading robustness for maintainability: an empirical study of evolving c# programs

Cacho

César

Filipe

et al. 2014

Proceedings of the 36th International Conference on Software Engineering

Self Cite

View full text Add to dashboard Cite

Mainstream programming languages provide built-in exception handling mechanisms to support robust and maintainable implementation of exception handling in software systems. Most of these modern languages, such as C#, Ruby, Python and many others, are often claimed to have more appropriated exception handling mechanisms. They reduce programming constraints on exception handling to favor agile changes in the source code.These languages provide what we call maintenance-driven exception handling mechanisms. It is expected that the adoption of these mechanisms improve software maintainability without hindering software robustness. However, there is still little empirical knowledge about the impact that adopting these mechanisms have on software robustness. This paper addressed this gap by conducting an empirical study aimed at understanding the relationship between changes in C# programs and their robustness. In particular, we evaluated how changes in the normal and exceptional code were related to exception handling faults. We applied a change impact analysis and a control flow analysis in 119 versions of 16 C# programs. The results showed that: (i) most of the problems hindering software robustness in those programs are caused by changes in the normal code, (ii) many potential faults were introduced even when improving exception handling in C# code, and (iii) faults are often facilitated by the maintenancedriven flexibility of the exception handling mechanism. Moreover, we present a series of change scenarios that decrease the program robustness.

show abstract

Section: Resultsmentioning

confidence: 99%