SOADL-EH: Service-Oriented Architecture Description Language Supporting Exception Handling

Abstract:

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.

• Periodical: Advanced Materials Research (Volumes 433-440)
• Pages: 3500-3509
• DOI: https://doi.org/10.4028/www.scientific.net/AMR.433-440.3500
• Online since: January 2012
• Authors: Quan Yu Wang, Shi Ying, Xiang Yang Jia, Guo Bin Lv, Yun Shuai
• Keywords: Architecture Description Language (ADL), Exception Handling, Service-Oriented Architecture (SOA)

References

[1] M.P. Papazoglou, P. Traverso, S. Dustdar, F. Leymann, Service-Oriented Computing: State of the Art and Research Challenges, IEEE Computer, 2007, 40(11), pp.38-45.

DOI: 10.1109/mc.2007.400

[2] F. Tartanoglu, V. Issarny, N. Levy, A. Romano-vsky, Dependability in the Web service architecture, In Architecting Dependable Systems, LNCS 2677, pp.89-108. SpringerVerlag, (2003).

DOI: 10.1007/3-540-45177-3_4

[3] N Medividovic, RN Taylor, A classification and comparison frame-Work for software architecture description language, IEEE Transactions on Software Engineering, 2000, 26(1), pp.77-93.

[4] W3C. Web Services Architecture [EB/OL], http: /www. w3. org/TR/ws-arch/, (2004).

[5] M. N Milad, I. Krichen, M. Jmaiel, An xADL extension for manage-ment dynamic deployment in distributed service oriented architectures, In Proceedings of the Third IPM International Conference on Fundamentals of Software Engineering, Lecture Notes in Computer Science, vol. 5961. a) Spring, Berlin (2009).

DOI: 10.1007/978-3-642-11623-0_27

[6] S.L. Marcos, Z. Qayyum , Representing service-oriented architectural models using pi-adl, ECSA 2008, LNCS 5292, pp.273-280.

[7] YANG Xin, CHEN Jun-Liang, An Architecture Description Language for Web Services Component System, Journal of Software. 2006, 17(005), pp, 1182-1194.

[8] Rao Yuan, Feng-Boqing and Li-Zunchao, ALBC4WS: A Dynamic Service Composition Framework Based on the software Architecture Lifecycle, Journal of Computer Research and Development. 2005, 42(02), p.2063-(2069).

DOI: 10.1360/crad20051205

[9] Xiangyang Jia, Shi Ying et al, A New Architecture Description Langu-age for Service-Oriented Architecture, In proceeding of Sixth Internation-Conference on Grid and Cooperative Computing(GCC 2007). 16-18 Aug, 2007, pp.96-103.

DOI: 10.1109/gcc.2007.18

[10] JIANG-Zheyuan, HAN-Jianghong , WANG Zhao, Service-oriented Software Architecture Description and Construction Using XML, Journal of Chinese Computer Systems, 2008, 29(8), pp.1437-1444.

[11] F.F. Castor, P.H. Brito, C.M. Rubira, Specification of exception flow in software architecture, The Journal of System & Software. 2006, 79(10), pp.1397-1418.

DOI: 10.1016/j.jss.2006.02.060

[12] P. Feiler, A. Rugina, Dependability Modeling with the Architecture Analysis & Design Language(AADL), Technical report, CMU-SEI-2007-TN-043, 2007, pp.1-76.

[13] P. A de G. Castro, C. Rubira and R. de Lemos, A Fault-Tolerant Software Architecture for Component-Based Systems, Architecting Dependable Systems, LNCS 2677, Spring, 2003, pp.129-149.

DOI: 10.1007/3-540-45177-3_6

[14] R. de Lemos, P.A.G. de Castro, C.M. Rubira, A fault-tolerant architectural approach for dependable systems, IEEE Software, Vol. 23 No. 2, 2006, pp.80-87.

DOI: 10.1109/ms.2006.35

[15] F. Oquendo, π-ADL: An Architecture Description Language based on the Higher-Order Typed π-Calculus for Specifying Dynamic and Mobile software Architectures, Software Engineering notes, 2004, 29(3), pp.1-14.

DOI: 10.1145/986710.986728