dc.creatorCastor, F
dc.creatorBrito, PHDS
dc.creatorRubira, CMF
dc.date2006
dc.dateOCT
dc.date2014-11-16T20:42:05Z
dc.date2015-11-26T16:25:12Z
dc.date2014-11-16T20:42:05Z
dc.date2015-11-26T16:25:12Z
dc.date.accessioned2018-03-28T23:06:00Z
dc.date.available2018-03-28T23:06:00Z
dc.identifierJournal Of Systems And Software. Elsevier Science Inc, v. 79, n. 10, n. 1397, n. 1418, 2006.
dc.identifier0164-1212
dc.identifierWOS:000241173200005
dc.identifier10.1016/j.jss.2006.02.060
dc.identifierhttp://www.repositorio.unicamp.br/jspui/handle/REPOSIP/72070
dc.identifierhttp://www.repositorio.unicamp.br/handle/REPOSIP/72070
dc.identifierhttp://repositorio.unicamp.br/jspui/handle/REPOSIP/72070
dc.identifier.urihttp://repositorioslatinoamericanos.uchile.cl/handle/2250/1268578
dc.descriptionIn recent years, various approaches combining software architectures and exception handling have been proposed for increasing the dependability of software systems. This conforms with the idea supported by some authors that addressing exception handling-related issues since early phases of software development may improve the overall dependability of a system. By systematically designing the mechanism responsible for rendering a system reliable, developers increase the probability of the system being able to avoid catastrophic failures at runtime. This paper addresses the problem of describing how exceptions flow amongst architectural elements. In critical systems where rollback-based mechanisms might not be available, such as systems that interact with mechanical devices, exception handling is an important means for recovering from errors in a forward-based manner. We present a framework, named Aereal, that supports the description and analysis of exceptions that flow between architectural components. Since different architectural styles have different policies for exception flow, Aereal makes it possible to specify rules on how exceptions flow in a given style and to check for violations of these rules. We use a financial application and a control system as case studies to validate the proposed approach. (C) 2006 Published by Elsevier Inc.
dc.description79
dc.description10
dc.description1397
dc.description1418
dc.languageen
dc.publisherElsevier Science Inc
dc.publisherNew York
dc.publisherEUA
dc.relationJournal Of Systems And Software
dc.relationJ. Syst. Softw.
dc.rightsfechado
dc.rightshttp://www.elsevier.com/about/open-access/open-access-policies/article-posting-policy
dc.sourceWeb of Science
dc.subjectexception handling
dc.subjectsoftware architecture
dc.subjectarchitecture description languages
dc.subjectverification
dc.subjectalloy
dc.subjectStatic Analysis
dc.subjectSystems
dc.subjectSupport
dc.subjectTime
dc.titleSpecification of exception flow in software architectures
dc.typeArtículos de revistas


Este ítem pertenece a la siguiente institución