Introduction

Abstract

Services, as perceived in the Service-Oriented Architecture (SOA), “are intrinsically un-associated units of functionality, which have no calls to each other embedded in them.” (Wikipedia 2008). They typically implement functionalities most humans would recognize as a Service, “such as filling out an online application for an account, viewing an online bank statement, or placing an online booking or airline ticket order. Instead of Services embedding calls to each other in their source code, protocols are defined which describe how one or more Services can talk to each other.” (Wikipedia 2008). This architecture (SOA) then relies on a business process expert to link and sequence services, in a process known as “orchestration”, to meet a new or existing business requirement.