Artykuły w czasopismach: „Exception Handling”

1

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

2

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

3

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

4

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

5

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

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

6

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

Pełny tekst źródła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

7

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

Pełny tekst źródła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

8

Snyder, Van. "Exception Handling in Fortran". ACM SIGPLAN Fortran Forum 34, nr 1 (3.04.2015): 5–9. http://dx.doi.org/10.1145/2754942.2754943.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

9

Lucas, Jim. "Array oriented exception handling". ACM SIGAPL APL Quote Quad 15, nr 4 (12.05.1985): 1–4. http://dx.doi.org/10.1145/255315.255318.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

10

Romanovsky, Alexander, i Bo Sandén. "Except for exception handling …". ACM SIGAda Ada Letters XXI, nr 3 (wrzesień 2001): 19–25. http://dx.doi.org/10.1145/568671.568678.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

11

Snyder, Van. "Exception Handling in Fortran". ACM SIGPLAN Fortran Forum 35, nr 2 (29.07.2016): 24–27. http://dx.doi.org/10.1145/2980025.2980028.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

12

Cui, Q., i J. Gannon. "Data-oriented exception handling". IEEE Transactions on Software Engineering 18, nr 5 (maj 1992): 393–401. http://dx.doi.org/10.1109/32.135772.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

13

Buhr, P. A., i W. Y. R. Mok. "Advanced exception handling mechanisms". IEEE Transactions on Software Engineering 26, nr 9 (2000): 820–36. http://dx.doi.org/10.1109/32.877844.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

14

Markus, Arjen. "Exception handling in Fortran". ACM SIGPLAN Fortran Forum 32, nr 2 (12.07.2013): 7–13. http://dx.doi.org/10.1145/2502932.2502933.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

15

VISSER, A. "An exception-handling framework". International Journal of Computer Integrated Manufacturing 8, nr 3 (maj 1995): 197–203. http://dx.doi.org/10.1080/09511929508944645.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

16

Cox, I. J., i N. H. Gehani. "Exception handling in robotics". Computer 22, nr 3 (marzec 1989): 43–49. http://dx.doi.org/10.1109/2.16224.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

17

Dillenburg, Fabiane Cristine, i Jorge Luis Victoria Barbosa. "Context-oriented exception handling". International Journal of High Performance Systems Architecture 2, nr 1 (2009): 16. http://dx.doi.org/10.1504/ijhpsa.2009.030095.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

18

Wu, Qing. "Formalization and Verification of Exception Handling Logic in Service-Oriented Software". Advanced Materials Research 479-481 (luty 2012): 1151–54. http://dx.doi.org/10.4028/www.scientific.net/amr.479-481.1151.

Pełny tekst źródła

Streszczenie:

The dynamic and uncertainty in service-oriented software(SOS) running environment , together with the autonomy and loose coupling of service resources，lead to higher workload and more complexity of exception handling. Aiming to guarantee the completeness of design for exception handling logic in service- oriented software, this paper proposed a formal description method which and the corresponding integrated verification method for exception handling logic. This method can guide the design quickly and efficiently construct exception handling logic model in service-oriented software, and validate whether all exceptions which explicitly declare in service-oriented software are processed

Style APA, Harvard, Vancouver, ISO itp.

19

Ritter, Daniel, i Jan Sosulski. "Exception Handling in Message-Based Integration Systems and Modeling Using BPMN". International Journal of Cooperative Information Systems 25, nr 02 (czerwiec 2016): 1650004. http://dx.doi.org/10.1142/s0218843016500040.

Pełny tekst źródła

Streszczenie:

Enterprise Integration Patterns (EIP) are a collection of widely used patterns for integrating enterprise applications and business processes. These patterns represent a “de-facto” standard for design decisions when integrating enterprise applications. For the specification of integration scenarios, the patterns’ control and data flow syntax and semantics have been expressed in the Business Process Model and Notation (BPMN). However, exceptions during message processing are left for further studies. In previous work, we specified common technical, exceptional situations in integration systems and derive exception types, for which we define a compliant representation in BPMN, resulting in general patterns for exception handling and compensation. In addition to the patterns, the Exception Flow was introduced, evaluated syntactically and semantically for representative integration scenarios. In this work, we complement these contributions by extending the exception strategies and patterns, and by adding an evaluation of pattern-based compilation from BPMN-based integration descriptions to an open source integration runtime system.

Style APA, Harvard, Vancouver, ISO itp.

20

Liu, Kaiping, Hee Beng Kuan Tan i Xu Chen. "Automated Insertion of Exception Handling for Key and Referential Constraints". Journal of Database Management 24, nr 1 (styczeń 2013): 1–19. http://dx.doi.org/10.4018/jdm.2013010101.

Pełny tekst źródła

Streszczenie:

Key and referential constraints are two main integrity constraints in database applications. These constraints can be automatically enforced by the Database Management System with their exception—violation from these constraints—handled by programmers. This paper proposes an approach to relieve the burden of programmers from mechanical coding for handling exceptions of these constraints violation by using program transformation. We first propose an extended abstract syntax tree to include SQL query semantics. Based on it, each code pattern that requires exception handling together with the exception handling code to be inserted is represented as a transformation rule. We provide two alternatives to handle the exceptions: one is to handle the exceptions in conjunction with the built-in enforcement feature in Database Management System; the other is handling them without using the feature provided in Database Management System. Hence, two types of transformation rules are provided accordingly. A tool GEHPHP (Generation of Exception Handling for PHP Systems) has been developed to implement the proposed approach. Experiments have also been conducted to evaluate the applicable of the approach.

Style APA, Harvard, Vancouver, ISO itp.

21

Sarma, Monalisa. "Mutation Analysis Approach to Develop Reliable Object-Oriented Software". Advances in Software Engineering 2014 (25.12.2014): 1–16. http://dx.doi.org/10.1155/2014/197983.

Pełny tekst źródła

Streszczenie:

In general, modern programs are large and complex and it is essential that they should be highly reliable in applications. In order to develop highly reliable software, Java programming language developer provides a rich set of exceptions and exception handling mechanisms. Exception handling mechanisms are intended to help developers build robust programs. Given a program with exception handling constructs, for an effective testing, we are to detect whether all possible exceptions are raised and caught or not. However, complex exception handling constructs make it tedious to trace which exceptions are handled and where and which exceptions are passed on. In this paper, we address this problem and propose a mutation analysis approach to develop reliable object-oriented programs. We have applied a number of mutation operators to create a large set of mutant programs with different type of faults. We then generate test cases and test data to uncover exception related faults. The test suite so obtained is applied to the mutant programs measuring the mutation score and hence verifying whether mutant programs are effective or not. We have tested our approach with a number of case studies to substantiate the efficacy of the proposed mutation analysis technique.

Style APA, Harvard, Vancouver, ISO itp.

22

Wu, Qing, Shi Ying, You Cong Ni i Hua Cui. "The Architecture Framework with Exception Handing in SOA". Applied Mechanics and Materials 20-23 (styczeń 2010): 992–97. http://dx.doi.org/10.4028/www.scientific.net/amm.20-23.992.

Pełny tekst źródła

Streszczenie:

Service-oriented software systems are inherently complex and have to cope with an increasing number of exceptional conditions in order to meet the system’s dynamic requirements. This work proposes an architecture framework which has exception handling capability. This framework ensures the credibility of service-oriented software, during the architectural stage, by adding exception handling-related architecture elements and modeling exception handling process. It allows a clear separation of concerns between the business function and the exception handling unit, using reflection mechanism. It plays an important guiding role for achieving reliable service-oriented system.

Style APA, Harvard, Vancouver, ISO itp.

23

Cui, Ji Tao, i Jian Hua Han. "Exception Handling of Composite Services Based on Autonomic Management". Applied Mechanics and Materials 336-338 (lipiec 2013): 2537–43. http://dx.doi.org/10.4028/www.scientific.net/amm.336-338.2537.

Pełny tekst źródła

Streszczenie:

BPEL-based composition of Web services has become one important part of business processes, but because of the dynamic and complexity of network, it easily raises various exceptions during the execution. In order to address various exceptions may exist in execution of composite Web services process effectively; this paper proposes an effective exception handling model of composite Web services in combination of the autonomic management theories and techniques in the field of autonomic computing. This model incorporates the autonomic management element of autonomic computing to monitor the execution of composite services and to compensate or restore the business process of the composite services according to the specified policy when an exception occurs. The model enhances the exception handling autonomy while reducing the complexity of exception handling of composite services.

Style APA, Harvard, Vancouver, ISO itp.

24

Rashkovits, Rami, i Ilana Lavy. "Students’ Strategies for Exception Handling". Journal of Information Technology Education: Research 10 (2011): 183–207. http://dx.doi.org/10.28945/1500.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

25

Hull, T. E., M. S. Cohen, J. T. M. Sawshuk i D. B. Wortman. "Exception handling in scientific computing". ACM Transactions on Mathematical Software 14, nr 3 (wrzesień 1988): 201–17. http://dx.doi.org/10.1145/44128.44129.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

26

Turba, Thomas N. "The Pascal exception handling proposal". ACM SIGPLAN Notices 20, nr 8 (sierpień 1985): 93–98. http://dx.doi.org/10.1145/988346.988360.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

27

Jakšić, Svetlana, i Luca Padovani. "Exception handling for copyless messaging". Science of Computer Programming 84 (maj 2014): 22–51. http://dx.doi.org/10.1016/j.scico.2013.05.001.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

28

Schilling, Jonathan L. "Optimizing away C++ exception handling". ACM SIGPLAN Notices 33, nr 8 (sierpień 1998): 40–47. http://dx.doi.org/10.1145/286385.286390.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

29

Perry, D. E., A. Romanovsky i A. Tripathi. "Current trends in exception handling". IEEE Transactions on Software Engineering 26, nr 9 (wrzesień 2000): 817–19. http://dx.doi.org/10.1109/tse.2000.877843.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

30

Perry, D. E., A. Romanovsky i A. Tripathi. "Current trends in exception handling". IEEE Transactions on Software Engineering 26, nr 10 (październik 2000): 921–22. http://dx.doi.org/10.1109/tse.2000.879816.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

31

Black, David L., David B. Golub, Karl Hauth, Avadis Tevanian i Richard Sanzi. "The mach exception handling facility". ACM SIGPLAN Notices 24, nr 1 (3.01.1989): 45–56. http://dx.doi.org/10.1145/69215.69220.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

32

Szalas, Andrzej, i Danuta Szczepanska. "Exception handling in parallel computations". ACM SIGPLAN Notices 20, nr 10 (październik 1985): 95–104. http://dx.doi.org/10.1145/382286.382385.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

33

Gauthier, Michel. "Exception Handling in Ada-94". ACM SIGAda Ada Letters XV, nr 1 (styczeń 1995): 70–83. http://dx.doi.org/10.1145/199682.569227.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

34

Bernot, Gilles, Pascale Le Gall i Marc Aiguier. "Label algebras and exception handling". Science of Computer Programming 23, nr 2-3 (grudzień 1994): 227–86. http://dx.doi.org/10.1016/0167-6423(94)00021-2.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

35

Liu, Leo Y., i R. K. Shyamasundar. "Exception handling in RT-CDL". Computer Languages 15, nr 3 (styczeń 1990): 177–92. http://dx.doi.org/10.1016/0096-0551(90)90010-m.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

36

Drew, Steven J., i K. John Gough. "Exception handling: Expecting the unexpected". Computer Languages 20, nr 2 (maj 1994): 69–87. http://dx.doi.org/10.1016/0096-0551(94)90015-9.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

37

Ding, Yue Hua, i Ri Hua Xiang. "Exception Throwing Analysis and Exception Handling Method for BPEL". Advanced Materials Research 1030-1032 (wrzesień 2014): 1905–8. http://dx.doi.org/10.4028/www.scientific.net/amr.1030-1032.1905.

Pełny tekst źródła

Streszczenie:

Business developer needs to develop fault-tolerant process, but fault-tolerant process development based on exception handling mechanism provided by BPEL costs much time and is easy to make mistake. We analyze application exception throw chain theory of service-oriented system. Exception throwing of BPEL process is broadcasted among component layer, service layer and process layer. We also propose an application exception handling method for BPEL by using EHPDL-P. EHPDL-P can separate normal business logic and exception business logic, and thus it can enhance BPEL fault-tolerance ability.

Style APA, Harvard, Vancouver, ISO itp.

38

Wang, Yilong, Daofu Gong, Bin Lu, Fei Xiang i Fenlin Liu. "Exception Handling-Based Dynamic Software Watermarking". IEEE Access 6 (2018): 8882–89. http://dx.doi.org/10.1109/access.2018.2810058.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

39

Kechagia, Maria. "Exception handling evaluation of large APIs". XRDS: Crossroads, The ACM Magazine for Students 21, nr 3 (27.03.2015): 16–17. http://dx.doi.org/10.1145/2745392.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

40

Burnett, M., A. Agrawal i P. van Zee. "Exception handling in the spreadsheet paradigm". IEEE Transactions on Software Engineering 26, nr 10 (2000): 923–42. http://dx.doi.org/10.1109/32.879817.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

41

Hagen, C., i G. Alonso. "Exception handling in workflow management systems". IEEE Transactions on Software Engineering 26, nr 10 (2000): 943–58. http://dx.doi.org/10.1109/32.879818.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

42

Demmel, J. W., i Xiaoye Li. "Faster numerical algorithms via exception handling". IEEE Transactions on Computers 43, nr 8 (1994): 983–92. http://dx.doi.org/10.1109/12.295860.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

43

Dony, Christophe, Jan Purchase i Russel Winder. "Exception handling in object-oriented systems". ACM SIGPLAN OOPS Messenger 3, nr 2 (kwiecień 1992): 17–30. http://dx.doi.org/10.1145/130943.130948.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

44

Lerner, B. S., S. Christov, L. J. Osterweil, R. Bendraou, U. Kannengiesser i A. Wise. "Exception Handling Patterns for Process Modeling". IEEE Transactions on Software Engineering 36, nr 2 (marzec 2010): 162–83. http://dx.doi.org/10.1109/tse.2010.1.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

45

Yemini, Shaula, i Daniel M. Berry. "A modular verifiable exception handling mechanism". ACM Transactions on Programming Languages and Systems 7, nr 2 (kwiecień 1985): 214–43. http://dx.doi.org/10.1145/3318.3320.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

46

Huang, Daniel T., i Ronald A. Olsson. "An exception handling mechanism for SR". Computer Languages 15, nr 3 (styczeń 1990): 163–76. http://dx.doi.org/10.1016/0096-0551(90)90009-e.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

47

Coelho, Roberta, Lucas Almeida, Georgios Gousios, Arie van Deursen i Christoph Treude. "Exception handling bug hazards in Android". Empirical Software Engineering 22, nr 3 (13.08.2016): 1264–304. http://dx.doi.org/10.1007/s10664-016-9443-7.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

48

Wang, Quan Yu, Shi Ying, Xiang Yang Jia, Guo Bin Lv i Yun Shuai. "SOADL-EH: Service-Oriented Architecture Description Language Supporting Exception Handling". Advanced Materials Research 433-440 (styczeń 2012): 3500–3509. http://dx.doi.org/10.4028/www.scientific.net/amr.433-440.3500.

Pełny tekst źródła

Streszczenie:

To solve the problem of the construction of service-oriented software architecture with fault tolerant, the paper proposes SOADL-EH, a novel service-oriented software architecture description language supporting exception handling. With the capability of modeling normal SOA and the provision of software architecture elements such as exception handling services, exception handling connectors and exception handling configurations, etc., this language can separate clearly the exception handling logic from the normal business logic of the service-oriented software architecture layer, which makes up the shortage in exception handling capability of the existing Architecture description language.

Style APA, Harvard, Vancouver, ISO itp.

49

Shang, Zong Min. "An Exception Handling Approach for Service-Based Business Processes". Advanced Materials Research 605-607 (grudzień 2012): 1700–1704. http://dx.doi.org/10.4028/www.scientific.net/amr.605-607.1700.

Pełny tekst źródła

Streszczenie:

This paper proposes an exception handling mechanism for running reliable service-based business processes. With Smart Process-based Application Model that we have proposed, a smart process is generated automatically according to the execution of composite web services to better meet user’s individual requirements. However, the loosely-coupled nature of the smart process introduces more exceptions during its running. This paper will mainly focus on the failures of a smart process, and give an approach to handle exceptions. Based on Execution Transition Diagram(ETD) and several execution states we define in this paper, exceptions can be handled automatically by selecting rational transitions in the ETD during the execution of a smart process.

Style APA, Harvard, Vancouver, ISO itp.

50

Jiang, Xiao Peng, Run Xiao Wang, Tao Li, Zhi Qing Luo i Dong Bo Wang. "Reconfiguration Methods for Exception Handling in Reconfigurable Manufacturing Systems". Materials Science Forum 532-533 (grudzień 2006): 628–31. http://dx.doi.org/10.4028/www.scientific.net/msf.532-533.628.

Pełny tekst źródła

Streszczenie:

Reconfigurable manufacturing systems (RMS) offer capabilities for quick adjustment of production capacity and functionality in response to sudden changes in market conditions. Both at the system and at the cell level exception events occur dynamically and unpredictably during the production process. These exceptions interrupt the production process by causing errors in the schedule plan. Error/ exception handling is the policy how to deal with errors caused by the occurrence of out-of-ordinary events. Author explores the new strategies to handling error events and proposes an intelligent control structure for real-time error handling, and illustrates the reconfiguration ability is the new crucial technological factor enabling new strategies to handle out-of-ordinary events of the production process.

Style APA, Harvard, Vancouver, ISO itp.

Artykuły w czasopismach na temat „Exception Handling”

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych