Architecting Service-Oriented Systems

Abstract : Service orientation is an approach to software systems development that has become a popular way to implement distributed, loosely coupled systems, because it offers such features as standardization, platform independence, well-defined interfaces, and tool support that enables legacy system integration. From a quality attribute point of view, the primary drivers for service orientation adoption are interoperability and modifiability. However, a common misconception is that an architecture that uses a service-oriented approach can achieve these qualities by simply putting together a set of vendor products that provide an infrastructure and then using this infrastructure to expose a set of reusable services to build systems. In reality, there are many architectural decisions that need to be made. An architectural decision that promotes interoperability or modifiability can negatively impact other qualities, such as availability, reliability, security and performance. The goal of this report is to present general guidelines for architecting service-oriented systems, how common service-oriented system components support these principles, and the effect that these principles and their implementation have on system quality attributes.

[1]  Bobby Woolf,et al.  Enterprise Integration Patterns , 2003 .

[2]  Ali Arsanjani,et al.  Service-Oriented Modeling and Architecture for Realization of an SOA , 2006, 2006 IEEE International Conference on Services Computing (SCC'06).

[3]  Grace A. Lewis,et al.  A Process for Context-Based Technology Evaluation , 2005 .

[4]  Activité ad‐hoc Types de tâches.  Introduction to BPMN , 2004 .

[5]  Soumya Simanta,et al.  Why Standards Are Not Enough to Guarantee End-to-End Interoperability , 2008, Seventh International Conference on Composition-Based Software Systems (ICCBSS 2008).

[6]  Ninghui Li,et al.  Denial of service attacks and defenses in decentralized trust management , 2006, 2006 Securecomm and Workshops.

[7]  Thomas Erl,et al.  SOA Principles of Service Design , 2007 .

[8]  Peter Sommerlad,et al.  Pattern-Oriented Software Architecture Volume 1: A System of Patterns , 1996 .

[9]  William Stafford.  For Robert I. Stafford , 1975 .

[10]  Soumya Simanta,et al.  Common Misconceptions about Service-Oriented Architecture , 2007, 2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07).

[11]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[12]  David A Chappell,et al.  Enterprise Service Bus , 2004 .

[13]  S. Mason.  Purdue University , 2005 .

[14]  Sudipto Ghosh,et al.  Testing component-based distributed applications , 2000 .

[15]  S. T. Buckland,et al.  An Introduction to the Bootstrap. , 1994 .

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

[17]  Beverly D. McIntyre,et al.  North America and Europe (NAE) report , 2009 .

[18]  M. Pursley.  Report Documentation Page Form Approved Omb No. 0704-0188 Please Do Not Return Your Form to the above Address. 1. Report Date (dd-mm-yyyy) Final Technical Report Receiver Statistics for Cognitive Radios in Dynamic Spectrum Access Networks Onr , 2007 .

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

[20]  Matjaz B. Juric,et al.  Java RMI, RMI tunneling and Web services comparison and performance analysis , 2004, SIGP.

[21]  Soumya Simanta,et al.  SMART: Analyzing the Reuse Potential of Legacy Components in a Service-Oriented Architecture Environment , 2007 .

[22]  Soumya Simanta,et al.  A Scenario-Based Technique for Developing SOA Technical Governance , 2009 .