Journal of Computing Science and Engineering

Korean Institute of Information Scientists and Engineers (한국정보과학회)
권호 표지
DOI QR코드

DOI QR Code

The Service-Oriented Metaphor Deciphered

  • Received : 2010.11.01
  • Accepted : 2010.12.13
  • Published : 2010.12.31
Download PDF
⟨ Previous Next ⟩

Abstract

In this article we review the metaphor of service-oriented architecture for enterprise computing. In typical definitions service-oriented architecture appears as a single message and a consistent roadmap for building flexible software system landscapes. But it is not. Different communities have elaborated different SOA (service-oriented architecture) concepts to address different problem areas, i.e., enterprise application integration, business-to-business, business process management, and software productizing. If software architects and software managers are aware of these strands of SOA when talking about SOA in their projects they can avoid misunderstandings and detours better. This article contributes a clarification of the different strands of SOA concepts and technologies and their mutual dependencies and identifies particular SOA concepts as instances of more general software engineering principles.

Keywords

References

  1. AGRAWAL, A. 2007. WS-BPEL Extension for People (BPEL4People), version 1.0. Tech. rep., Active Endpoints, Adobe Systems, BEA Systems, IBM, Oracle, SAP. June.
  2. ATKINSON, C., BOSTAN, P., HUMMEL, O., AND STOLL, D. 2007. A Practical Approach to Web Service Discovery and Retrieval. In Proceedings of ICWS 2007 - the 5th IEEE International Conference on Web Services. IEEE Press.
  3. ATKINSON, C. AND HUMMEL, O. 2007. Supporting Agile Reuse Through Extreme Harvesting. In Proceedings of XP 2007 - the 8th International Conference on Agile Processes in Software Engineering and Extreme Programming, Lecture Notes in Computer Science 4536. Springer.
  4. BECK, K. 2000. Extreme Programming Explained - Embrace Change. Addison-Wesley.
  5. BEISIEGEL, M. 2005. Service Component Architecture - Building Systems using a Service Oriented Architecture. Tech. Rep. Joint Whitepaper, version 0.9, BEA, IBM, Interface21, IONA, Oracle, SAP, Siebel, Sybase. November.
  6. BEISIEGEL, M. 2007. ASCA Policy Framework, SCA Version 1.00. Tech. rep., BEA, Cape Clear, IBM, Interface21, IONA, Oracle, Primeton, Progress, Red Hat, Rogue Wave, SAP, Siemens, Software AG, Sun, Sybase, TIBCO. March.
  7. BERNSTEIN, P. 1996. Middleware: a Model for Distributed System Services. Communications of the ACM 39, 2 (February), 86-98.
  8. BOX, D. 2000. Simple Object Access Protocol (SOAP) 1.1 - W3C Note. Tech. rep. May.
  9. BROOKS, F. 1975. The Mythical Man-month − Essays on Software Engineering. Addison-Wesley.
  10. BROOKS, F. P. 1987. No Silver Bullet - Essence and Accidents of Software Engineering. IEEE Computer 20, 4 (April).
  11. BROWN, A. 1997. CASE in the 21st Century - Challenges Facing Existing Case Vendors. In Proceedings of STEP'97 - the 8th International Workshop on Software Technology and Enginering Practice. IEEE Press.
  12. BROWN, A., JOHNSTON, S., AND KELLY, K. 2002. Using Service-Oriented Architecture and Component-Based Development to Build Web Service Applications. Tech. rep., Santa Clara, CA: Rational Software Corporation.
  13. BUSINESS PROCESS PROJECT TEAM. 2001. ebXML Business Process Specification Schema, Version 1.01. Tech. rep., UN/CEFACT, OASIS.
  14. CHOW, L., MEDLEY, C., AND RICHARDSON, C. 2007. BPM and Service-Oriented Archtiecture Teamed Togehter: A Pathway to Success for an Agile Government. In 2007 BPM and Workflow Handbook, L. Fischer, Ed. Workflow Management Coalition, 33-54.
  15. COLAN, M. 2004. Service-Oriented Architecture expands the Vision of Web Services -Characteristics of Service-Oriented Architecture. Tech. rep., IBM Corporation. April.
  16. COMPUTER, C. AND AGENCY, T. 2000. IT Infrastructure Library - Service Support. Tech. rep., Renouf.
  17. DEREMER, F. AND KRON, H. 1975. Programming-in-the-Large Versus Programming-in-the-Small. In Proceedings of the International Conference on Reliable Software. ACM Press, 114-121.
  18. DERLER, P. AND WEINREICH, R. 2006. Models and Tools for SOA Governance. In Proceedings of TEAA 2006 - International Conference on Trends in Enterprise Application Architecture, Lecture Notes in Computer Science 4473, D. Draheim and G. Weber, Ed. Springer.
  19. DRAHEIM, D. 2003. A CSCW and Project Management Tool for Learning Software Engineering. In Proceedings of FIE 2003 - Frontiers in Education: Engineering as a Human Endeavor. IEEE Press.
  20. DRAHEIM, D. 2006. Learning Software Engineering with EASE. In Informatics and the Digital Society, Tom J. van Weert and Robert K. Munro, Ed. Kluwer Academic Publishers. 2003.
  21. DRAHEIM, D. AND KOPTEZKY, T. 2007. Workflow Management and Service-Oriented Architecture. In Proceedings of SEKE 2007 - The 19th International Conference on Software Engineering and Knowledge Engineering.
  22. EMMELHAINZ, M. 1993. EDI: A Total Management Guide. Van Nostrand Reinhold.
  23. Erl, T. 2007. SOA: Principles of Service Design. Prentice Hall.
  24. EVDEMON, J. AND JORDAN, D. 2007. Web Services Business Process Execution Language Version 2.0. Tech. Rep. OASIS standard wsbpel-v2.0-OS, OASIS. April.
  25. GAMMA, E. 1995. Design Patterns - Elements of Reusable Object-Oriented Software. Addison-Wesley.
  26. GARTNER GROUP. 2004. The Gartner Glossary of Information Technology Acronyms and Terms. Tech. rep., Gartner Group.
  27. GILLETTE, W. 1996. Managing Megaprojects: a Focused Approach. Software 13, 4.
  28. GUTA, G., SCHREINER, W., AND DRAHEIM, D. 2009. A Lightweight MDSD Process Applied in Small Projects. In Proceedings of SEAA 2009 - the 35th Euromicro Conference on Software Engineering and Advanced Applications. IEEE Computer Society.
  29. HOLLEY, K., PALISTRANT, J., AND GRAHAM, S. 2006. Effective SOA Governance. Tech. Rep. IBM White Paper, IBM Corporation. March.
  30. IBM CORPORATION. 2007. Smart SOA: Best Practices for Agile Innovation and Optimization. Tech. Rep. IBM White Paper, IBM Corporation. November.
  31. INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. 1988. International Standard ISO 9735. Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) - Application Level Syntax Rules. Tech. rep., ISO.
  32. KENNEY, L. AND PLUMMER, D. 2008. Magic Quadrant for Integrated SOA Governance Sets. Tech. Rep. Gartner RAS Core Research Note G00153858, Gartner Group. June.
  33. KLOPPMANN, M., KOENIG, D., LEYMANN, F., PFAU, G., RICKAYZEN, A., RIEGEN, C., SCHMIDT, P., AND TRICKOVIC, I. 2005. WS-BPEL Extension for People - BPEL4People. Tech. rep., IBM, SAP.
  34. LEWIS, G., MORRIS, E., O'BRIEN, L., SMITH, D., AND WRAGE, L. 2005. SMART: The Service- Oriented Migration and Reuse Technique. Tech. Rep. Technical Note CMU/SEI-2005-TN-029, SEI - Software Engineering Institute, Carnegie Mellon University. September.
  35. LEYMANN, F., ROLLER, D., AND SCHMIDT, M. 2002. Web Services and Business Process Management. IBM Systems Journal 41.
  36. LHEUREUX, B. AND MALINVERNO, P. 2008. Magic Quadrant for B2B Gateway Providers. Tech. Rep. Gartner RAS Core Research Note G00157460, Gartner Group. June.
  37. MACKENZIE, C., LASKEY, K., MCCABE, F., BROWN, P., METZ, R., AND HAMILTON, B. 2006. Reference Model for Service Oriented Architecture 1.0, Committee Specification 1. Tech. Rep. document identifier soa-rm-cs, OASIS Open. August.
  38. MAHMOUD, Q. 2005. Service-Oriented Architecture (SOA) and Web Services: The Road to Enterprise Application Integration (EAI). Tech. rep., Sun Microsystems. April.
  39. MCCOY, D. AND NATIS, Y. 2003. Service-Oriented Architecture: Mainstream Straight Ahaed. Tech. Rep. Gartner Research ID Number LE-19-7652, Gartner Group. April.
  40. MCNAMARA AND CHISHTI, M. 2006. Business Integration Using State-Based Asynchronous Services. In 2006 BPM and Workflow Handbook, L. Fischer, Ed. Future Strategies.
  41. NATIS, Y. 2003. Service-Oriented Architecture Scenario. Tech. Rep. Gartner Research ID Number AV-19-6751, Gartner Group. April.
  42. OF GOVERNMENT COMMERCE, O. 2002. ICT Infrastructure Management. Tech. rep., Bernan.
  43. ROBINSON, I. 2007. ACID Transaction Policy in SCA, SCA Version 1.00. Tech. rep., BEA, Cape Clear, IBM, Interface21, IONA, Oracle, Primeton, Progress, Red Hat, Rogue Wave, SAP, Siemens, Software AG, Sun, Sybase, TIBCO. December.
  44. SCHULTE, R. 1996. Service Oriented Architectures, Part 2. Tech. Rep. Gartner Research ID Number SPA-401-069, Gartner Group.
  45. SCHULTE, R. AND NATIS, Y. 1996. Service Oriented Architectures, Part 1. Tech. Rep. Gartner Research ID Number SPA-401-068, Gartner Group.
  46. TEN-HOVE, R. AND WALKER, P. 2005. Java Business Integration 1.0 Final Release. Tech. Rep. Specification JSR 208, Sun Microsystems. August.
  47. THATTE, S. 2003. Specification: Business Process Execution Language for Web Services Version 1.1. Tech. rep. May.
  48. UN/CEFACT. 2006. UN/CEFACT${^{\circ}}$Os Modeling Methodology (UMM): UMM Meta Model - Foundation Module Version 1.0, Technical Specification. Tech. rep., UN/CEFACT.
  49. WALDO, J. 1999. The Jini Architecture for Network-Centric Computing. Communications of the ACM 42, 7.
  50. WEAVER, R. 2005. The Business Value of the Service Component Architecture (SCA) and Service Data Objects (SDO). Tech. Rep. Business Value White Paper, version 0.9., International Business Machines. November.
  51. ZIEBERMAYR, T. 2010. A Framework for Enhanced Service Reuse in an industrial SOA-Context -Dissertation. Institute for Application Oriented Knowledge Processing, Johannes-Kepler-University Linz.
  52. ZIEBERMAYR, T., WEINREICH, R., AND DRAHEIM, D. 2007. A Versioning Model for Enterprise Services. In Proceedings of WAMIS 2007 - 3rd International Workshop on Web and Mobile Information Services. IEEE Press.

Cited by

  1. A sharing-oriented design strategy for networked knowledge organization systems vol.17, pp.1, 2016, https://doi.org/10.1007/s00799-015-0164-0