SOA decision making - what do we need to know

The SOA decision making process addresses specific concerns, which requires (its own) specific information. Currently, SOA design decisions are often documented (if at all) using generic architectural design decision models. The information that is specifically relevant to SOA design decisions remains hidden in the description of the existing entities of architectural decision models. As a result, this information could be overlooked during the decision making process and result in unsound decisions. In this paper, we highlight a set of information items that aids SOA decision making.

[1]  Philippe Kruchten,et al.  Building up and Exploiting Architectural Knowledge , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[2]  Mike P. Papazoglou,et al.  Service-oriented computing: concepts, characteristics and directions , 2003, Proceedings of the Fourth International Conference on Web Information Systems Engineering, 2003. WISE 2003..

[3]  Thomas Erl,et al.  SOA Design Patterns , 2008 .

[4]  Jan Bosch,et al.  Software Architecture as a Set of Architectural Design Decisions , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[5]  Frank Leymann,et al.  Reusable Architectural Decision Models for Enterprise Application Development , 2007, QoSA.

[6]  Giovanni Cantone,et al.  Design decision rationale: experiences and steps ahead towards systematic use , 2006, SOEN.

[7]  Olaf Zimmermann,et al.  Second generation web services-oriented architecture in production in the finance industry , 2004, OOPSLA '04.

[8]  Frank Leymann,et al.  Architectural Decisions and Patterns for Transactional Workflows in SOA , 2007, ICSOC.

[9]  Philippe Kruchten,et al.  Architectural knowledge and rationale: issues, trends, challenges , 2007, SOEN.

[10]  Jeff Tyree,et al.  Architecture decisions: demystifying architecture , 2005, IEEE Software.

[11]  Nikola Milanovic.  Service Engineering Design Patterns , 2006, 2006 Second IEEE International Symposium on Service-Oriented System Engineering (SOSE'06).