Supporting a service-oriented architecture

ABSTRACT

Service-oriented Architectures (SOA) have become increasingly popular as a way to support the business processes of an organization.[1] A Service-Oriented Architecture approach to system design is one where application design and development are done with the goal of producing usable services. This approach allows for the integration of applications as reusable system services. The services must have platform independent specifications which abstract the underlying complexity of the service, are loosely coupled, and, perhaps most importantly, are reusable. This paper gives an in depth overview of SOA concepts, and will briefly introduce current Enterprise Architectures, such as the Department of Defense Architecture Framework (DoDAF), Ministry of Defense Architecture Framework (MoDAF), and The Open Group Architecture Framework (TOGAF), and what is being done to address the current need for SOA.

References

1. Datz, T. 2004. What You Need to Know About Service-Oriented Architectures. http://www.cio.com/article/32060/What_You_Need_to_Know_About_Service_Oriented_Archit ecture, November 2007.
2. M. Endrei, J Ang, A Arsanjani, S. Chua, P. Comte, P. Krogdahl, M. Luo, T. Newling. 2004. Patterns: Service-Oriented Architectures and Web Services. IBM RedBooks, IBM 2004, http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstr acts/sg246303.html?Open, November 2007
3. Organization for the Advancement of Structured Information Standards (OASIS). 2006. Service Oriented Architecture (SOA) Reference Model Public Review Draft 1.0 (Feb), http://www.oasis-open.org/committees/download.php/16587/wd-soa-cd1ED.pdf, November 2007
4. Open Management Group. SOA SIG. http://SOA.omg.org, November 2007
5. Thanh, D. v. and Jorstad, I. 2005. A Service-oriented Architecture Framework for Mobile Services. In the Proceedings of the Advanced Industrial Conference on Telecommunications/Service Assurance with Partial and Intermittent Resources Conference/E-Learning on Telecommunications Workshop. IEEE, Piscataway, N.J., 65--70.
6. Dandashi, F. and Ang, H. W. 2006. Tailoring DoDAF For Service Oriented Arhitectures: A Recommended Guide. Military Communications Conference (Oct. 23--45). IEEE, Piscataway, N.J., 1--8.
7. Josuttis, M. N.; 2007. SOA In Practice The Art of Distributed Syste, Design. O'Reilly Media, Inc., Sebastopol, CA.
8. Lewis, G. A., Morris, E., Simanta, S. and Wrage, L. 2007. Common Misconceptions About Service-Oriented Architectures. Sixth International IEEE Conference on Commercial-off-the-shelf (COTS)-Based Software Systems (Feb. 26 -- Mar. 2). IEEE, Piscataway, N. J., 123--130.
9. Stal, M. 2006. Using Architectural Patterns and Blueprints for Service-Oriented Architecture. IEEE Software 23, no. 2 (Mar. -- Apr.): 54~61.
10. Liegel, P. 2007. The strategic impact of service oriented architectures. In the Proceedingsof the 14^th Annual IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (Mar. 26--29). IEEE, Piscataway, N.J., 475--484.
11. Hinton, H., Hondo, M. and Hutchison, B. 2006. Security Patterns within a Service-Oriented Architecture. http://searchwebservices.techtarget.com/search WebServices/downloads/SecuritySOA_(2).pdf, November 2007.
12. Cotroneo, D., Graziano, A. and Russo, S. 2004. Security Requirements in Service Oriented Architectures for Ubiquitous Computing. In the Proceedings of the 2^nd workshop on Middlware for pervasive and ad-hoc computing (Toronto, Ontario, Canada, Oct.). ACM Press, New York, N.Y., 172--177.
13. Durbeck, S., Schillinger, R. and Kolter, J. 2007. Security Requirements for a Semantic Service-oriented Architecture. Second International Conference on Availability, Reliability, and Security (Vienna, Apr. 10--13). IEEE, Piscataway, N.J., 366--373.
14. DoD Architecture Framework Working Group. 2004. DoD Architecture Framework Version 1.0 -- Volume I: Definitions and Guidelines, http://www.tricare.mil/jmis/download/DoDArch itectureFrameworkVersion1Feb2004.pdf, November 2007
15. Chen, P., Han, J. and Tang, A. 2004. A Comparative Analysis of Architecture Frameworks. In the Proceedings of the 11^th Asia-Pacific Software Engineering Conference (Nov. 30 - Dec. 3). IEEE, Piscataway, N.J., 640--647.
16. MODAF. http://www.hi-q.co.uk/modaf_togaf_mapping/, November 2007
17. MODAF. http://www.modaf.org.uk/3Modelling/56/how-does-modaf-relate-to-dodaf, November 2007
18. MODAF. MODAF AND SERVICE ORIENTED ARCHITECTURE. http://www.modaf.org.uk/files/SOA-article2.doc, November 2007
19. Leist, S. and Zellner, G. 2006. Evaluation of Current Architecture Frameworks. In Proceedings of the 2006 ACM symposium on Applied computing (Dijon, France). ACM, New York, N.Y., 1546--1553.
20. http://www.opengroup.org/projects/soatogaf/, November 2007
21. TOGAF. http://www.opengroup.org/projects/soa/uploads/40/11475/Practical_Guide_to_SOA_Project_v1.2.doc, November 2007
22. Anand, S., Erradi, A. and Kulkarni, N. 2006. SOAF: An Architectural Framework for Service Definition and Realization. IEEE International Conference on Services Computing (Sept.). IEEE, Piscataway, N.J., 151--158.

• Software and its engineering

  • Software organization and properties

    • Software system structures