A framework for analyzing exception flow in software architectures

We present Aereal, a framework for analyzing exception flow in architecture descriptions. Aereal works as a customizable architectural-level exception handling system that can be further constrained or have some of its rules relaxed. 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. As enabling technologies. Aereal uses Alloy, a first-order relational language, ACME, an interchange language for architecture description, and their associated tool sets.

[1]  Bradley R. Schmerl,et al.  AcmeStudio: supporting style-centered architecture development , 2004, Proceedings. 26th International Conference on Software Engineering.

[2]  Mary Shaw,et al.  Software architecture - perspectives on an emerging discipline , 1996 .

[3]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[4]  Wang Yi,et al.  Uppaal in a nutshell , 1997, International Journal on Software Tools for Technology Transfer.

[5]  Martin P. Robillard,et al.  Static analysis to support the evolution of exception structure in object-oriented systems , 2003, TSEM.

[6]  Richard N. Taylor,et al.  A framework for classifying and comparing architecture description languages , 1997, ESEC '97/FSE-5.

[7]  Avelino Francisco Zorzo,et al.  Structuring integrated Web applications for fault tolerance , 2003, The Sixth International Symposium on Autonomous Decentralized Systems, 2003. ISADS 2003..

[8]  Brian Randell,et al.  Error recovery in asynchronous systems , 1986, IEEE Transactions on Software Engineering.

[9]  Cecília M. F. Rubira,et al.  An Architectural-Level Exception-Handling System for Component-Based Applications , 2003, LADC.

[10]  C. A. R. Hoare,et al.  Communicating sequential processes , 1978, CACM.

[11]  David Garlan,et al.  Architecture-Based Performance Analysis , 1998 .

[12]  David S. Rosenblum,et al.  Exploiting ADLs to specify architectural styles induced by middleware infrastructures , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[13]  Daniel Jackson,et al.  Alloy: a lightweight object modelling notation , 2002, TSEM.

[14]  Cecilia Mary Fischer Rubira,et al.  An Idealized Fault-Tolerant Architectural Component , 2002 .

[15]  Valérie Issarny,et al.  Architecture-based exception handling , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[16]  Paul Clements,et al.  Software Architecture: An Executive Overview , 1996 .

[17]  Jean-Raymond Abrial,et al.  The B-book - assigning programs to meanings , 1996 .

[18]  Michael J. Butler,et al.  An Approach to Combining B and Alloy , 2002, ZB.

[19]  Walter Mann,et al.  Correction to "Specification and Analysis of System Architecture Using Rapide" , 1995, IEEE Trans. Software Eng..

[20]  David Garlan,et al.  Acme: architectural description of component-based systems , 2000 .

[21]  Cecilia Mary Fischer Rubira,et al.  Exception handling in the development of dependable component-based systems , 2005 .

[22]  Nenad Medvidovic,et al.  Composing architectural styles from architectural primitives , 2003, ESEC/FSE-11.

[23]  Richard N. Taylor,et al.  A Component- and Message-Based Architectural Style for GUI Software , 1995, 1995 17th International Conference on Software Engineering.

[24]  David Garlan,et al.  A formal basis for architectural connection , 1997, TSEM.