FosterEvolution

You are here: Home » SOA Article
Thursday, 23 Feb 2012

Service-Oriented Architectures (SOA)

E-mail Print PDF

The following describes our opinion and philosophy of what SOA really means to progressive software engineering and systems development...

 

SOA is really Service-Orientation

 

Fundamentally, a Service-Oriented Architecture (SOA) can be described as a system architecture which adheres to the principles of some service-based architectural design rules. The design rules should cover service governance, functional re-usability and technology independence through standards-based communication protocols to support the evolution and maintenance of the service-based system. An SOA typically crosses enterprise boundaries and/or system domains. For example, it may be To illustrate some of the core concepts of service-orientation a relationship model was constructed as a Service-Oriented Model (SOM) by the W3C Services Architecture Group [1]. They describe the model as:

Service-Oriented Model (W3C)

 

"a model to explicate the relationships between an agent and the services is provides and requests".

 

The fundamental elements for service composition are service, service goal state, task and role. A service is an abstract resource that represents a capability of performing tasks, whilst it’s goal state is driven from the requirements of a some person or organization’s point of view. Furthermore, a service may take a particular role in performing a task. The model also serves to exhibit the relationships between service elements, and links these with service choreography.

Service-Oriented Model

Figure 1. The W3C Service-Oriented Topics and Relationships Model

 

Whilst the SOM model serves as a useful reference map in considering the principles of SOAs, there is clearly a gap between principle and implementation.

 

SOA is not a technical challenge

SOA is not really a technical challenge; it is promoting a common standards-based way of designing re-usable functions and integrating systems across partners that is the challenge.  Technical (IT) considerations however, are important in the instantiation of an SOA strategy (e.g. deciding whether to leverage Web Service standards in the architecture under design).

 

References

 

[1] World-Wide Web (W3C), Services Architecture Group, 2009.

Other News

  • 1
  • 2
  • 3
Prev Next

Safety, Certification and Compliance for Software Services (WESOA11)

H.Foster and G.Spanoudakis, Safety, Ceritifcation and Compliance for Software Services, in proceedings of the Workshop on Engineering Service-Oriented Applications (WESOA11), Paphos, Cyprus, December 2011. Abstract Preview The maturity of IT processes, such as software development, can be and is often certified. Current trends in the IT industry suggest that software systems in the future will be very different from their counterparts today, with an increasing adoption of the Service-Oriented Architecture (SOA) design pattern and the deployment of Software-as-a-Service (SaaS) on Cloud infrastructures. In this talk we discuss some issues surrounding engineering Software Services for Cloud infrastructures and highlight the need for enhanced control, service-level agreement...

Read more

Dynamic Creation of Monitoring Infrastructures

Dynamic Creation of Monitoring Infrastructures

In this paper we discuss an approach to the dynamic configuration of service monitoring infrastructure from SLAs. Published in Service Level Agreements for Cloud Computing, Springer, 2011.

Read more

SMaRT: A Workbench for Reporting the Monitorability of Services from SLAs

H.Foster and G.Spanoudakis, SMaRT: A Workbench for Reporting the Monitorability of Services from SLAs, 3rd International Workshop on the Principles of Engineering Service-Oriented Systems (PESOS) located at the IEEE International Conference on Software Engineering, Honolulu, HI, USA, May 2011. Abstract Preview Service Level Agreements (SLAs) for Software Services aim to clearly identify the service level commitments established between service requesters and providers. A dynamic configuration for the monitoring of these SLAs provides the opportunity for service monitor providers to offer and release monitoring infrastructures for different types of services. Whilst there has been work on automating this monitor matching and configuration, additional support may be...

Read more