Patterns for service-oriented information exchange requirements

Service-Oriented Computing (SOC) is an emerging computing paradigm that supports loosely-coupled inter-enterprise interactions. SOC interactions are predominantly specified in a procedural manner that defines message sequences intermixing implementation with business requirements. In this paper we present a set of patterns concerning requirements of information exchange between participants engaging in service-oriented interactions. The patterns aim at explicating and elaborating the business requirements driving the interaction and separating them from implementation concerns

SERVICE ORIENTED COMPUTING (SOC) DALAM SISTEM ENTERPRISE

Penggunaan Middleware telah banyak mempengaruhi proses bisnis dan kolaborasi antara pelaku bisnis dalam sistem enterprise. Keterkaitan data dari proses bisnis dalam lingkup unit yang berbeda menjadi hal fundamental untuk dapat menghasilkan informasi yang cepat dan dapat menjadi dasar pengambilan keputusan. Enterprise application integration (EAI) memadukan aplikasi dan sumber data enterprise sehingga dengan mudah mereka dapat berbagai bisnis proses dan data. Cara integrasi yang dilakukan tidak mengubah sistem dan data yang sudah adaKeberagaman platform dan framework serta banyaknya pulau pulau aplikasi maupun pulau-pulau data menjadi permasalahan baru untuk dapat mewujudkan integrasi dan kolaborasi dari masing masing aplikasi atau sistem. Peranan Middleware diarasa penting untuk dapat menjembatani hal tersebut, hal ini disebabkan customer semakin menginginkan pelayanan yang cepat, mudah dan terpercaya. Dalam suatu sistem enterprise, pertukaran dan integrasi data dari platform yang beragam mutlak diperlukan, selain itu perubahan proses bisnis maupun penambahan proses bisnis juga seringkali terjadi dalam memenangkan persaingan. Pemakaian middleware berbasis services diharapakan dapat menjadi solusi atas permasalahan tersebut.Kehadiran service oriented computing (SOC) dapat melengkapi arsitektur yang telah ada sebelumnya. Paradigma SOC ini merupakan paradigma pengembangan yang berorientasi pada service. Dengan berorientasi pada service, proses dan logic dapat dijadikan service dan subservice yang nantinya masing masing service akan saling berkomunikasi dan terintegrasi. Hal ini akan mempermudah pengembangan bila ada perubahan proses ataupun adanya penambahan proses nantinya

SERVICE ORIENTED COMPUTING (SOC) DALAM SISTEM ENTERPRISE

Penggunaan Middleware telah banyak mempengaruhi proses bisnis dan kolaborasi antara pelaku bisnis dalam sistem enterprise. Keterkaitan data dari proses bisnis dalam lingkup unit yang berbeda menjadi hal fundamental untuk dapat menghasilkan informasi yang cepat dan dapat menjadi dasar pengambilan keputusan. Enterprise application integration (EAI) memadukan aplikasi dan sumber data enterprise sehingga dengan mudah mereka dapat berbagai bisnis proses dan data. Cara integrasi yang dilakukan tidak mengubah sistem dan data yang sudah adaKeberagaman platform dan framework serta banyaknya pulau pulau aplikasi maupun pulau-pulau data menjadi permasalahan baru untuk dapat mewujudkan integrasi dan kolaborasi dari masing masing aplikasi atau sistem. Peranan Middleware diarasa penting untuk dapat menjembatani hal tersebut, hal ini disebabkan customer semakin menginginkan pelayanan yang cepat, mudah dan terpercaya. Dalam suatu sistem enterprise, pertukaran dan integrasi data dari platform yang beragam mutlak diperlukan, selain itu perubahan proses bisnis maupun penambahan proses bisnis juga seringkali terjadi dalam memenangkan persaingan. Pemakaian middleware berbasis services diharapakan dapat menjadi solusi atas permasalahan tersebut.Kehadiran service oriented computing (SOC) dapat melengkapi arsitektur yang telah ada sebelumnya. Paradigma SOC ini merupakan paradigma pengembangan yang berorientasi pada service. Dengan berorientasi pada service, proses dan logic dapat dijadikan service dan subservice yang nantinya masing masing service akan saling berkomunikasi dan terintegrasi. Hal ini akan mempermudah pengembangan bila ada perubahan proses ataupun adanya penambahan proses nantinya

Approaches Regarding Business Logic Modeling in Service Oriented Architecture

As part of the Service Oriented Computing (SOC), Service Oriented Architecture (SOA) is a technology that has been developing for almost a decade and during this time there have been published many studies, papers and surveys that are referring to the advantages of projects using it. In this article we discuss some ways of using SOA in the business environment, as a result of the need to reengineer the internal business processes with the scope of moving forward towards providing and using standardized services and achieving enterprise interoperability.Business Rules, Business Processes, SOA, BPM, BRM, Semantic Web, Semantic Interoperability

A graph semantics for a variant of the ambient calculus more adequate for modeling SOC

In this paper we present a graph semantics of a variant of the well known ambient calculus. The main change of our variant is to extract the mobility commands of the original calculus from the ambient topology. Similar to a previous work of ours, we prove that our encoding have good properties. We strongly believe that this variant would allow us to integrate our graph semantics of our mobile calculus with previous work of us in service oriented computing (SOC). Basically, our work on SOC develops a new graph transformation system which we call temporal symbolic graphs. This new graph formalism is used to give semantics to a design language for SOC developed in an european project, but it could also be used in connection with other approaches for modeling or specifying service systems.Postprint (published version

Forum Session at the First International Conference on Service Oriented Computing (ICSOC03)

The First International Conference on Service Oriented Computing (ICSOC) was held in Trento, December 15-18, 2003. The focus of the conference ---Service Oriented Computing (SOC)--- is the new emerging paradigm for distributed computing and e-business processing that has evolved from object-oriented and component computing to enable building agile networks of collaborating business applications distributed within and across organizational boundaries. Of the 181 papers submitted to the ICSOC conference, 10 were selected for the forum session which took place on December the 16th, 2003. The papers were chosen based on their technical quality, originality, relevance to SOC and for their nature of being best suited for a poster presentation or a demonstration. This technical report contains the 10 papers presented during the forum session at the ICSOC conference. In particular, the last two papers in the report ere submitted as industrial papers

Goal-Oriented RE for E-Services

Current research in service-oriented computing (SoC) is mainly\ud about technology standards for SoC and the design of software components that\ud implement these standards. In this paper we investigate the problem of\ud requirements engineering (RE) for SoC. We propose a framework for goaloriented\ud RE for e-services that identifies patterns in service provisioning and\ud shows how to compose business models from them. Based on an analysis of 19\ud business models for e-intermediaries we identified 10 intermediation service\ud patterns and their goals, and show how we can compose new business models\ud from those patterns in a goal-oriented way. We represent the service patterns\ud using value models, which are models that show which value exchanges\ud business patterns engage in. We conclude the paper with a discussion of how\ud this approach can be extended to include business process patterns to perform\ud the services, and software components that support these processes

Graceful Interruption of Request-Response Service Interactions

Bi-directional request-response interaction is a standard communication pattern in Service Oriented Computing (SOC). Such a pattern should be interrupted in case of faults. In the literature, different approaches have been considered:WS-BPEL discards the response, while Jolie waits for it in order to allow the fault handler to appropriately close the conversation with the remote service. We investigate an intermediate approach in which it is not necessary for the fault handler to wait for the response, but it is still possible on response arrival to gracefully close the conversation with the remote service