Relevant bibliographies by topics / Exception Handling

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Exception Handling'

Author: Grafiati
Published: 4 June 2021
Last updated: 9 June 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Exception Handling.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Exception Handling"

1

K, Kwon. "Exception Handling in Logic Programming." Advances in Robotic Technology 1, no. 1 (October 2, 2023): 1–3. http://dx.doi.org/10.23880/art-16000104.

Full text
Abstract:
One problem on logic programming is to express exception handling. We argue that this problem can be solved by adopting linear logic and prioritized-choice disjunctive goal formulas (PCD) of the form G G 0 *1 ⊕ where G0, G1 are goals. These goals have the following intended semantics: sequentially choose the first true goal GI and execute GI where i (= 0 or 1), discarding the rest if any.
APA, Harvard, Vancouver, ISO, and other styles
2

Liu, Chuan Chang. "A Framework for Handling with Web Services Exception." Advanced Materials Research 121-122 (June 2010): 287–93. http://dx.doi.org/10.4028/www.scientific.net/amr.121-122.287.

Full text
Abstract:
Service oriented architecture presents us with a standards-based architecture for developing modular business applications and a lightweight framework for the business integration across heterogeneous platforms. However, due to the traits such as loose coupling, autonomy and distribution of web services, service oriented architecture is inherently vulnerable to exceptions. Moreover, the traditional exception handling strategies can hardly handle with the exceptions occurred in service oriented architecture. Based on the idea that exception management should be implemented in the system infrastructure, the paper presents a novel web services working framework with exception handling capability, including exception definition, exception handling policies, exception monitoring mechanism and handling process. The framework can dynamically monitor and handle with the exceptions that occur during the execution of web services.
APA, Harvard, Vancouver, ISO, and other styles
3

Abrantes, Joilson, Roberta Coelho, and Rodrigo Bonifácio. "DAEH: A Tool for Specifying and Monitoring the Exception Handling Policy." International Journal of Software Engineering and Knowledge Engineering 25, no. 09n10 (November 2015): 1515–30. http://dx.doi.org/10.1142/s0218194015400306.

Full text
Abstract:
The exception handling policy of a system comprises the set of design rules that specify its exception handling behavior (how exceptions should be handled and thrown). Such policy is usually undocumented and implicitly defined by the system architect. For this reason, developers often consider that by just including catch-blocks in the code they are dealing with exceptional conditions. This lack of information may turn the exception handling into a generalized “goto” mechanism making the program more complex and less reliable. This work presents a domain-specific language called ECL (Exception Contract Language) to specify the exception handling policy and a runtime monitoring tool which dynamically checks this policy. The monitoring tool is implemented in the form of an aspect library, which can be added to any Java system without the need to change the application source code. We applied this approach to two large-scale web-based systems and to a set of versions of the well-known JUnit framework. The results indicate that this approach can be used to express and to automatically check the exception handling policy of a system, and consequently support the development of more robust Java systems.
APA, Harvard, Vancouver, ISO, and other styles
4

Zhang, Chongyu, Qiping Tao, Liangyu Chen, and Min Zhang. "BERT-Based Code Learning for Exception Localization and Type Prediction." Proceedings of the AAAI Conference on Artificial Intelligence 39, no. 1 (April 11, 2025): 1040–47. https://doi.org/10.1609/aaai.v39i1.32090.

Full text
Abstract:
Exception handling is crucial but challenging in program development. It needs to identify and handle all potential exceptions within programs to ensure system security and stabilization. Traditional exception handling relies on the expertise and experience of programmers, which often leads to oversights. Therefore, identifying exceptional code and recommending handling solutions are hot research topics with significant practical value. This paper presents a model called CodeHunter for exception localization and type prediction. The model first utilizes BERT-based model to represent code features and then uses Bi-LSTM for sequence labeling to pinpoint exceptional code. Additionally, this model also considers contextual features of the exception code and learns weights for the code within the try block and its context through the self-attention mechanism. Subsequently, it performs exception localization and predicts exception types. We conduct experiments on three different datasets. The results demonstrate that in the task of exception localization, our model can achieve a maximum accuracy of 98.6%, exceeding SOTA baselines by 11.2%. In the task of exception type prediction, our model can surpass the accuracy of SOTA baselines by a maximum of 18.7%, achieving 92.0% Top-1 accuracy. The rationality of techniques used in our model is also proved by the ablation testing. The model is implemented as an IDE plugin for programming convenience.
APA, Harvard, Vancouver, ISO, and other styles
5

Strong, Diane M., and Steven M. Miller. "Exceptions and exception handling in computerized information processes." ACM Transactions on Information Systems 13, no. 2 (April 1995): 206–33. http://dx.doi.org/10.1145/201040.201049.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Hwang, San-Yih, and Jian Tang. "Consulting past exceptions to facilitate workflow exception handling." Decision Support Systems 37, no. 1 (April 2004): 49–69. http://dx.doi.org/10.1016/s0167-9236(02)00194-x.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

de Dinechin, C. "C++ exception handling." IEEE Concurrency 8, no. 4 (October 2000): 72–79. http://dx.doi.org/10.1109/4434.895109.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Neville-Neil, George. "Forced Exception-Handling." Queue 15, no. 1 (February 2017): 11–15. http://dx.doi.org/10.1145/3055301.3064643.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Neville-Neil, George V. "Forced exception handling." Communications of the ACM 60, no. 6 (May 24, 2017): 31–32. http://dx.doi.org/10.1145/3084356.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Fetzer, Christof, and Pascal Felber. "Improving Program Correctness with Atomic Exception Handling." JUCS - Journal of Universal Computer Science 13, no. (8) (August 28, 2007): 1047–72. https://doi.org/10.3217/jucs-013-08-1047.

Full text
Abstract:
Exception handling is a powerful mechanisms for dealing with failures at runtime. It simplifies the development of robust programs by allowing the programmer to implement recovery actions and tolerate non-fatal errors. Yet, exception handling is difficult to get right! The complexity of correct exception handling is a major cause for incorrect exception handling. It is therefore important to reduce the complexity of writing exception handling code while, at the same time, making sure it is correct. Our approach is to use atomic blocks for exception handling combined with optional compensation actions.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Exception Handling"

1

Shamal, Taher Sahand. "Exceptional Actors Implementing Exception Handling for Encore." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-330862.

Full text
Abstract:
Encore is an object-oriented programming language which uses the acto rmodel as its concurrency model, and is specifically aimed atimplementing concurrent and parallel systems. Communication between actors is done via asynchronous method calls, which store their results in futures, placeholder objects for later storing the result of a computation. Encore currently lacks an exception handling mechanism, which is an important part of programming languages, and helps programmers create more fault tolerant and robust software. This thesis presents an exception handling implementation for Encore, in whichfutures are used to propagate errors between actors. The implementation uses a modified version of the open-source library Exceptions4C as a basis, and enables basic exception handling through try-catch-finally expressions. It uses type-based matching that also considers subtyping, and allows the programmer to define and throw custom exception types. Apull-model is used to enable inter-process communication of exceptions, where receiving actors can choose to handle exceptions at any point by consuming associated futures. The implementation is a good first step,but there are Encore features such as streams which it does not yet support. Furthermore, it brings an overhead to programs, which can be reduced by redesigning parts of the exception handling model.
APA, Harvard, Vancouver, ISO, and other styles
2

Gurunath, Pramod. "OCL exception handling." Thesis, Texas A&M University, 2004. http://hdl.handle.net/1969.1/1281.

Full text
Abstract:
Object Constraint Language (OCL) is part of the Unified Modeling Language (UML) specification and can be used to enforce constraints on the attributes or methods of a class. It would greatly help the software developers if such non-executable OCL constraints specified in a UML model could be enforced on the executable code generated from the model. This thesis discusses the concepts, ideas and the approach in transforming a model developed in the Rational Rose software with OCL constraints into Java code shells, complete with fragments of code to detect the run-time violations of the constraints. The implementation and testing of a prototype tool that incorporates these ideas is also discussed.
APA, Harvard, Vancouver, ISO, and other styles
3

DAMASCENO, KARLA NAZARE FERREIRA. "CONTEXT-SENSITIVE EXCEPTION HANDLING." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2006. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=9181@1.

Full text
Abstract:
CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO<br>FUNDAÇÃO PADRE LEONEL FRANCA<br>Tratamento de erros em aplicações móveis sensíveis ao contexto não é uma tarefa trivial devido às características peculiares destes sistemas, como mobilidade, comunicação assíncrona e aumento de imprevisibilidade. Mecanismos convencionais de tratamento de exceções não podem ser utilizados por vários motivos. Primeiro, a propagação de erros deve considerar as mudanças contextuais que ocorrem constantemente nestes sistemas. Segundo, as atividades de recuperação de erros e a estratégia de tratamento de exceções também precisam freqüentemente ser selecionadas de acordo com as informações de contexto. Terceiro, a própria caracterização de uma exceção pode depender do contexto dos dispositivos envolvidos. Embora vários middlewares orientados a contexto ofereçam suporte ao desenvolvimento de aplicações móveis, estes sistemas raramente fornecem suporte adequado ao tratamento de exceções. Este trabalho realiza uma análise das soluções existentes para tratamento de exceções, considerando os requisitos de sensibilidade ao contexto. Além disso, são propostos um modelo para tratamento de exceções sensível ao contexto e um mecanismo implementado a partir de MoCA (Mobile Collaboration Architecture). MoCA é um middleware publish-subscribe que oferece suporte ao desenvolvimento de aplicações móveis colaborativas através da incorporação de serviços de contexto. Finalmente, este trabalho avalia o mecanismo de exceções proposto através de sua utilização em alguns protótipos de aplicações colaborativas desenvolvidas a partir de MoCA. Através do mecanismo, foram implementadas diferentes estratégias de tratamento de exceções que consideram as informações de contexto das aplicações.<br>Context-sensitive exception handling on mobile systems is not a trivial task due to their intrinsic characteristics: mobility, asynchrony and increased unpredictability. Conventional mechanisms of exception handling can not be used for many reasons. First, error propagation needs considering the contextual changes that often occur in these systems. Second, error recovery and exception handling strategies also frequently need to be selected according to contextual information. Third, the characterization of an exception may depend on the contextual situation of involved devices. Even though there are now several context-oriented middleware systems that provide support for the development of mobile applications, they rarely provide explicit and adequate features for contextsensitive exception handling. This work presents an analysis of existing exception handling mechanisms, which to some extent consider the context-awareness requirements. Besides, it proposes a general model for context-sensitive exception handling and a supporting mechanism implemented using the MoCA (Mobile Collaboration Architecture) infrastructure. MoCA is a publish-subscribe middleware supporting the development of collaborative mobile applications by incorporating explicit services to empower software agents with contextsensitiveness. Finally, this paper reports our experience in implementing contextaware exception handling strategies in some prototype collaborative applications built with the MoCA system.
APA, Harvard, Vancouver, ISO, and other styles
4

Cacho, Nelio Alessandro Azevedo. "Supporting Maintainable Exception Handling with Explicit Exception Channels." Thesis, Lancaster University, 2008. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.527180.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Sheikh, Muhammad Jamal. "Exception handling in software analysis." Thesis, McGill University, 2008. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=21999.

Full text
Abstract:
With the advancement in technology, software systems are more and more in control of devices that we use in our daily lives. Complex computer systems are increasingly built for highly critical tasks. Failures of such systems may have severe consequences ranging from loss of business opportunities, physical damage, to loss of human lives. Systems with such responsibilities should be highly dependable. Discovering and documenting potential abnormal situations and irregular user behavior that can interrupt normal system interaction is of tremendous importance in the context of dependable systems development. Exceptions that are identified during requirements elicitation have to be systematically carried over to a subsequent analysis phase, and included in the system specification in order to ensure that the implementation of the system later on can deal with all relevant exceptional situations. This thesis advocates a more methodical approach to exception handling by extending the requirements elicitation and analysis phases of the Fondue development process to address exceptions. Exceptions are discovered at the requirements stage of software development using a use-case based approach, and then mapped to the Fondue specification models: the environment model, in which exceptional messages that signal exceptional situations to the system, the concept model, in which exceptional state is specified that keeps track of the failures of secondary actors, and the operation model, in which recovery functionality is specified. The proposed ideas are illustrated by a comprehensive case study, the 407 ETR Electronic Toll Collection system.<br>Avec les avancements d'aujourd'hui, les appareils que nous utilisons dans notre vie quotidienne sont de plus en plus dans contrôles des systèmes informatiques. Les systèmes informatiques complexes prennent une nouvelle importance dans la réalisation des tâches hautement critiques. Un échec dans un tel système peut causer des pertes d'occasions d'affaires, des dommages physiques ou, dans le pire des cas, la perte de vies humaines. Les systèmes avec de telles responsabilités doivent être très fiables. La découverte et la documentation des situations potentiellement anormales, sans oublier le comportement irrégulier d'utilisateur qui peut interrompre les interactions régulières du système, sont d'une grande importance dans le contexte de développement de systèmes fiables. Les exceptions qui sont identifiées pendant la phase de collecte des spécifications doivent être systématiquement utilisées a la phase d'analyse, et doivent être également intégrées dans les spécifications systèmes pour assurer que l'implémentation du système peut réagir a toutes les situations exceptionnelles relatives. Cette thèse propose une approche plus méthodique pour la gestion des exceptions en prolongeant les phases de collection de spécifications et d'analyse du processus de développement Fondue pour y ajouter la gestion d'exceptions. Les exceptions sont découvertes dans la phase de spécification du cycle de développement en utilisant une approche cas d'utilisation "use case", pour ensuite les associer aux modèles de spécification Fondue : le modèle d'environnement ou se trouve les messages exceptionnels qui sont envoyés au système dans le cas d'une situation exceptionnelle, le modèle conceptuel, ou les états exceptionnels sont spécifiés un suivi des échecs des acteurs secondaires est effectué; et finalement le modèles opérationnel, ou les fonctionnalités sont spécifiées. Les idées proposées sont illustrées par une étude de cas é
APA, Harvard, Vancouver, ISO, and other styles
6

BARBOSA, EIJI ADACHI MEDEIROS. "RECOMMENDER SYSTEM FOR EXCEPTION HANDLING CODE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2012. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=20357@1.

Full text
Abstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO<br>FUNDAÇÃO DE APOIO À PESQUISA DO ESTADO DO RIO DE JANEIRO<br>Mecanismos de tratamento de exceções são modelos comumente usados em linguagens de programação para a estruturação do fluxo de execução excepcional de módulos de software. Tais mecanismos possibilitam a detecção e a sinalização da ocorrência de exceções, permitindo que módulos de software tomem medidas corretivas que recuperem o sistema para um estado correto. Estudos recentes mostram que falhas recorrentes e problemas de desempenho em aplicações de software estão relacionados à má qualidade do código que implementa o tratamento de exceções. Os estudos preliminares realizados no contexto desta dissertação não apenas corroboram esses resultados, como também evidenciam uma série de outros fatos interessantes que ocorrem durante a evolução de sistemas de software. Em especial, percebeu-se que é bastante comum nas versões preliminares de um sistema a implementação de ações de tratamento de exceções ineficazes. Também se percebeu que pouco (ou nenhum) esforço é realizado em termos de melhorar o tratamento de exceções durante a evolução do sistema de software. Os trabalhos recentes que se propõem a auxiliar desenvolvedores de software a lidar com código de tratamento de exceções falham em auxiliá-los em uma tarefa primordial: implementar código de tratamento de exceções bem estruturado desde as primeiras versões de um sistema. Neste contexto, o presente trabalho propõe um sistema de recomendação capaz de prover exemplos de código tratando exceções de modo a auxiliar desenvolvedores a implementarem seu próprio código em suas aplicações. O sistema extrai informações estruturais do código sob desenvolvimento para buscar por exemplos em um repositório local a fim de recomendar exemplos de código com contexto parecido ao que o desenvolvedor está trabalhando. O sistema implementado neste trabalho recomenda exemplos de código implementados em Java.<br>Exception handling mechanisms are models commonly used in programming languages to structure the exceptional execution flow of software modules. These mechanisms enable the detection and signaling of exception occurrences, allowing these modules to take corrective actions to recover a module to a correct state. Recent studies show that recurrent failures and performance issues in software applications are related to the poor structuring of exception handling code. The preliminary studies performed in the context of this dissertation not only confirm these results, but also show other interesting facts that occur during software evolution. In particular, it was realized that it is often very common to observe ineffective exception handling actions in the first releases of a system. It was also realized that little (or no) effort was allocated to improve the quality of these action during the software evolution. Recent studies that aim aiding software developers to deal with exception handling elements fail in assisting them in a crucial task: implementing well-structured exception handling code since the first release of a system. In this context, this dissertation proposes a recommender system able to provide code fragments implementing exception handling code. The proposed strategy aims to assist developers in implementing their own code in their applications. The system extracts structural information from the code under development to search for examples in a local repository in order to recommend code examples that share similar structural context with the code that the developer is working on. The system implemented in the context of this dissertation recommends code examples implemented in Java.
APA, Harvard, Vancouver, ISO, and other styles
7

Drew, Steve. "Exception handling with fail-safe semantics." Thesis, Queensland University of Technology, 1996. https://eprints.qut.edu.au/36827/1/36827_Digitised%20Thesis.pdf.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Tellefsen, Christian. "An Examination of Issues with Exception Handling Mechanisms." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2007. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9529.

Full text
Abstract:
<p>Exception handling suffers from a fluke in its evolution. Some time in the 1970's, a researcher called Goodenough introduced the exception handling mechanism, known today as the tcode{try...catch} construct. At about the same time, two fellows called Parnas and Würges published a paper about "undesired events". This paper appears forgotten. The funny thing is, Parnas and Würges effectively described how to emph{use} exception handling mechanisms. There is a need to respond to this undesired event. Exception handling suffers from lack of design guidelines and a number of inconsistencies with the object-oriented paradigm, among other things. The thesis' main contribution is creating a library of exception challenges and the evaluation of safety facades, an approach that introduce an architecture and guidelines for designing exception handling. Through qualitative evaluation, this thesis shows how safety facades form an interesting new approach to exception handling.</p>
APA, Harvard, Vancouver, ISO, and other styles
9

BARBOSA, EIJI ADACHI MEDEIROS. "GLOBAL-AWARE RECOMMENDATIONS FOR REPAIRING EXCEPTION HANDLING VIOLATIONS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2015. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=26804@1.

Full text
Abstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>CONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO<br>FUNDAÇÃO DE APOIO À PESQUISA DO ESTADO DO RIO DE JANEIRO<br>Tratamento de exceções e o modo mais comum de lidar com erros no desenvolvimento de software robusto. Tratamento de exceções refere-se ao processo de sinalizar exceções quando erros em tempo de execução são detectados e de tomar ações para responder à ocorrência destas exceções. Apesar de objetivarem a melhoria da robustez de software, sistemas de software ainda são implementados sem se basear em uma política explícita para tratamento de exceções. Cada política define as decisões de projeto que governam como tratamento de exceções deve ser implementado num sistema. Tais políticas não são comumente documentadas e são apenas implicitamente definidas no projeto do sistema. Desta forma, desenvolvedores tendem a introduzir no código fonte violações das políticas implícitas e tais violações comumente causam falhas em sistemas de software. Neste contexto, o objetivo desta tese é apoiar desenvolvedores na detecção e reparação de violações de tratamento de exceções. Para atingir este objetivo, duas soluções complementares foram propostas. A primeira solução é baseada numa linguagem específica de domínio que apoia a detecção de violações ao definir explicitamente políticas de tratamento de exceções que devem ser obedecidas no código fonte. A linguagem proposta foi avaliada num estudo centrado no usuário e num estudo de caso. Com as observações e as experiências coletadas no estudo centrado no usuário, nós identificamos algumas características da linguagem que dificultavam o seu uso e que motivaram novos construtos. Além disso, os resultados do estudo de caso mostraram que violações e falhas costumam ter causas comuns. Portanto, violações de tratamento de exceção podem ser usadas para detectar causas de faltas relacionadas à exceções. Para complementar a detecção de violações, este trabalho também propôs uma solução para apoiar o reparo de violações de tratamento de exceções. Reparar estas violações requer raciocinar sobre o impacto global que mudanças em tratamento de exceções pode ter em diferentes partes do sistema. Desta forma, este trabalho propôs uma estratégia heurística de recomendação que leva em conta o contexto global onde violações ocorrem a fim de produzir recomendações. Cada recomendação produzida consiste em uma sequência de modificações que servem como um plano detalhado de como uma violação de tratamento de exceções pode ser removida do código fonte. A estratégia de recomendação proposta também se beneficia de especificações explícitas de políticas, embora sua disponibilidade não seja obrigatória. Os resultados das nossas avaliações empíricas revelaram que a estratégia de recomendação proposta produziu recomendações capazes de reparar violações em aproximadamente 70 por cento dos casos. Quando especificações de políticas estão disponíveis, a estratégia produziu recomendações capazes de reparar violações em 97 por cento dos casos.<br>Exception handling is the most common way of dealing with exceptions in robust software development. Exception handling refers to the process of signaling exceptions upon the detection of runtime errors and taking actions to respond to their occurrence. Despite being aimed at improving software robustness, software systems are still implemented without relying on explicit exception handling policies. Each policy defines the design decisions governing how exception handling should be implemented in a system. These policies are often not documented and are only implicitly defined in the system design. Thus, developers tend to introduce in the source code violations of implicit policies and these violations commonly cause failures in software systems. In this context, the goal of this thesis is to support developers in detecting and repairing exception handling violations. To achieve this goal, two complementary solutions were proposed. The first solution is based on a domain-specific language supporting the detection of violations by explicitly defining exception handling policies to be enforced in the source code. The proposed language was evaluated with a user-centric study and a case study. With the observations and experiences gathered in the user-centric study, we identified some language characteristics that hindered its use and that motivated new language constructs. In addition, the results of the case study showed that violations and faults in exception handling share common causes. Therefore, violations can be used to detect potential causes of exceptionrelated failures. To complement the detection of exception handling violations, this work also proposed a solution for supporting the repair of exception handling violations. Repairing these violations requires reasoning about the global impact that exception handling changes might have in different parts of the system. Thus, this work proposed a recommender heuristic strategy that takes into account the global context of where violations occur to produce recommendations. Each recommendation produced consists of a sequence of modifications that serves as a detailed blueprint of how an exception handling violation can be removed from the source code. The proposed recommender strategy also takes advantage of explicit policy specifications, although their availability is not mandatory. The results of our empirical assessments revealed that the proposed recommender strategy produced recommendations able to repair violations in approximately 70 per cent of the cases. When policy specifications are available, it produced recommendations able to repair violations in 97 per cent of the cases.
APA, Harvard, Vancouver, ISO, and other styles
10

Mahanga, Mwaka. "Unknown Exception Handling Tool Using Humans as Agents." UNF Digital Commons, 2015. http://digitalcommons.unf.edu/etd/563.

Full text
Abstract:
In a typical workflow process, exceptions are the norm. Exceptions are defined as deviations from the normal sequence of activities and events. Exceptions can be divided into two broad categories: known exceptions (i.e., expected and predefined deviations) and unknown exceptions (i.e., unexpected and undefined deviations). Business Process Execution Language (BPEL) has become the de facto standard for executing business workflows with the use of web services. BPEL includes exception handling methods that are sufficient for known exception scenarios. Depending on the exception and the specifics of the exception handling tools, processes may either halt or move to completion. Instances of processes that are halted or left incomplete due to unhandled exceptions affect the performance of the workflow process, as they increase resource utilization and process completion time. However, designing efficient process handlers to avoid the issue of unhandled exceptions is not a simple task. This thesis provides a tool that handles unknown exceptions using provisions for exception handling with the involvement of human activities by using the BPEL4PEOPLE specification. BPEL4PEOPLE, an extension of BPEL, offers the ability to specify human activities within BPEL processes. The approach considered in this thesis involves humans in exception handling tools by providing an alternate sub process within a given business process. A prototype application has been developed implementing the tool that handles unknown exceptions. The prototype application monitors the progress of an automated workflow process and permits human involvement to reroute the course of a workflow process when an unknown exception occurs. The utility of the prototype and the tool using the Scenario Walkthrough and Inspection Methods (SWIMs) are demonstrated. We demonstrate the utility of the tool through loan application process scenarios, and offer a walkthrough of the system by using examples of instances with examples of known and unknown exceptions, as well as a claims analysis of process instances results.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Exception Handling"

1

Mejia Alvarez, Pedro, Raul E. Gonzalez Torres, and Susana Ortega Cisneros. Exception Handling. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50681-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Romanovsky, Alexander, Christophe Dony, Jørgen Lindskov Knudsen, and Anand Tripathi, eds. Advances in Exception Handling Techniques. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-45407-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Dony, Christophe, Jørgen Lindskov Knudsen, Alexander Romanovsky, and Anand Tripathi, eds. Advanced Topics in Exception Handling Techniques. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11818502.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Stelting, Stephen. Robust Java: Exception handling, testing, and debugging. Upper Saddle River, N.J: Prentice Hall PTR, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Nedialkov, Nedialko Stoyanov. Precision control and exception handling in scientific computing. Ottawa: National Library of Canada, 1994.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Strong, Diane M. Modeling exception handling and quality control in information processes. Boston, MA: BostonUniversity, School of Management, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Healey, Gordon James. The design and implementation of an exception handling facility for concurrent Euclid. Toronto: University of Toronto, Dept. of Computer Science, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Russo, Vincent. Process management and exception handling in multiprocessor operating systems using object-oriented design techniques. Urbana, IL (1304 W. University Ave., Urbana 61801-2987): Dept. of Computer Science, University of Illinois at Urbana-Champaign, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Klein, Mark. A knowledge-based approach to handling exceptions in workflow systems. Cambridge, Mass: Sloan School of Management, Massachusetts Institute of Technology, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Metcalf, Michael, John Reid, and Malcolm Cohen. Floating-point exception handling. Oxford University Press, 2018. http://dx.doi.org/10.1093/oso/9780198811893.003.0018.

Full text
Abstract:
Exception handling is required for the development of robust and efficient numerical software, a principal application of Fortran. Indeed, the existence of such a facility makes it possible to develop more efficient software than would otherwise be possible. Most computers nowadays have hardware based on the IEEE standard for binary floating-point arithmetic, which later became an ISO standard. Therefore, the Fortran exception handling features are based on the ability to test and set the five flags for floating-point exceptions that the IEEE standard specifies.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Exception Handling"

1

Mejia Alvarez, Pedro, Raul E. Gonzalez Torres, and Susana Ortega Cisneros. "Exception Handling in Real-Time and Embedded Systems." In Exception Handling, 73–109. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50681-9_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Mejia Alvarez, Pedro, Raul E. Gonzalez Torres, and Susana Ortega Cisneros. "Exception Handling Best Practices." In Exception Handling, 29–47. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50681-9_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mejia Alvarez, Pedro, Raul E. Gonzalez Torres, and Susana Ortega Cisneros. "Introduction to Exception Handling." In Exception Handling, 1–16. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50681-9_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Mejia Alvarez, Pedro, Raul E. Gonzalez Torres, and Susana Ortega Cisneros. "Basics of Exception Handling." In Exception Handling, 17–28. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50681-9_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mejia Alvarez, Pedro, Raul E. Gonzalez Torres, and Susana Ortega Cisneros. "Advanced Exception Handling Techniques." In Exception Handling, 49–72. Cham: Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-50681-9_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Adams, Michael, and Nick Russell. "Exception Handling." In Modern Business Process Automation, 147–73. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-03121-2_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Olsson, Mikael. "Exception Handling." In C++ 14 Quick Syntax Reference, 107–9. Berkeley, CA: Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-1727-6_25.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Zambon, Giulio. "Exception Handling." In Practical C, 119–36. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1769-6_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Olsson, Mikael. "Exception Handling." In PHP 7 Quick Scripting Reference, 127–29. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1922-5_30.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Hunt, John. "Exception Handling." In Guide to C# and Object Orientation, 229–39. London: Springer London, 2002. http://dx.doi.org/10.1007/978-1-4471-0193-2_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Exception Handling"

1

Xie, Tao, and Suresh Thummalapenta. "Making exceptions on exception handling." In 2012 5th International Workshop on Exception Handling (WEH). IEEE, 2012. http://dx.doi.org/10.1109/weh.2012.6226593.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Wang, Ching-Yang, and Robert E. Fulton. "An Architecture for Handling Manufacturing Exceptions Based on Information Integration." In ASME 1994 International Computers in Engineering Conference and Exhibition and the ASME 1994 8th Annual Database Symposium collocated with the ASME 1994 Design Technical Conferences. American Society of Mechanical Engineers, 1994. http://dx.doi.org/10.1115/edm1994-0501.

Full text
Abstract:
Abstract Currently, most efforts to characterize manufacturing processes are based on the normal process assumption and pay little attention to exceptions. An exception is either a rare or an unexpected event which interrupts the normal manufacturing processes. There are potential exceptions in all stages of manufacturing processes. Exceptions like resource mismanagement (at the management decisions level), process out-of-control (at the technical strategies level) and product quality deterioration (at the operational plans level) can and do occur. These exceptions can have detrimental effects on quality, reliability and productivity. Little is known about managing unexpected events in manufacturing information integration. A conceptual exception model for handling manufacturing exceptions is proposed. The architecture of the exception model includes the views of levels impacted, process flow, inference network and decision propagation, information relations, math/logic formalism, feedback control, user action and avoidance knowledge base. These multiple views are designed to aid in understanding the exceptional problems, in characterizing the information requirements and in building an information system. An information system for an optical fiber manufacturing process was implemented as a case study of the model. The case study has been implemented in the Smalltalk environment. The developing procedure of the information system serves to illustrate the concepts of the exception model. This research is expected to benefit persons, such as system integrators, who need to build exception management information systems. Such an information system provides a platform for users to execute exception management capabilities such as recovery plans to aid in coping with exceptions and the impact and decision propagation regarding exceptions.
APA, Harvard, Vancouver, ISO, and other styles
3

Romanovsky, Alexander. "On Exceptions, Exception Handling, Requirements and Software Lifecycle." In 10th IEEE High Assurance Systems Engineering Symposium (HASE'07). IEEE, 2007. http://dx.doi.org/10.1109/hase.2007.71.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Feather, Martin S. "Modularized exception handling." In Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96). New York, New York, USA: ACM Press, 1996. http://dx.doi.org/10.1145/243327.243644.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Krischer, Roy, and Peter A. Buhr. "Usability challenges in exception handling." In 2012 5th International Workshop on Exception Handling (WEH). IEEE, 2012. http://dx.doi.org/10.1109/weh.2012.6226604.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Jacobs, Bart. "Provably live exception handling." In the 17th Workshop. New York, New York, USA: ACM Press, 2015. http://dx.doi.org/10.1145/2786536.2786543.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Nguyen, Tam, Phong Vu, and Tung Nguyen. "Recommending Exception Handling Code." In 2019 IEEE International Conference on Software Maintenance and Evolution (ICSME). IEEE, 2019. http://dx.doi.org/10.1109/icsme.2019.00066.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Carlsson, Richard, Björn Gustavsson, and Patrik Nyblom. "Erlang's exception handling revisited." In the 2004 ACM SIGPLAN workshop. New York, New York, USA: ACM Press, 2004. http://dx.doi.org/10.1145/1022471.1022475.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Lucas, Jim. "Array oriented exception handling." In the international conference. New York, New York, USA: ACM Press, 1985. http://dx.doi.org/10.1145/17701.255318.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Li, Yi, Tien N. Nguyen, Yuchen Cai, Aashish Yadavally, Abhishek Mishra, and Genesis Montejo. "Neural Exception Handling Recommender." In ICSE-Companion '24: 2024 IEEE/ACM 46th International Conference on Software Engineering: Companion Proceedings. New York, NY, USA: ACM, 2024. http://dx.doi.org/10.1145/3639478.3643082.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Exception Handling"

1

Bischof, C., G. Corliss, and A. Griewank. ADIFOR exception handling. Office of Scientific and Technical Information (OSTI), January 1992. http://dx.doi.org/10.2172/5745734.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Cui, Qian. Data-Oriented Exception Handling. Fort Belvoir, VA: Defense Technical Information Center, January 1990. http://dx.doi.org/10.21236/ada232645.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Klein, Mark. An Exception Handling Service for Software Agent Ensembles. Fort Belvoir, VA: Defense Technical Information Center, February 2004. http://dx.doi.org/10.21236/ada421591.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Bischof, C., G. Corliss, and A. Griewank. ADIFOR exception handling. ADIFOR Working Note No. 3. Office of Scientific and Technical Information (OSTI), January 1992. http://dx.doi.org/10.2172/10123577.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Fang, Aiman, Ignacio Laguna, Kento Sato, Tanzima Islam, and Kathryn Mohror. Fault Tolerance Assistant (FTA): An Exception Handling Programming Model for MPI Applications. Office of Scientific and Technical Information (OSTI), May 2016. http://dx.doi.org/10.2172/1258538.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Greer, J. T. Hierarchical architecture for automated electrom beam (EB) welding systems: Exception handling and robust controllers. Office of Scientific and Technical Information (OSTI), May 1989. http://dx.doi.org/10.2172/6162227.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Lowry, Svetlana Z., Mala Ramaiah, Emily S. Patterson, Latkany A. Paul, Debora Simmons, David Brick, and Michael C. Gibbons. Electronic Health Record Design Considerations in Responding to Incidences of Highly Infectious Diseases: Clinical Workflows and Exception Handling. National Institute of Standards and Technology, December 2015. http://dx.doi.org/10.6028/nist.ir.8095.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Hauser, John R. Handling Floating-point Exceptions in Numeric Programs. Fort Belvoir, VA: Defense Technical Information Center, March 1995. http://dx.doi.org/10.21236/ada637041.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Gwin, Catherine, Mayra Ruiz, Saleema Vellani, and Alejandro Guerrero. IDB-9: Access to Information. Inter-American Development Bank, March 2013. http://dx.doi.org/10.18235/0010517.

Full text
Abstract:
Following up on the IDB-9 commitments, the Inter-American Development Bank (IDB, or Bank) established a new Access to Information Policy that took effect on January 1, 2011. The new policy was expected to match international best practices and to increase the overall transparency of the Bank, strengthening its governance and development effectiveness. This review assesses the extent to which the access to information reform has been fully and effectively implemented. The review finds that the new policy largely matches best practices in comparator institutions, with, however, one provision that is unique to the IDB policy and inconsistent with the core principle of transparency: a broadly written exception to disclosure of country-specific information to which a country objects. As evidence of country use of this exception already suggests, this exception could completely undermine the access to information reform endeavor. The policy cannot be implemented effectively unless the country-specific exception is narrowed. Overall, the Bank is in the process of fully implementing the Access to Information Policy. Implementation progress has been substantial in the key areas of designing a regulatory framework, training staff, upgrading the Bank's document management system, and establishing governance structures and processes; and issues are being addressed as they become evident. Still, key steps to full and effective implementation remain under way. As a consequence, the effectiveness of the new policy has been significant in relation to the disclosure of key documents (such as Board-related information) but remains limited overall. Important revisions to the Implementation Guidelines have taken much longer than planned, and remain a work in progress. Timely disclosure and improved online access remain challenges. The share of documents made public under the new policy has decreased marginally, and staff and external stakeholders report limited awareness of the new policy. These findings reflect a need to improve IT monitoring systems to ensure policy compliance, expand staff training, broaden the communications strategy, and improve the online accessibility of information. This review offers six suggestions for further actions to advance effective implementation of the Access to Information Policy: (i) revise the policy to clarify that redaction is the remedy for country objections to disclosure of country-specific information, and make explicit that the final decision on the handling of information lies with the Bank, after consultation in cases of country concern; (ii) to be consistent with IDB-9 commitments to disclose project results, include Expanded Project Supervision Reports (XPSRs) in the list of disclosed information for non-sovereign-guaranteed operations; (iii) to effectively monitor policy compliance, establish a mechanism to spot-check the accuracy of document classification; (iv) enhance and launch the planned tracking system for timely disclosure of public information; (v) improve the IDB's website and better integrate the different repository systems to ensure easy and adequate accessibility to the Bank's information; and (vi) identify and track indicators of transparency.
APA, Harvard, Vancouver, ISO, and other styles
10

Aalto, Juha, and Ari Venäläinen, eds. Climate change and forest management affect forest fire risk in Fennoscandia. Finnish Meteorological Institute, June 2021. http://dx.doi.org/10.35614/isbn.9789523361355.

Full text
Abstract:
Forest and wildland fires are a natural part of ecosystems worldwide, but large fires in particular can cause societal, economic and ecological disruption. Fires are an important source of greenhouse gases and black carbon that can further amplify and accelerate climate change. In recent years, large forest fires in Sweden demonstrate that the issue should also be considered in other parts of Fennoscandia. This final report of the project “Forest fires in Fennoscandia under changing climate and forest cover (IBA ForestFires)” funded by the Ministry for Foreign Affairs of Finland, synthesises current knowledge of the occurrence, monitoring, modelling and suppression of forest fires in Fennoscandia. The report also focuses on elaborating the role of forest fires as a source of black carbon (BC) emissions over the Arctic and discussing the importance of international collaboration in tackling forest fires. The report explains the factors regulating fire ignition, spread and intensity in Fennoscandian conditions. It highlights that the climate in Fennoscandia is characterised by large inter-annual variability, which is reflected in forest fire risk. Here, the majority of forest fires are caused by human activities such as careless handling of fire and ignitions related to forest harvesting. In addition to weather and climate, fuel characteristics in forests influence fire ignition, intensity and spread. In the report, long-term fire statistics are presented for Finland, Sweden and the Republic of Karelia. The statistics indicate that the amount of annually burnt forest has decreased in Fennoscandia. However, with the exception of recent large fires in Sweden, during the past 25 years the annually burnt area and number of fires have been fairly stable, which is mainly due to effective fire mitigation. Land surface models were used to investigate how climate change and forest management can influence forest fires in the future. The simulations were conducted using different regional climate models and greenhouse gas emission scenarios. Simulations, extending to 2100, indicate that forest fire risk is likely to increase over the coming decades. The report also highlights that globally, forest fires are a significant source of BC in the Arctic, having adverse health effects and further amplifying climate warming. However, simulations made using an atmospheric dispersion model indicate that the impact of forest fires in Fennoscandia on the environment and air quality is relatively minor and highly seasonal. Efficient forest fire mitigation requires the development of forest fire detection tools including satellites and drones, high spatial resolution modelling of fire risk and fire spreading that account for detailed terrain and weather information. Moreover, increasing the general preparedness and operational efficiency of firefighting is highly important. Forest fires are a large challenge requiring multidisciplinary research and close cooperation between the various administrative operators, e.g. rescue services, weather services, forest organisations and forest owners is required at both the national and international level.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Exception Handling' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography