An Introduction to Service Choreographies (Servicechoreographien – eine Einführung)

2008 ◽  
Vol 50 (2) ◽  
Author(s):  
Gero Decker ◽  
Oliver Kopp ◽  
Alistair Barros
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Global Perspective ◽  
Software Systems ◽  
Architectural Style ◽  
Service Oriented

SummaryService oriented architecture (SOA) is an architectural style for building software systems based on services. Especially in those scenarios where services implement business processes, complex conversations between the services occur. Service choreographies are a means to capture all interaction obligations and constraints from a global perspective. This article introduces choreographies as an important artifact for SOA, compares them to service orchestrations and surveys existing languages for modeling them.

Software for Small-to- Medium Enterprises

2010 ◽  
pp. 188-200
Author(s):  
Jaroslav Král ◽  
Michal Žemlicka
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Learning By Doing ◽  
Third Party ◽  
Limited Resources ◽  
Software Systems ◽  
New Business ◽  
Service Oriented ◽  
Medium Enterprises ◽  
User Knowledge

Small-to-medium enterprises (SME) have specific requirements on the software systems (SWS) they use. SME have a limited possibility to design stable business processes as they have limited resources and data to design the processes properly. Moreover, SME must be able to adapt itself dynamically to changing business conditions and must, due to limited resources, reuse legacy systems and third-party products. SME cannot apply the higher levels of CMM and to define precisely its business processes, as SME cannot have enough data and experience. The solution of this issue or weakening of its consequences can be based on the variant of service-oriented architecture (SOA) discussed next. A proper use of modern software systems depends on the skills and knowledge of (end) users of the systems. The extent of a new software-oriented knowledge of the users needed to specify, install, and use the systems depends on the architecture of the system. We further show that a properly used SOA can substantially reduce the need to learn new knowledge at users’ side. The kernel of the solution should be based on the SOA-based generalization of the concept of usability and on a technical turn enabling agility of business processes. The solution can simplify the development of tools enabling the activation of inhibited user knowledge via flexible prototyping supporting agile business processes and learning by doing. The solution further enables new business turns and has many technical advantages. Our solution is especially preferable for small-to-medium enterprises, but it should be applied in very large enterprises for different reasons.

Dynamic Reconfiguration of Component-Based Systems

2014 ◽  
pp. 76-102
Author(s):  
Tony Clark ◽  
Balbir S. Barn ◽  
Vinay Kulkarni
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Dynamic Reconfiguration ◽  
System Component ◽  
Ripple Effect ◽  
Dynamic Architecture ◽  
Component Architecture ◽  
Service Oriented ◽  
Typical Component

Component-based approaches generalize basic object-oriented implementations by allowing large collections of objects to be grouped together and externalized in terms of public interfaces. A typical component-based system will include a large number of interacting components. Service-Oriented Architecture (SOA) organizes a system in terms of components that communicate via services. Components publish services that they implement as business processes. Consequently, a change to a single component can have a ripple effect on the service-driven system. Component reconfiguration is motivated by the need to evolve the component architecture and can take a number of forms. The authors define a dynamic architecture as one that supports changing the behavior and topology of existing components without stopping, updating, and redeploying the system. This chapter addresses the problem of dynamic reconfiguration of component-based architectures. It proposes a reification approach that represents key features of a language in data, so that a system can reason and dynamically modify aspects of it. The approach is described in terms of a new language called µLEAP and validated by implementing a simple case study.

Semantic Web Services-Based Knowledge Management Framework

2016 ◽  
pp. 429-438
Author(s):  
Vili Podgorelec ◽  
Boštjan Grašič
Keyword(s):  
Knowledge Management ◽  
Web Services ◽  
Semantic Web ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Semantic Web Services ◽  
Semantic Web Technologies ◽  
Management Framework ◽  
Knowledge Based ◽  
Service Oriented

In this chapter, a Semantic Web services-based knowledge management framework that enables holistic knowledge management in organizations is presented. As the economy is becoming one single global marketplace, where the best offer wins, organizations have to search for competitive advantage within themselves. With the growing awareness that key potentials of an organization lie within its people and their knowledge, efficient knowledge management is becoming one of key focuses in organizational activities. The proposed knowledge management framework is based on Semantic Web technologies and service-oriented architecture, supporting the operational business processes as well as knowledge-based management of services in service-oriented architecture.

Enterprise Integration With the Structural Services Architectural Style

2019 ◽  
pp. 352-392 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Architectural Style ◽  
Enterprise Integration ◽  
Representational State Transfer ◽  
Advantages And Disadvantages ◽  
Architectural Styles ◽  
State Transfer ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Structural Compliance

The Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles are the most used for the integration of enterprise applications. Each is more adequate to a different class of applications and exhibits advantages and disadvantages. This chapter performs a comparative study between them. It is shown that SOA and REST are dual architectural styles, one oriented towards behavior and the other towards state. This raises the question of whether it is possible to combine them to maximize the advantages and to minimize the disadvantages. A new architectural style, Structural Services, is proposed to obtain the best characteristics from SOA and REST. As in SOA, services are able to offer a variable set of operations and, as in REST, resources are allowed to have structure. This style uses structural interoperability, based on structural compliance and conformance. A service-oriented programming language is also introduced to instantiate this architectural style.

A Role of Enterprise Service Bus in Building Web Services

2017 ◽  
pp. 46-58
Author(s):  
Dinesh Sharma ◽  
Devendra Kumar Mishra
Keyword(s):  
Web Services ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Enterprise Service Bus ◽  
Fast Processing ◽  
Service Oriented ◽  
Open Standards ◽  
Or Organization ◽  
Services Use

Present is the era of fast processing industries or organization gives more emphasis for planning of business processes. This planning may differ from industry to industry. Service oriented architecture provides extensible and simple architecture for industry problem solutions. Web services are a standardized way for developing interoperable applications. Web services use open standards and protocols like http, xml and soap. This chapter provides a role of enterprise service bus in building web services.

Improving Application Integration by Combining Services and Resources

2019 ◽  
pp. 197-226 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Application Integration ◽  
Architectural Style ◽  
Representational State Transfer ◽  
Architectural Styles ◽  
State Transfer ◽  
Fixed Set ◽  
Service Oriented ◽  
Application Developers ◽  
Bare Minimum

The main application integration approaches, the service-oriented architecture (SOA) and representational state transfer (REST) architectural styles, are rather different in their modeling paradigm, forcing application developers to choose between one and the other. In addition, both introduce more application coupling than required, since data schemas need to be common, even if not all instantiations of those schemas are used. This chapter contends that it is possible to improve this scenario by conceiving a new architectural style, structural services, which combines services and resources to reduce the semantic gap with the applications, allowing to tune the application integration between pure service-based and pure resource-based, or an intermediate mix. Unlike REST, resources are not constrained to offer a fixed set of operations, and unlike SOA, services are allowed to have structure. In addition, compliance is used to reduce coupling to the bare minimum required by the actually used application features.

An Open Source e-Procurement Application Framework for B2B and G2B

2011 ◽  
pp. 76-97 ◽  
Author(s):  
Georgousopoulos Christos ◽  
Xenia Ziouvelou ◽  
Gregory Yovanof ◽  
Antonis Ramfos
Keyword(s):  
Open Source ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Cost Effective ◽  
Assessment Process ◽  
Application Framework ◽  
Two Phase ◽  
Model Driven ◽  
Service Oriented ◽  
The Cost

Since the early 1980s, Open Source Software (OSS) has gained a strong interest and an increased acceptance in the software industry that has to date initiated a “paradigm shift” (O’Reilly, 2004). The Open Source paradigm has introduced wholly new means of software development and distribution, creating a significant impact on the evolution of numerous business processes. In this chapter we examine the impact of the open source paradigm in the e-Procurement evolution and identify a trend towards Open Source e-Procurement Application Frameworks (AFs) which enable the development of tailored e-Procurement Solutions. Anchored in this notion, we present an Open-Source e-Procurement AF with a two-phase generation procedure. The innovative aspect of the proposed model relates to the combination of the Model Driven Engineering (MDE) approach with the Service-Oriented Architecture (SOA) paradigm for enabling the cost-effective production of e-Procurement Solutions by facilitating integration, interoperability, easy maintenance, and management of possible changes in the European e-Procurement environment. The assessment process of the proposed AF and its resulting e-Procurement Solutions occurs in the context of G2B in the Western-Balkan European region. Our evaluation yields positive results and further enhancing opportunities for the proposed Open Source e-Procurement AF and its resulting e-Procurement Solutions.

Advanced Technologies and Architecture for Collaborative Business

2010 ◽  
pp. 121-150
Author(s):  
Bhuvan Unhelkar ◽  
Abbass Ghanbary ◽  
Houman Younessi
Keyword(s):  
Business Processes ◽  
Service Oriented Architecture ◽  
Business Environment ◽  
Process Engineering ◽  
System Architectures ◽  
Service Oriented ◽  
Technical Collaboration ◽  
Role Of Information ◽  
Technical Platform

This chapter discusses the role of information system architectures in Collaborate Business Process Engineering (CBPE). Thus, in this chapter, there is an extension of the discussion on Service-oriented Architecture (SOA) from chapters 2 and 4, and its importance and relevance to CBPE. The SOA based architecture is extended and applied in a collaborative business environment. The technical platform of Service Oriented Architecture (SOA) provides an ideal mechanism to start building collaborative business processes, as it facilitates technical collaboration of different environments - as discussed in this chapter.

Event-Driven Service-Oriented Architectures for E-Business

2010 ◽  
pp. 952-962
Author(s):  
Olga Levina ◽  
Vladimir Stantchev
Keyword(s):  
Distributed System ◽  
Enterprise Architecture ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Reference Architecture ◽  
Service Oriented Architectures ◽  
Application Systems ◽  
Event Driven ◽  
Service Oriented ◽  
Definition Of

E-Business research and practice can be situated on following multiple levels: applications, technological issues, support and implementation (Ngai and Wat 2002). Here we consider technological components for realizing business processes and discuss their foundation architecture for technological enabling. The article provides an introduction to the terms, techniques and realization issues for eventdriven and service-oriented architectures. We begin with a definition of terms and propose a reference architecture for an event-driven service-oriented architecture (EDSOA). Possible applications in the area of E-Business and solution guidelines are considered in the second part of the article. Service-oriented Architectures (SOA) have gained momentum since their introduction in the last years. Seen as an approach to integrate heterogeneous applications within an enterprise architecture they are also used to design flexible and adaptable business processes. An SOA is designed as a distributed system architecture providing a good integration possibility of already existing application systems. Furthermore, SOA is mostly suitable for complex and large system landscapes.

Developing a Collaborative Supply Chain Management Platform

2010 ◽  
pp. 209-232
Author(s):  
Yves Wautelet ◽  
Youssef Achbany ◽  
Jean-Charles Lange ◽  
Vi Tran
Keyword(s):  
Supply Chain ◽  
Supply Chain Management ◽  
Business Processes ◽  
Design Stage ◽  
Software Systems ◽  
Industrial Case Study ◽  
Chain Management ◽  
Dynamic View ◽  
Development Life Cycle ◽  
Service Oriented

Service-oriented computing is becoming increasingly popular. It allows designing flexible and adaptable software systems that can be easily adopted on demand by software customers. Those benefits are from primary importance in the context of supply chain management; that is why this paper proposes to apply ProDAOSS, a process for developing adaptable and open service systems to an industrial case study in outbound logistics. ProDAOSS is conceived as a plug-in for I-Tropos - a broader development methodology - so that it covers the whole software development life cycle. At analysis level, flexible business processes are generically modelled with different complementary views. First of all, an aggregate services view of the whole applicative package is offered; then services are split using an agent ontology - through the i* framework - to represent it as an organization of agents. A dynamic view completes the documentation by offering the service realization paths. At design stage, the service center architecture proposes a reference architectural pattern for services realization in an adaptable and open manner. The paper finally presents the implemented platform for a particular service – manage transport – so that the reader can realize how the developments have been achieved.

Sign in / Sign up

Export Citation Format

Share Document